Issue with WebP Express Plugin and WP-Staging

  • Resolved cpcusteve

    (@cpcusteve)


    3 years, 11 months ago

    Hi

    There’s an interesting issue with the WebP Express plugin and WP Staging which is worth noting if you use this combination of plugins. When WebP Express is activated, it writes .htaccess files to /wp-content, /wp-content/uploads, /wp-content/themes, /wp-content/plugins and /wp-content/webp-express/webp-images directories. It depends on these .htaccess files to serve webp format images correctly. Wp-staging does not transfer these .htaccess files to the staging site. This results in images being displayed as “not found” placeholders on browsers accessing the staging site. The work-round is to deactivate the webp-express plugin in the staging site and reactivate it, causing the .htaccess files to be written and restoring the display of the images.

    I don’t know whether this is something than can be addressed by additions to WP-Staging?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter cpcusteve

    (@cpcusteve)

    You can also write the .htaccess files by going to the WebP-Express plugin settings and clicking on “Save settings and force new .htaccess rules” (top right).

    • This reply was modified 3 years, 11 months ago by cpcusteve.
    Plugin Author Rene Hermenau

    (@renehermi)

    WP STAGING does not copy the .htaccess to the staging site if you set as target a subfolder. This is done for the reason to prevent 404 page not found and permalink issues related to a different path in the .htaccess. WP STAGING can not catch all possible variations in the .htaccess automatically so we decided to not copy the file at all.

    Thanks for the feedback and providing a possible solution for other users:-)

    Cheers
    René

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Issue with WebP Express Plugin and WP-Staging’ is closed to new replies.