• Resolved extremecarver

    (@extremecarver)


    At least with nginx – if you change something about the rewrite structure – the plugin wants to recreate the htaccess file – however it doesn’t. The only way to solve is deactivate the plugin, delete htaccess – reactivate plugin.

    There is no write protection or whatever on that file. It could easily be edited. Not sure why this bug happens. Easy to solve anyhow.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Fastware

    (@fastware)

    Hi @extremecarver

    What is exactly the issue you are encountering? It’s correct that the .htaccess is always written, but with nginx this .htaccess file is ignored, and should not cause issues.

    Thread Starter extremecarver

    (@extremecarver)

    The problem is a wrong error notice. The plugin complains about htaccess not being acessible. And maybe that bug also affects apache installations. Because the plugin only seems to be able to create that file from scratch but not to edit it (if it exists already – e.g. because you changed some options in the plugin or because another plugin created it)

    Thread Starter extremecarver

    (@extremecarver)

    But yeah I stopped using the plugin because the website would load superslow if the webp/avif image isn’t created yet with nginx. A filescanner and instant conversion of all images would be much better and yeah in general the nginx rules will not work with how this plugin works.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug .htaccess not accessible’ is closed to new replies.