Weird section saving behavior
This is an open discussion with 4 replies, filed under Troubleshooting.
Search
I’d bet it’s a server security thing. mod_security or some such.
mod_security would typically result in the 411, right? I think it’s server related too… anyone else have additional things to check or similar experience?
Any major differences between the local and live MySQL version or config?
Good news. I replaced the php.ini settings with a backup copy and all works correctly. I think I fudged things when I had memory issues and was changing settings to try and accommodate larger XML output.
Nevertheless, what a weird result! Thanks for helping me think outside of Symphony :-)
I went to save a section for a website I have been working on and to my surprise the page reloaded with no error or save message. More importantly, several fields were deleted.
I copied the database and files to a local set up. Created the same scenario and the entry saved as it should. I then copied the database from local back to the live server. Upon saving the section again I got the original behavior where several fields were deleted.
This only occurs with one of my sections. There doesn’t seem to be any issues with the database.
Has anyone ran into this problem before? I’m hesitant to call it a bug but I can’t figure out what I might have done to cause this behavior.