• tw1l1ght

    (@tw1l1ght)


    It would be very helpful to have a setting or filter or hook to change the .htaccess path

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support johnghiz

    (@johnghiz)

    Hello @tw1l1ght

    Thanks for your feedback.

    To ensure that we fully and correctly understand this feature, could you please provide us with a more detailed description of the exact functionality you need?

    Specifically, it would be very helpful if you could describe your specific use case or scenario where this feature would be utilized.

    All the best,

    Thread Starter tw1l1ght

    (@tw1l1ght)

    I face an issue with AllowOverride. Some hostings don’t give access to apache config file even by ssh. It becomes a pain to always contact the support, especially then you’re manages a lot of websites (like in my case).

    I understand it can lead to big code changes maybe with a bad backward compatibility, so maybe you can provide a snippet or example of code which can change the path to .htacces file?

    Plugin Support johnghiz

    (@johnghiz)

    Hello @tw1l1ght

    Thanks for providing the information.

    I’ve recorded your request and scenario and included it in my weekly report for the team to discuss. We are going to keep you posted on any updates regarding this.

    All the best,

    I am getting this error message in the plugin settings section:
    .htaccess rewrite rules—we’ve detected that .htaccess write rules are not executed on your Apache server, this can be because the server is not configured correctly for using .htaccess file from custom location

    I have tried several options but still the issue is not resolved.

    Plugin Support johnghiz

    (@johnghiz)

    Hello @asood28

    Please first confirm whether WebP/AVIF formats are being served correctly on your site. You can follow the steps in this documentation to check whether WebP/AVIF is active and taking effect.

    If the WebP/AVIF images are already converted and displaying successfully, you can safely ignore the warning. It is likely caused by residual page caching, which can sometimes lead to an inaccurate display or judgment.

    All the best,

    Plugin Support johnghiz

    (@johnghiz)

    Hello @tw1l1ght

    Just a quick update:

    The team has discussed your feature request and the specific scenario you presented. We are now going to further research methods to see if there is an alternative approach that would allow us to ensure compatibility with this issue.

    We are going to keep you posted once we have an update on our findings.

    All the best

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.