• While going through the plugin configuration, I see there are numerous HTACCESS edits required by the plugin to work.

    For security reasons we have .htaccess turned off.
    We also have an alternate WP core layout, based off Bedrock

    It would be great if we could see a ‘summary’ output of all the require HTACCESS rules, so that we can manually add them to our site host files…

    Any advice?

    • This topic was modified 5 years, 11 months ago by Sean.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author rosell.dk

    (@roselldk)

    Are the .htaccess file(s) generated? (plural because WebP Express when needed puts rules in multiple .htaccess files – ie when uploads folder has been moved).

    Look in the wp-content folder. (WebP Express puts the rules in the wp-content folder rather than root, because this ensures that no rules put in the root .htaccess by other plugins interferes).

    If so, you could simply copy the rules from there.

    But yes, I agree, it would be a good improvement to be able to see the rules that are generated in the backend. These rules, btw. are slightly different depending on the folder where they are generated. Also, btw, they vary depending on detection of server capabilities. Ie whether mod_headers are enabled or not, and whether or not it is possible to “pass” variables from the .htaccess to the script through environment vars

    Plugin Author rosell.dk

    (@roselldk)

    On this note, I would also like to make it possible to choose which .htaccess files which WebP Express should put rules in / which parts it should work for (uploads only / templates too / plugins too / all wp-content / admin too). There is an issue for that here: https://github.com/rosell-dk/webp-express/issues/219

    • This reply was modified 5 years, 11 months ago by rosell.dk.
    Plugin Author rosell.dk

    (@roselldk)

    Thread Starter Sean

    (@rapidsean)

    Thank you for the follow up!

    No we don’t have .htaccess files anywhere, as I was saying we have security rules in place that means we had to turn off ANY and ALL htaccess file use in Apache.

    For this reason, we use PUPPET to ‘build’ our environments on the fly, and part of that is to manually create/inject HTACCESS rules as required.

    So, yes, if we could use the WebP plugin to generate and show the various htaccess files / locations, we can replicate those manually

    it’s not the funnest way to work, I tell ya.

    edit:

    Perhaps a ‘Simulation’ mode where instead of writing to files, you write to the plugin Admin page

    • This reply was modified 5 years, 11 months ago by Sean.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Provide Summary of HTACCESS Rules that ‘would’ be generated’ is closed to new replies.