Olawale Adesina

Also, if the upgrade was completed successfully, older version of the plugin will no longer show the correct part but if it does, that shows the upgrade wasn’t completed successfully.

So, we’ll need to make an update that enable manual trigger for series update to new part and I’ve added an issue on it in https://github.com/publishpress/publishpress-series/issues/810.

I’ll try my best to work on this today and send an update for test.It’s advisable not to

Hello @wp-mememe

After upgrading the plugin, you should get a notification below on admin pages for data upgrade.

Can you confirm if you completed the upgrade task?

Hi @nitrofox

Thanks for reporting this issue.

A fix has been made which will be included in this week follow up release.

Here’s the patch you can install pending the time the update is released https://drive.google.com/file/d/1qQC_XnbtQVb_H4odaBkdEX-30Yv8EPZZ/view?usp=sharing

Hi @nreljed

While waiting for the release, i made a quick check on our code and notice there’s a way you can enable classic editor tab before we release an update to fix this issue by simply defining PP_CAPABILITIES_CONFIGURE_CLASSIC_EDITOR as true in your wp-config.php

Example: Adding the below code in your config file will enable the classic editor tab even without classic editor plugin been active.

define('PP_CAPABILITIES_CONFIGURE_CLASSIC_EDITOR', true);

Hello @rcosmos

Thanks for reporting the issue, we’ve made a fix for this which will be available on scheduled release coming on Monday but before then, here’s the beta package that has latest update as well fixing the issue which you can use pending the time the release will be out.

https://drive.google.com/file/d/1B5gRsbBACztQ_3PV4D6OAWMig5AGV4m_/view?usp=sharing

Hello @natethenomad, this doesn’t seems to be capabilities plugin issue.

Did you try deactivating capabilities while the other plugin is still active and then test if the problem still exist or not?

Hi @williamwps, thanks for providing the requested information.

Kindly be informed this is not a conflict with woocommerce latest version as earlier suggested but an option key returning unexpected data.

The issue has been noted and will be fix in the next update but before then, you can get a quick fix so everything could be back to normal by deleting “capsman_feature_restrict_classic_product” in wp_option table as it contain invalid data or alternatively, simply go to Editor features via ‘/wp-admin/admin.php?page=pp-capabilities-editor-features’ and update the settings for affected roles.

Regards.