Support Forum
This is most peculiar. It looks like you have an options record missing from the sfoptions table - but - if that is the case then it should be created after changes and an update.And the odd thing here is that there are no real error messages about failing to save it.
Do you have access to and know your way around your database?
YELLOW
SWORDFISH
|
Curiouser and curiouser.
I wonder if you are trying to put something in there it doesn't like which is causing a null value although - that really should produce an error message.
Any chance of a screen dump of that panel?
And if it is any help I can copy our data for that row and you could paste it in...?
YELLOW
SWORDFISH
|
This is ours but you will hjave to edit it. Interesting to see what happens though
a:9:{s:10:"sfnofollow";b:1;s:8:"sftarget";b:1;s:11:"sffilterpre";b:0;s:12:"sfdupemember";b:1;s:11:"sfdupeguest";b:1;s:10:"sfurlchars";s:2:"40";s:12:"sfallowlinks";b:1;s:10:"sfmaxlinks";s:2:"10";s:12:"sfnolinksmsg";s:56:"<b>** you don\'t have permission to see this link **</b>";}
YELLOW
SWORDFISH
|
Modified that data to my personal settings, copied it into the database and saved. Now when I go into Options > Content Settings everything looks correct and my options are all appropriately ticked. I tried clicking update content options just to test, and it wiped the sffilters empty again. Something definitely going on between the PHP and SQL.
I'll enable trace mode in my php.ini and see what's logged.
For now, I'll just manually update the database with the appropriate data until we figure this out.
okay. just let us know if you need any more info...
Visit Cruise Talk Central and Mr Papa's World
Nothing out of the ordinary in debug log file when viewing outputted SQL errors/warnings server-side. But, when attempting to save options in the Options-Content Settings, my database is definitely receiving a SQL drop command for the sffilters row (option_value) within the sfoptions table.
Nothing was changed whatsoever in WP between the SP 4.5x to 5.0 upgrade. This seems like a 5.0 issue to me. Any insight from you guys as to why this may be happening?