Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Critical error when activating plugin due to incompatible Carbon Fields #7

Closed
jggerrits opened this issue Jul 28, 2021 · 3 comments
Closed
Assignees
Milestone

Comments

@jggerrits
Copy link

Sorry, the attached image is in Dutch, but I think you can understand the message. I used Customify and need to upgrade to Style Manager.

After activating the plugin, the /wp-admin can no longer be reached and needs to be recovered in recovery mode.

Got this from the apache logs:


[Wed Jul 28 10:43:05.876072 2021] [proxy_fcgi:error] [pid 25494:tid 139890356279040] [client 185.58.53.95:51060] AH01071: Got error 'PHP message: PHP Fatal error: Declaration of Pixelgrade\StyleManager\Provider\PluginSettingsCFDatastore::load($field) must be compatible with Carbon_Fields\Datastore\Datastore_Interface::load(Carbon_Fields\Field\Field $field) in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/style-manager/src/Provider/PluginSettingsCFDatastore.php on line 12\n',

Carbon_Fields

@vladolaru
Copy link
Contributor

Thank you @jggerrits for this report. To help me nail down the problem, could you share a list of active plugins and also the PHP version your server is using? Thanks.

@vladolaru vladolaru self-assigned this Jul 28, 2021
@jggerrits
Copy link
Author

WordPress 5.8
Server running PHP version: 7.0.16.

List of plugins:

business-profile
coming-soon
customify
display-php-version
duplicate-page
food-and-drink-menu
fsp-premium-helper
nova-blocks
pixelgrade-care
restaurant-reservations
style-manager
temporary-login-without-password
ultimate-addons-for-gutenberg
updraftplus
wordpress-seo
wp-google-maps
wp-mail-smtp
wp-restaurant-manager
wpforms-lite

@vladolaru vladolaru added this to the 2.0.5 milestone Aug 2, 2021
@vladolaru
Copy link
Contributor

Thank you @jggerrits for your info. I have fixed the issue and will release an update shortly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants