Support Forum
jim said
in the past we have had issues with posts not saving upon page refresh. And this new aha issue returns an empty page when trying to save. Perhaps the two are unrelated, but we haven't heard reports of the former in a while. The latter still has me baffled...
Sorry - I thought you said this was resolved due to a mod-security setting. Is that not now the case?
Guess I was just looking for clarification about where ini_set() is configured, and how it can be enabled since i don't know how it got disabled.
The php.ini file is the main configuration file that sets up all the options that php needs to run and do its stuff. Think of it like a Windows ini file or a Mac OSX preferences file.
It will be on the server somewhere - your server guy will know.
ini_set() is a php function that allows code to modify the ini settings during run time. To be honest I have not got a clue where you set this option to disallow ini settings being modified in code. That might be an Apache thing. I really don't know off-hand, But again - whoever looks after your server should know. WordPress calls the ini_set() function quite few times...
YELLOW
SWORDFISH
|
Yellow Swordfish said
I thought you said this was resolved due to a mod-security setting.
We just had another user report the issue, after I whitelisted the mod_sec rules I thought were causing the problem (posts not saving with ahah URL).
In earlier troubleshooting I was able to replicate the issue after disabling ModSecurity altogether.
The php.ini file... ini_set() is a php function... might be an Apache thing....
Thanks for the clarification!
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Yellow Swordfish said
When you disabled mod_security did you reboot the server?
No, apparently only a restart of Apache is required for the changes to be applied
And stepping back a bit... what has actually changed in your environment that this suddenly starts to happen?
That's the odd thing, nothing that I know of. We did have a consultant harden the server security, but that was over a month ago. Perhaps this issue of posts failing is coincidental due to new instances of users discussing certain content (medication for their dogs).
With that said, I did discover and whitelist certain "antispam" mod_sec rules and have since been able to post content that previously threw the blank aha page.
Still monitoring things and awaiting any further reports from members.
FYI: Prior to doing that, I did re-enable ini_set() and that made no difference with this issue. But I have not yet seen another entry about it being disabled in the SP error log either.
As usual, having this forum as a sounding board for tossing around troubleshooting ideas has proven valuable. Thanks again for all the feedback!
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Web developers the world over shudder at mod_security. It is a good idea and on a website where the urls are known and fixed then it is just fine. But on any website where the urls are dynamic 'permalinks', then there will always (and yes - I do mean always) be the odd problem. Let's hope this is all it is.
YELLOW
SWORDFISH
|
1 Guest(s)