Gutenberg: Fatal error on plugin activation.

[sayful1]

When I tried to activate it gives me fatal error.

Fatal error: Cannot declare class WP_REST_Autosaves_Controller, because the name is already in use in /var/www/shapla.test/wp-content/plugins/gutenberg/lib/class-wp-rest-autosaves-controller.php on line 0

Please see the attachment

WordPress environment (local):
WordPress version: 5.0-alpha-43773
Gutenberg version: 4.0.0
Server: nginx/1.14.0
PHP version: 7.0.32

[swissspidy]

Gutenberg should be compatible with WordPRess 5.0 beginning with plugin version 4.1.

Please download 4.1 RC 1 here and test again: https://make.wordpress.org/core/2018/10/19/whats-new-in-gutenberg-19th-october/

[sayful1]

Installed Gutenberg 4.1.0-rc.1 but got another error:

Fatal error: Cannot redeclare get_block_categories() (previously declared in /var/www/wp.test/wp-admin/includes/post.php:1950) in /var/www/wp.test/wp-content/plugins/gutenberg/lib/client-assets.php on line 1265

[youknowriad]

Thanks for the report @sayful1

@mcsf Looks like we missed some functions

[mcsf]

I can work something up in the next hour.

[mcsf]

Actually, this is not the same straightforward operation as in #10754. In:

Fatal error: Cannot redeclare get_block_categories() (previously declared in /var/www/wp.test/wp-admin/includes/post.php:1950) in /var/www/wp.test/wp-content/plugins/gutenberg/lib/client-assets.php on line 1265

Guarding the function definition with function_exists is enough for the plugin to be activated, but then the site gets bricked, since in subsequent page loads the core function is declared _after_ the plugin's function:

Fatal error: Cannot redeclare get_block_categories() (previously declared in /www/wp-content/plugins/gutenberg/lib/client-assets.php:1268) in /www/wp-admin/includes/post.php on line 1987

[mcsf]

For completeness, get_block_categories was added to core in r43762.

since in subsequent page loads the core function is declared after the plugin's function

I'm not sure if this means that some of the functions landing in core should be made pluggable, or if it means that the Gutenberg plugin should be checking against the WP version before some of its function declarations. Thoughts, @pento?

[Jojaba]

Hello! I get the same issue than sayful1. Ready to test any patch you will publish ;)
Thanks in advance!
Joël

[youknowriad]

@mcsf Cab we just check for existence now and on 4.2 or 4.3 we just remove all this code by increasing the minimum WP version for the plugin to 5.0?

[mcsf]

@youknowriad, checking for function existence in the plugin leads is useless since the plugin loads before core's declarations in wp-admin/includes/post.php. (I assume you didn't mean checking for existence in core.) That's why the server fatals.

[youknowriad]

Mmm 🤔 gotcha, can we rename the function in the plugin maybe?

[mcsf]

Since this particular function isn't expected to be consumed by other plugins, we could.

[mcsf]

See PR #10826.

[Jojaba]

Hello,
Just downloaded the master zip on github. aded it to plugin folder in my local installation, activated it and get this message:

Gutenberg development mode requires files to be built. Run npm install to install dependencies, npm run build to build the files or npm run dev to build the files and watch for changes. Read the contributing file for more information.

Any other way to install it ?

[youknowriad]

The master zip is not a ready to use plugin, you need to build it first. If you want a ready to use plugin, see here https://danielbachhuber.com/2018/10/02/gutenberg-nightly-build/

[Jojaba]

Thanks a lot youknowriad!
Got it and installed it! Works fine ;)
Regards