Hi,
Do you use a security plugin, iTheme Security or similar?
Yes I do. That’s probably non negotiable however.
Is there a way for them both to work, together? Surely there must be?
I see lots of people on your website forum having this issue, but there appears to be no resolution. You have asked the same question there also, “Are you using a security plugin like iTheme Security?”, but how does this question answer the obvious issue here????
Are you suggesting there is a conflict? If so, can it be addressed? Can you direct me to a thread where a solution was found?
iTheme Security works with BackupBuddy, which is a paid service which I use on all my WP websites. I can’t just switch it off, disable or delete it. Is there a way for your component to work with it or not????
Does your Pro version resolve this issue?
Please, some kind of useful response would be appreciated. God, I hate these so called ‘Support Forums’.
OK, for those people who may not actually have an account with Time.ly and who run into this conflict, here is some helpful advice:
I was having this same issue with WP ver 4.2.2 and AIO Calendar ver 2.2.1, but only with Firefox and IE browser. Thinking that this most likely was a plugin issue, I selectively worked my way through the plugins until I hit iThemes Security. After isolating the plugin, I worked my way through the individual settings and discovered that the problem was in System Tweaks and Suspicious Query Strings. After turning ONLY this feature off, everything works in all 4 major browsers now.
So at the end the problem was with iThemes Security plugin.
For those who have the same problem, go to iThemes Security > Settings > System Tweaks Filter Suspicious Query Strings in the URL, and deactivate -> Filter Suspicious Query Strings in the URL.
Take care,
Ben
Yes, in the end the problem was with iThemes Security plugin.
Thanks to someone else’s hard work, I was able to resolve the issue.
I think it would be awesome if support people actually offered support instead of responding to questions with other questions which don’t in any way provide an answer!
A simple link to the thread would have saved me some time, but hopefully I’ll be saving someone else valuable time by posting the fix here for you.
I immediately asked if you use iTheme Security plugin. This did not help you? Because I see you’ve found the cause of this issue in iTheme Security options and there was no need to write you a solution. 403 error can occur for several reasons, and because of this we must first ask some questions.
Take care,
Ben
