mvied

@peopleinside Do you have time to show me what kinds of elements are giving you issues in the latest version? The latest is a huge improvement on speed at the cost of the reliability we’re used to with the plugin. I would love to get it back to where it was, but a lot faster. Thanks for your help!

Please try the latest release. I’ve made a few improvements that I think should speed things up, however I don’t have a large site to test it on. Let me know how it goes. Thanks!

Thanks for the kind words! 🙂

Performance is my highest priority for the next release. I’m going to add a few more options and hooks that should allow users to fine-tune it to their needs. I don’t know that I’ll be able to speed it up while retaining all of the functionality, so I may need to add different “modes” that the plugin can run in. But, it’s going to take some time to figure out what those are.

All of your concerns are valid. I apologize for letting it go without any updates for so long. I didn’t anticipate it being so resilient, haha.

I just pushed out a release that was actually quite a few features and performance fixes, hopefully. A few of those came from contributors on Github and they tested out fine as far as I could tell.

My primary focus for the next release will be purely performance and automated testing for the plugin. Back when I wrote the plugin originally, I didn’t know how to do automated testing or code profiling. In my years away, I’ve done those things and can work on speeding up what’s there by making some functionality optional and removing functionality that isn’t required in 2018 and beyond. Automated tests will help this thing not be the time sink that it originally became testing 1000 use-cases.

I’m going to write a sticky here shortly that outlines a my roadmap for the plugin and my suggestions on other options that exist. There are plenty of light-weight alternatives that I believe would work fine for most people. I understand that my plugin is heavy, but it also handles a lot more edge-cases. Not to say that we can’t get it sped up!

Thanks for your time!

I wrote this plugin almost 3 years ago and provided support and updates continuously for a long time. I own my own business and time is money. I simply can’t justify giving all my time away simply because I wrote this plugin for the public.

I only came here to tell you that I don’t understand your logic at all. I have my own life and things that I want to do with it. I should be allowed to.

I will be updating the plugin soon but I will not be supporting it for free. Especially since most requests come from people who don’t understand how to thoroughly troubleshoot their problems. I am not here to figure out your problems for you for free.

Caching plugins serve HTML files and the WordPress core (including plugins) is never run. There is no fix for this outside of creating rewrite rules in your .htaccess file to control if a page is forced to/from HTTPS.

If you keep activating the dev version, it should eventually work. I’ve made it so that the plugin now remembers when it has run the install process for a blog, so it shouldn’t try again. Try activating it a few times and let me know it works. Also, increase your memory limit if you can.