Hi DLT95,
I had this exact same problem from a client of mine. He had installed two plugins for creating columns. When I deactivated the ‘Easy Columns’ plugin, the ‘Advanced WP Columns’ plugin worked fine. So, a rather misleading error message for a plugin clash. …
Helen
Thread Starter
DLT95
(@dlt95)
That sounds like a good call. Thanks.
Easy Columns is also installed on this site but unfortunately I cant remove it until there is a replacement in place as the site is live. I was hoping to try out Advanced WP Columns on a test page first without changing the other pages but if the two plug-ins dont play nicely together then that wont be possible.
Agreed, a very misleading error message. I was expecting it to be something to do with the recent WP3.9 update.
Edit: Just seen that Easy Columns is broken in Wp3.9 so with any luck when the developer fixes that it will also fix this incompatibility with Advanced WP Columns.
Thread Starter
DLT95
(@dlt95)
The Easy Columns developer updated his plug-in which has solved most peoples problems with it and WP3.9 but it hasn’t helped with my permissions error in Advanced WP Columns.
And on top of that I now get a similar error when I click on the Easy Columns editor button, though of course the error mentions a file in the Easy Columns plug-in directory.
Have you contacted the developers of both plugins? You could direct them to this support thread.
You could set up a copy of the live site inside a dev folder in the root of the live site, and play with the columns plugins there.
Thread Starter
DLT95
(@dlt95)
On a flash of inspiration I renamed my htaccess file and bingo: both plugins working correctly. Now all I need to do is work out what in the htaccess file is preventing the two plugins from working. It’s strange as the htaccess file hasnt changed for months but I didnt get the problem before.
Thanks for the good ideas anyway.
Thread Starter
DLT95
(@dlt95)
That was easier than I expected. It was actually a rewrite setting in BPS Security that needed changing.
In the custom code section add something like this:
# <plug in name>
RewriteCond %{REQUEST_URI} ^/wp-content/plugins/<plug-in directory>/ [NC]
RewriteRule . – [S=<number as needed>]
to the bypass rules, changing the parts in <> to suit your needs.
I dont know why the problem suddenly arose after so much time.
Good work, DLT95. My client also has the BPS Security plugin installed and activated. So, a three-way clash of sorts. …
Plugin Author
LordMX
(@lordmx)
I’m glad that you solve this issue. PS, did any of you try to contact me directly, it looks like I missed it somehow.
Anyway, thanks for your feedback, I’m sure it will be useful if there’s more peoples with the same problem. 🙂
Regards
Hi LordMX, I didn’t try to contact you.
