htaccess modifications and deactivation
-
I setup webp express for CDN friendly modifications to the HTML alone. I noticed it modified the .htaccess files anyway, which I did not want to happen because I just wanted to try the <picture> element.
Then, when I deactived webp express, the modifications were still left in the .htaccess files. Not good.
BTW: This is the best solution I’ve seen for the <picture> element. It ultimately didn’t work for me, but kudos on moving in the right direction for webp. Here’s some of the changes left after deactivation:
$ cat wp/wp-content/uploads/.htaccess # BEGIN WebP Express # The rules below have been dynamically created by WebP Express in accordance with the plugin settings # DO NOT EDIT MANUALLY (unless you are prepared that your changes might be overridden by WebP Express) # The following parameters have been in play to produce the rules: # # WebP Express options: # - Operation mode: cdn-friendly # - Redirection to existing webp: disabled # - Redirection to converter: disabled # - Redirection to converter to create missing webp files upon request for the webp: disabled # - Destination folder: separate # - Destination extension: append # - Destination structure: image-roots # - Image types: jpeg, png # - Alter HTML enabled?: yes # # WordPress/Server configuration: # - Document root availablity: Available and its "realpath" is available too. Can be used for structuring cache dir. # # .htaccess capability test results: # - mod_header working?: yes # - pass variable from .htaccess to script through header working?: no # - pass variable from .htaccess to script through environment variable working?: yes # # Role of the dir that this .htaccess is located in: # - Is this .htaccess in a dir containing source images?: yes # - Is this .htaccess in a dir containing webp images?: no
The page I need help with: [log in to see the link]
- The topic ‘htaccess modifications and deactivation’ is closed to new replies.