Hi @georgeorg,
There are a couple of reasons for this error. Please check:
Do you have a plugin installed called iThemes Security Pro?
It’s could be a setting in that plugin. The one that triggered it for other users was: Suspicious Query Strings – Filter Suspicious Query Strings in the URL
Unchecking this option fixed the problem.
Do you have a plugin installed called All In One WP Security?
This error is caused by a setting in that plugin called “6G Blacklist firewall protection.”
To fix the problem, disable that option and enable “”5G Firewall Protection” instead.
Greetings, thanks for the answer but it didn’t work.
i have wp security
disabled 6g blacklist
enabled 5g
didn’t fix the error
even tried disabling both 6g an 5g
-
This reply was modified 8 years ago by
georgeorg.
Hi @georgeorg,
Do you have any other security or caching plugins?
In any case, can you try this broad troubleshooting step to see if it helps:
Please try a different theme temporarily such as Twenty Seventeen, or, disable all plugins and then check if the problem recurrs — then re-enable each one until you find which one caused the problem.
Let me know the results.
no other security plugin.
it’s no help trying another theme , which will cause other problems in a running site
dont even suggest it
by disabling temporarily wp security there is no conflict
and calendar works fine
try to figure out the conflict after your last update please !!!
thanks
Hi @georgeorg
The last update’s change release can be seen here:
https://time.ly/document/release-notes/one-event-calendar/2-5-30/
Released Apr 11, 2018
Fixed compatibility with PHP 7.2.
Clean up: Removing use of deprecated WordPress function.
You would have to contact the support staff for All In One WP Security plugin, if their plugin is blocking our calendar script.
great answer Sunny Lal !
your plugin update caused the issue, please don’t make customers choose between a calendar and a security plugin !
following your advice, i have contacted and waiting an answer from wp security support
George, in my last message I explained the 2 changes that were made in order that your 3rd party plugin support might be able to find why their plugin is blocking our script. I didn’t ask you to choose anything.
thanks for your efforts and replies
the conflict went off after having disabled all firewall rules from the plugin
i contacted the other plugin support for a solution.
thanks, although i believe that a “change” from this side faults for the conflict, prior to last update everything worked ok
