Chad Ross
Member
I'd like to be able to use Gravity Forms for to contain UNC path data such as \\share\directory\filename.ext.
However, when I submit the data the backslashes are properly written to the database (verified by direct mysql query) but when I go to view the entry the backslashes are gone, displaying sharedirectoryfilename.ext and if I edit the entry and submit the backslashes are now removed from the db entry as well, now leaving sharedirectoryfilename.ext in the database as well.
Ideas?
Hey Chad, we are going to look into this and get back with you. Need to reproduce it on our end and then determine why it is happening, etc.
chadlanchlanross,
We have identified the problem. It is a bug in Gravity Forms causing slashes to be stripped off when they shouldn't. We are currently working on a fix. I will let you know when it is ready for you to give it a try.
We have released an updated version of Gravity Forms that should take care of this issue. You may update your install using Automatic Upgrade in your WordPress plugins page or by downloading the v1.2.1 release from the Downloads page.
If you go to your plugins page and it says no updates are available for Gravity Forms, click on the "Installed" link under the "Plugins" page once again to force WordPress to check for updates. It caches this information.
Chad Ross
Member
It's back again, same behavior. Data (thank gawd) is correct in the DB, just displays without the backslashes in the admin View entry page.
GF 1.5.2 WP 3.1.2 PHP 5.2.10 I've performed standard testing, disabled theme, all other plugins. Tested in FF4, IE8, Chrome. Issue still occurs.
Odd thing is I reverted to GF 1.4.5 and the issue also still occurs, even though I am sure it was working with that version previously.
Only change recently is updating to WP 3.1.1 to 3.1.2.
Edit: Rolled back to 3.1.1. No change, \ characters are still gone.
Ideas?
Chad Ross
Member
Update again: Turns new entries created after updating to 1.5.2 weren't written to the DB correctly, the backslashes are stripped even when being created, so that's why rolling back to Gravity Forms 1.4.5 didn't seem to alter the behavior.
I've rolled back to 1.4.5 and manually fixed the entries created after updating to 1.5.2 and things seem fine for now, so it's obviously an issue with GF 1.5.2.
We have replicated this and will get it patched in the next release which should be out within the next 48 hours.
