beyonddesignmedia
Member
I have a form that has 47 fields so far...can't add anymore as it gives me your message when I save "There was an error while saving your form, most likely caused by a plugin conflict. Please contact us and we will be happy to help you get this corrected."
I've raised my PHP Memory Limit is 512M and my WordPress memory limit to 512M. I've installed the TPC! System Overview plugin to make sure it was set correctly.
This isn't a memory issue. It's going to be either a plugin or theme conflict OR related to data you are trying to use in one of the fields.
What are you trying to add to the form or change on the form? Can you simply add a new single input field and save the form? Are you trying to add anything that includes HTML or any special characters when editing the form?
The message you saw is a failsafe to prevent a corrupt array of form data from being saved and overwriting your form. This is triggered when something is wrong with the array to be stored. It's either caused by some sort of bad character in the data or by a plugin or theme conflict.
beyonddesignmedia
Member
Hmmm...well, I can save up to about 47 fields and then if I just click to enter a new single text box, it gives the error. If I then delete one of my other fields (like a name or something) it will save and then if I add another single line text box (or any other field) it throws the error.
Keep us posted. It doesn't sound like a memory issue, it sounds like something else is going on.
beyonddesignmedia
Member
Okay, so I need help with this. The form saves fine with the number of fields I have now. If I click to add a new field, it won't save and displays the error above, again "There was an error while saving your form, most likely caused by a plugin conflict. Please contact us and we will be happy to help you get this corrected."
If I delete a single field from my form, I can then add a new one, but I can't add two...make sense? I really need help with this.
Something is causing this issue to happen, as I mentioned above it could be a plugin or theme conflict that is causing this OR it could be data you are inputting into the field settings that is triggering this.
I would suggest checking for theme and plugin conflicts first by following the instructions here:
http://www.gravityhelp.com/documentation/page/Testing_for_a_Theme/Plugin_Conflict
Let me know how it goes and we can go from there.
beyonddesignmedia
Member
I have all plugins deactivated except Gravity Forms and the Gravity Forms Paypal integration. I have Twenty Ten Theme activated. Was able to add 1 new field and save successfully...then clicked to add a phone field and clicked save and got the same message. Do you want to login and see yourself?
Send me a WordPress admin login for the site to carl@rocketgenius.com and include a link to this forum post so I know what it is in reference to. Let me know exactly which form you are editing and exactly what field(s) and field settings you are trying to use so I can recreate the issue exactly as you encounter it.
Yes, we did and our lead developer will be taking a look. We already know what to do to fix the issue. It is an issue that has to do with content in your HTML fields breaking the serialized array used by the AJAX request to save the form. We just need to determine why it is happening on your form because nobody else is experiencing it.
beyonddesignmedia
Member
Okay, since you've now found it, would it be okay if I activated my other theme again? Also, I know you're super busy, but do you know when he will be able to look at it at all? Just want to know if it's going to be today at all.
beyonddesignmedia
Member
With what you said, would it have anything to do with quotes or semi colons? for example, my hidden html fields bring up images like this...
<img src="http://accucolorweddings.com/wp-content/uploads/2011/09/Charlee.png" alt="Charlee Font" />
<div style="clear:both;"></div>
If I used single quotes and removed the semi-colon do you think it will matter?
@beyonddesignmedia It was not a markup issue like I suspected. Instead it looks like a strange server related issue. Our lead developer sent you a detailed description of the problem and you'll need to discuss it with your web host.
Awesome, glad your host was able to pinpoint the exact cause. We will note this in case we encounter this again.
