Install locally with ServerPress getting this error upon activation

Hey there crafter,

Looks like we have a typo in the file your error mentions, I’ll get a fix out in the next hour or so, need to pack it up and rerun our tests, but in the meantime, if you open that file up (since you’re testing locally), you can change line 12 to

if( !class_exists( 'PucFactory' ) ) {

And that’ll resolve your problem.

Alternatively, wait an hour and download the update.

Thanks,

Hey Crafter,

2.0.4 should fix your issue. Again, sorry about that!

Please let us know if it resolves your issues.

Have a great day!

Yea the update took my site down, which isn’t a big deal since it is for development only.

The site will come back up when I manually delete LifterLMS.

Now the error I see in my browser is pointing to another plugin that is activated that uses PUC, but I think the problem is in Lifter.

So the error says: Fatal error: Call to undefined method PucFactory::addVersion() in /Users/…/wp-content/plugins/thrive-leads/plugin-updates/plugin-update-checker.php on line 959

But like I said, removing Lifter brings my site back. If I delete the plugin in the error message my site does not come pack, it just lists the same error for the next plugin I have activated.

Hey Crafter,

We’ve made some mistakes in 1) using this 3rd party library ages ago and 2) in attempting to phase it out by stubbing it out. We were using it for a handful of extensions and the extensions required the plugin and when we phased it out (without a stub like we have now) the extensions looking for the plugin (even though they didnt need it anymore) were failing. So in order to migrate everything over we created the stub which, even though we don’t want it to load in your case, is being defined before whatever other plugin uses it is defining it and causes some issues…

As a backup we implemented a filter to opt out of loading our deprecation file altogether, can you add the following filter to your theme / child theme’s functions.php file and see if that let’s you get up and running again?

add_filter( 'lifterlms_include_deprecated_functions', '__return_false' );

Thanks,

Thanks for sorting this out. I am preparing a review of the plugin, so trying to get it working, lol.

Hey added that function to my child theme, still getting that error.

What I did was remove all the plugins that were having issues. Finally got Lifter activated. I added the function. Then added those plugins that were not playing nice. But now they won’t activate. BTW one of those plugins is Updrafts, which has a very large user base.

Hey Crafter,

I’m not sure what’s going on here — can you give me a list of a few (hopefully free) plugins that I can install locally to get a recreation of this issue and work out a solution.

I realize this update checker is generally used on non-free plugins which might make that task a little bit more difficult. If none of them are free can you provide me some links to the websites where I can get the plugins you’re using.

A quick google of “Updrafts” doesn’t net any results that I think match the large user base you’re hinting. Is it “UpdraftPlus”?

Also, what’s the error the other plugins are reporting during activation?

Thanks,

Actually, I think I know what the issue is…

based on WP architecture the filter will never run until after plugins are loaded rendering it ineffective for what we’re actually trying to accomplish.

So really we need to opt-out using another method, which should be pretty simple…

I made a patchfile for lifterlms.php (core plugin file in wp-content/plugins/lifterlms/lifterlms/lifterlms.php

Since you’re local and incredible can you give this file a test and ensure it works before I make it an official part of the codebase?

I’ve located a copy of a plugin that I could recreate the issue you’re experiencing with and the patch fixes it, but my previous fix yesterday also fixed the issue on my end so I want to ensure this works in your environment.

This solution relies on a constant (which we can add to the wp-config.php file so that at time of plugin load our opt-out will be fired, instead of during theme setup when it’s too late.

The patch file is here: https://gist.github.com/thomasplevy/57edcec800bdca66b40d

Copy the contents of the gist and replace the contents of lifterlms.php with it.

Then add define( 'LLMS_LOAD_DEPRECATED', false ); to your wp-config.php file before the /* That's all, stop editing! Happy blogging. */ comment.

I’m fairly certain this will (finally) resolve your issue.

Thanks for your patience!

Yup, replacing the file, then adding that to my wp-config file, solved the problem!!

Thank you very much, now I can get to testing!!!

Perhaps you should document this because I am sure your user base will be increasing rapidly moving forward.

Added to documentation here, thanks for your help!