v3.0.0 Critical Error
-
Version 3.0.0 (latest update) causes a critical error:
An error of type E_COMPILE_ERROR was caused in line 14 of the file /home/XXXXXX/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php. Error message: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use
-
Hi @rjadev, thanks for getting in touch and sharing the error message. To help you look into this further, please can you share the following:
- Your Site Health information which will help us to see if anything obvious stands out from your setup.
- Do you encounter the same when accessing from an Incognito window?
- Where do you encounter this error?
Once you have shared the above I can perform some checks on my side to see if I can see what the cause is. We can also try some troubleshooting steps if needed. Let me know if you have any questions at this time.
Hi @adamdunnage
Same problem here with a very old test installation (I had to manually disable performance-lab to access WP)
Here are my site health data:wp-core version: 6.5.2 site_language: en_US user_language: en_US timezone: +00:00 permalink: /%year%/%monthnum%/%day%/%postname%/ https_status: true multisite: false user_registration: 0 blog_public: 0 default_comment_status: open environment_type: production user_count: 1 dotorg_communication: true wp-paths-sizes wordpress_path: /home/xxxxxxxxxx/qqqqqqqqq wordpress_size: 96.74 MB (101434436 bytes) uploads_path: /home/xxxxxxxxxx/qqqqqqqqq/wp-content/uploads uploads_size: 2.15 MB (2253702 bytes) themes_path: /home/xxxxxxxxxx/qqqqqqqqq/wp-content/themes themes_size: 13.07 MB (13701238 bytes) plugins_path: /home/xxxxxxxxxx/qqqqqqqqq/wp-content/plugins plugins_size: 162.94 MB (170857544 bytes) database_size: 3.12 MB (3266369 bytes) total_size: 278.01 MB (291513289 bytes) wp-dropins (1) object-cache.php: true wp-active-theme name: Storefront (storefront) version: 4.5.5 author: Automattic author_website: https://woocommerce.com/ parent_theme: none theme_features: core-block-patterns, widgets-block-editor, post-thumbnails, automatic-feed-links, custom-logo, menus, html5, custom-background, custom-header, site-logo, title-tag, customize-selective-refresh-widgets, wp-block-styles, align-wide, editor-styles, editor-font-sizes, editor-style, responsive-embeds, amp, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, starter-content, widgets theme_path: /home/xxxxxxxxxx/qqqqqqqqq/wp-content/themes/storefront auto_update: Enabled wp-themes-inactive (3) Twenty Seventeen: version: 3.6, author: the WordPress team, Auto-updates enabled Twenty Twenty-Four: version: 1.1, author: the WordPress team, Auto-updates disabled Twenty Twenty-Three: version: 1.4, author: the WordPress team, Auto-updates disabled wp-plugins-active (7) Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd: version: 6.17.4, author: SeedProd, Auto-updates enabled Google Analytics for WooCommerce: version: 2.0.6, author: WooCommerce, Auto-updates enabled Loginizer: version: 1.8.4, author: Softaculous, Auto-updates enabled WooCommerce: version: 8.7.0, author: Automattic, Auto-updates enabled WooCommerce PayPal Checkout Gateway: version: 2.1.3, author: WooCommerce, Auto-updates enabled WooCommerce Shipping & Tax: version: 2.5.4, author: WooCommerce, Auto-updates enabled Yoast SEO: version: 22.5, author: Team Yoast, Auto-updates enabled wp-plugins-inactive (7) Akismet Anti-spam: Spam Protection: version: 5.3.2, author: Automattic - Anti-spam Team, Auto-updates enabled AWS for WordPress: version: 4.3.2, author: AWS Labs, WP Engine, Auto-updates enabled Hello Dolly: version: 1.7.2, author: Matt Mullenweg, Auto-updates enabled Performance Lab: version: 3.0.0, author: WordPress Performance Team, Auto-updates disabled WooCommerce Admin: version: 3.3.2, author: WooCommerce, Auto-updates enabled WooCommerce Blocks: version: 11.7.0, author: Automattic, Auto-updates enabled WooCommerce PayPal Payments: version: 2.6.1, author: WooCommerce, Auto-updates disabled wp-media image_editor: WP_Image_Editor_GD imagick_module_version: Not available imagemagick_version: Not available imagick_version: Not available file_uploads: 1 post_max_size: 8M upload_max_filesize: 2M max_effective_size: 2 MB max_file_uploads: 20 gd_version: 2.3.3 gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM ghostscript_version: 9.25 wp-server server_architecture: Linux 3.10.0-962.3.2.lve1.5.26.4.el7.x86_64 x86_64 httpd_software: Apache php_version: 8.1.22 64bit php_sapi: litespeed max_input_variables: 1000 time_limit: 30 memory_limit: 128M admin_memory_limit: 256M max_input_time: 60 upload_max_filesize: 2M php_post_max_size: 8M curl_version: 7.87.0 OpenSSL/1.1.1d suhosin: false imagick_availability: false pretty_permalinks: true htaccess_extra_rules: true current: 2024-04-17T06:43:36+00:00 utc-time: Wednesday, 17-Apr-24 06:43:36 UTC server-time: 2024-04-17T06:43:34+00:00 wp-database extension: mysqli server_version: 5.7.36-cll-lve client_version: 5.7.42 max_allowed_packet: 268435456 max_connections: 600 wp-constants WP_HOME: undefined WP_SITEURL: undefined WP_CONTENT_DIR: /home/xxxxxxxxxx/qqqqqqqqq/wp-content WP_PLUGIN_DIR: /home/xxxxxxxxxx/qqqqqqqqq/wp-content/plugins WP_MEMORY_LIMIT: 40M WP_MAX_MEMORY_LIMIT: 256M WP_DEBUG: false WP_DEBUG_DISPLAY: true WP_DEBUG_LOG: false SCRIPT_DEBUG: false WP_CACHE: false CONCATENATE_SCRIPTS: undefined COMPRESS_SCRIPTS: undefined COMPRESS_CSS: undefined WP_ENVIRONMENT_TYPE: Undefined WP_DEVELOPMENT_MODE: undefined DB_CHARSET: utf8mb4 DB_COLLATE: undefined wp-filesystem wordpress: writable wp-content: writable uploads: writable plugins: writable themes: writable
@ste18k Thanks for the input. Do you recall what version of the plugin you were using prior to upgrading?
Note also that there is an open GitHub issue in relation to this:
https://github.com/WordPress/performance/issues/1150Hi @jamesosborne
No I don’t know what version was installed before the upgrade (it’s a test installation and I didn’t login since months). I think auto-updates were enabled also for the performance-lab plugin (otherwise it could not have been updated to version 3.0).
If this information is important for you to debug the issue, later today I can try to restore a backup and check the exact version of the plugin. Just let me know if you need it or not.Appreciate the update @ste18k. I’ll perform some checks on this, while the team are aware as per the GitHub issue. I’ll certainly be in touch for additional insights. Thank you!
Same here, plugin from auto upgrade
This error causing my website inaccessible
[16-Apr-2024 03:29:26 UTC] PHP Fatal error: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use in /home/proz5825/public_html/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php on line 14 [16-Apr-2024 03:29:26 UTC] PHP Fatal error: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use in /home/proz5825/public_html/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php on line 14 [16-Apr-2024 04:51:29 UTC] PHP Fatal error: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use in /home/proz5825/public_html/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php on line 14 [16-Apr-2024 04:51:30 UTC] PHP Fatal error: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use in /home/proz5825/public_html/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php on line 14 [16-Apr-2024 06:05:11 UTC] PHP Fatal error: Cannot declare class Perflab_Server_Timing_Metric, because the name is already in use in /home/proz5825/public_html/wp-content/plugins/performance-lab/includes/server-timing/class-perflab-server-timing-metric.php on line 14
Sorry to hear that @masedinet. You can manually remove the plugin directory in order to restore access to your site. You’ll find it on a typical install at
wp-content/plugins/performance-lab
.After restoring access, it would be great if you could share your Site Health information here within this support topic. This may provide some further insights into any possible cause.
- The topic ‘v3.0.0 Critical Error’ is closed to new replies.