• Resolved mikeatbds

    (@mikeatbds)


    Site went down after the update. Reverting to 2.40.0 fixed things, so I disabled auto-updates for now.

    The error message I was seeing with WP_DEBUG set to ‘true’ was:

    Uncaught Error: Call to undefined function PublishPress\Capabilities\pp_capabilities_feature_enabled() in ….capability-manager-enhanced/includes/features/frontend-features/frontend-features-restrict.php:24.

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    Thanks for reporting that, @mikeatbds

    We see the error and will have an updated version of Capabilities out in the next hour or so.

    Also experienced this, commenting so I can follow this thread.

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks to everyone who reported this. Please let us know if version 2.42.0 fixes the error for you (or not).

    I had the same issue and 2.42.0 fixes it here. Thanks for the quick fix.

    Re my previous post, careful, the downloaded ZIP filename is still 2.41.0, I had to rename it as 2.42.0.

    Plugin Author Steve Burge

    (@stevejburge)

    That’s good to hear. Thanks for letting us know, @manni02

    It’s possible there’s a cache still showing for you.

    The download button here links to https://downloads.wordpress.org/plugin/capability-manager-enhanced.2.42.0.zip

    • This reply was modified 2 months, 2 weeks ago by Steve Burge.

    Thanks, that did download 2.42.0.

    Hi @stevejburge – Confirmed that the 2.40.0 release resolves fatal errors on two sites we manage. Thanks for the quick investigation/resolution.

    Cheers

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks for letting us know @rlkz. There’s a lot of under the hood changes in the last two versions. We were so focused on getting those right that we let another, un-related issue slide in.

    Thread Starter mikeatbds

    (@mikeatbds)

    Much appreciated. 🙂

    I’m still facing issues with the latest updates v2.41.0 and also v2.42.0. If i update to either version from WP dashboard or by uploading the file directly as a “new plugin”, it causes my site to hit an error for “There has been a critical error on this website.”

    Using FTP i have to rename the plugin folder for this plugin in wp-content, which allows me back in to WP admin dashboard, but i still get the same error when trying to access the “installed plugins” section. I can use the “add plugin” function and re-upload the v2.40.0 file, which then lets me back in to the plugins section, where it tells me it can see both versions installed, although one is in the wrong folder it says (the one I’ve renamed manually). I can then delete that plugin and it leaves me functioning again on v2.40.0 which is working fine.

    Plugin Author Steve Burge

    (@stevejburge)

    Hi @wpsi1. It sounds like you may need to remove both folders and then try installing 2.42.0 again.

    Hi @stevejburge thanks for the suggestion. I did a complete deactivation and deletion via WordPress dashboard for the installed v2.40.0, then via FTP checked that there was no trace of any related folder in the plugins directory.

    After that I installed the latest plugin as new via the “add plugin” section, but faced the same error. It will let me in to my dashboard, but I get the same error when trying to access the plugins section. I can use “add plugin” to manually overwrite the new version with the older v2.40.0 which I had downloaded, and then everything returns to normal.

    I don’t face this problem with any other plugin updates. Are there any known compatibility issues with any plugins I should perhaps check? any other advice appreciated. thanks

    Plugin Author Steve Burge

    (@stevejburge)

    @wpsi1 Sorry, I don’t have an easy explanation for that. It could be a caching issue. Perhaps a server configuration issue. If 2.40.0 works for you it might be best staying on that version and updating with with the next Capabilities release.

    thanks for the pointer @stevejburge I think this might have been a clash with the ‘Docket Cache’ plugin. I’ve disabled that and it allowed the normal update process for this plugin to work without an error.

Viewing 15 replies - 1 through 15 (of 16 total)

You must be logged in to reply to this topic.