that code snippte is only useful if you’re on cloudways servers π
a 403 is “not authorized”, you likely have some security plugin (?) blocking access to .php-files in wp-content/plugins, you’ll have to tweak settings there a bit I guess?
This plugin’s thumbnail cache feature conflicts with the timThumb rule from the 6G and 7G htaccess firewalls by Perishable Press. Commenting that line out will resolve that 403 error, or at least it did in one of our cases. Worth a try if you happen to use that firewall, which by all means you should π
https://perishablepress.com/7g-firewall/
interesting MNX. what line specifically is that?
Respected sir , I was trying to figure out the issue but unable to fix my 403 issue . I even tried removing all the codes from .htacess files then also it was showing same error Evemn i tried with wordfence deactivation didnp’t work . I tried removing function.php codes that also didn’t worked . I was a big fan of perishablepress . I am using 5g code in .htacess file . Thanks for proving 7g code i will use that .
Could you please provide me fix ? Still unable to figure it out
@optimizingmatters
Line 72:
RewriteCond %{REQUEST_URI} (thumbs?(_editor|open)?|tim(thumbs?)?)(\.php) [NC,OR]
@ronwisely
Hold on, there may be a fix for this soon. We’re working on it.
@optimizingmatters Since it’s hard to omit that string with your plugin, do you think you’d be able to contact Mr. Starr at perishablepress directly and enquire about a more permanent solution? I hear he’s a very nice guy. The problem is any solution we come up with may get flattened in the next update so working together is inevitable to ensure future compatibility. I wouldn’t like to sit in the middle of this though as it’s bound to disrupt communication.
sent him a message through his contact form π
OK, so after discussing with Jeff I somewhat reluctantly (I’m lazy) decided to move away from the nice lyteThumbs.php file name, which will become lyteCache.php. This has been done on the github-version, so I would not volunteers to test π you can download the zipfile here and install it instead of the stock 1.7.11 you have now. Feedback appreciated!
@optimizingmatters
Respected Sir ,
π Still not yet fix
What to do now
@optimizingmatters This was probably the smartest fix, yes!
@ronwisely The next update should include the fix.
so did you test @mononox ? π
@optimizingmatters It works!
Edit: My bad, had wrong testing conditions π
phew, you had me scared there for a second (I saw you original answer in the notification mail) π