Support » Plugin: 404page - your smart custom 404 error page » New update incompatible with Fast Velocity Minify plugin

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Peter Raschendorfer

    (@petersplugins)

    OK, I took a look at the HTML code and it seems that there’s a link to a file cached by FVM that no longer exists. I think it’s only a temporary problem due to updating 404page. As far as I can see, you should only have to purge the FVM cache once to make it work again. If you’re using a caching plugin you should also purge the cache there. Please try it and let me know.

    Many thanks for your detailed problem description.

    Regards,
    Peter

    edikitt

    (@edikitt)

    Hmm, that doesn’t appear to have worked.

    I purged the files and cleared both the minification cache and the static cache on my server.

    It appears that the URL paths on the 404 pages are pointing to http://www.gradepotentialtutoring.com (my production site) instead of staging1.gradepotentialtutoring.com (my staging environment). Oddly enough, this is only happening on the 404 pages and possibly only on my staging environment.

    For example, if you examine the HTML on a non-404 page (http://www.staging1.gradepotentialtutoring.com/about-us), the paths are all pointing correctly to staging1.gradepotentialtutoring.com.

    Plugin Author Peter Raschendorfer

    (@petersplugins)

    You are right, I did not notice the difference in the URLs. I can’t imagine the reason for this strange behavior. Is it a Multisite?

    Hi Peter, hope you had a great weekend!

    It’s a completely separate WordPress installation. However, I’m fairy sure that the staging environment files are simply copied over from the production site. This is a 1-click feature with our hosting company, so I’m not entirely sure what the process is. Could that have created any issues?

    • This reply was modified 9 months, 3 weeks ago by  edikitt.
    • This reply was modified 9 months, 3 weeks ago by  edikitt.
    Plugin Author Peter Raschendorfer

    (@petersplugins)

    Many apologies, I’ve totally forgotten this issue!

    Does the problem still exist?

    Peter

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.