Title: Archive isn’t working
Last modified: February 12, 2024

---

# Archive isn’t working

 *  Resolved [cassi0712](https://wordpress.org/support/users/cassi0712/)
 * (@cassi0712)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/archive-isnt-working/)
 * Hello, since Friday the archive system isn’t working. The Status shows this:
 * >     ```wp-block-code
   >                   # Errors
   >     ```
   > 
   >  - Error Letzter erfolgreicher Abschluss der Archivierung: error (Die Archivierung
   >    ist zuletzt am Freitag, 9. Februar 2024 06:01:16 erfolgreich gelaufen, also
   >    vor 3 Tage 02:58:05 )
   >  - Error plugin_update: 2024-02-12 09:53:26 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; ScheduledTasks.php:195; ScheduledTasks.
   >    php:276; SystemReport.php:179; SystemReport.php:321; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; admin.php:259;)
   >  - Error plugin_update: 2024-02-12 09:57:04 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34;)
   >  - Error plugin_update: 2024-02-12 09:57:28 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34; plugins.php:10;)
   >  - Error plugin_update: 2024-02-12 09:57:40 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34; plugin-install.php:16;)
   >  - Error plugin_update: 2024-02-12 09:59:21 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34;)
   > Matomo
   >  - Matomo-Plugin-Version: 5.0.3
   >  - Config existiert und ist schreibbar.: Ja (“$abs_path/wp-content/uploads/
   >    matomo/config/config.ini.php” )
   >  - JS Tracker existiert und ist schreibbar.: Ja (“$abs_path/wp-content/uploads/
   >    matomo/matomo.js” )
   >  - Plugin-Verzeichnisse: Yes ([{“pluginsPathAbsolute”:”$abs_path\/wp-content\/
   >    plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/plugins”}])
   >  - Tmp-Verzeichnis schreibbar: Yes ($abs_path/wp-content/cache/matomo)
   >  - Matomo-Version: 5.0.2
   >  - Matomo Blog idSite: 1
   >  - Installierte Matomo-Version: 4.6.0 (Install date: 2022-01-18 15:01:05)
   >  - Upgrades outstanding: Yes ({“matomo-plugin-version-matomo”:”5.0.3″})
   >  - Upgrade in progress: No
   > Endpoints
   >  - Matomo JavaScript Tracker URL: ($site_url/wp-content/uploads/matomo/matomo.
   >    js)
   >  - Matomo JavaScript Tracker – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
   >  - Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.
   >    php)
   >  - Matomo HTTP Tracking API – WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
   > Crons
   >  - Server-Zeit: 2024-02-12 08:59:21
   >  - Blog-Zeit: 2024-02-12 09:59:21 (Die nachfolgenden Daten werden in der Blog-
   >    Zeitzone angezeigt)
   >  - Sync users & sites: Next run: 2024-02-12 15:02:03 (5 Stunden 2 Minuten) (
   >    Last started: 2024-02-11 15:02:05 (-18 Stunden 57 Minuten). Last ended: 
   >    2024-02-11 15:02:06 (-18 Stunden 57 Minuten). Interval: daily)
   >  - Archive: Next run: 2024-02-12 10:01:05 (1 Minuten 44s) ( Last started: 2024-
   >    02-12 09:01:39 (-57 Minuten 42s). Last ended: 2024-02-12 09:01:40 (-57 Minuten
   >    41s). Interval: hourly)
   >  - Update GeoIP DB: Next run: 2024-03-08 15:01:45 (25 Tage 5 Stunden) ( Last
   >    started: 2024-02-07 15:02:37 (-4 Tage 18 Stunden). Last ended: 2024-02-07
   >    15:02:39 (-4 Tage 18 Stunden). Interval: matomo_monthly)
   > Vorgeschriebene Prüfungen
   >  - PHP-Version >= 7.2.5: ok
   >  - PDO Erweiterung: ok
   >  - PDO\MYSQL Erweiterung: ok
   >  - MYSQLI Erweiterung: ok
   >  - Weitere erforderliche Anforderungen: ok
   >  - Erforderliche Funktionen: ok
   >  - Benötigte PHP Konfiguration (php.ini): ok
   >  - Verzeichnisse mit Schreibzugriff: ok
   >  - Verzeichnisse mit Schreibzugriff auf Tag Manager: ok
   > Optionale Prüfungen
   >  - 64-bit PHP Binär: ok
   >  - Tracker-Status: ok
   >  - Speicherlimit: ok
   >  - Zeitzone: ok
   >  - Öffnen einer URL: ok
   >  - GD > 2.x + FreeType (Grafiken): ok
   >  - Andere Erweiterungen: ok
   >  - Andere Funktionen: ok
   >  - Dateisystem: ok
   >  - Error Letzter erfolgreicher Abschluss der Archivierung: error (Die Archivierung
   >    ist zuletzt am Freitag, 9. Februar 2024 06:01:16 erfolgreich gelaufen, also
   >    vor 3 Tage 02:58:05 )
   >  - Datenbankfähigkeiten: ok
   >  - Maximale Packetgröße: ok
   >  - Standorterkennung: ok
   >  - Update über HTTPS: ok
   >  - Mobile Messaging SMS Provider: ok
   >  - Supports Async Archiving: No
   >  - Async Archiving Disabled in Setting: No
   >  - Location provider ID: geoip2php
   >  - Location provider available: Yes
   >  - Location provider working: Yes
   >  - Had visit in last 5 days: Yes
   >  - Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)
   > Matomo Settings
   >  - Track mode: default
   >  - Track ecommerce: Yes
   >  - Track codeposition: footer
   >  - Track api endpoint: default
   >  - Track js endpoint: default
   >  - Version history: 5.0.3, 4.15.3, 4.15.2, 4.15.1, 4.15.0
   >  - Core version: 5.0.2
   >  - Last tracking settings update: 1692115549
   >  - Last settings update: 1692115549
   >  - Disable cookies: Yes
   >  - Mail history: 2024-02-05 00:02:14, 2024-01-29 00:02:12, 2024-01-22 00:01:
   >    26
   >  - Show get started page: 0
   > Logs
   >  - Error plugin_update: 2024-02-12 09:53:26 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; ScheduledTasks.php:195; ScheduledTasks.
   >    php:276; SystemReport.php:179; SystemReport.php:321; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; admin.php:259;)
   >  - Warning archive_main: 2024-02-12 09:53:26 (WP DB Error: [1054] Unknown column‘
   >    secure_only’ in ‘where clause’ SQL: SELECT * FROM wp_matomo_user_token_auth
   >    WHERE `password` = ? AND (date_expired is null or date_expired > ?) AND 
   >    secure_only = 0 => WordPress.php:407; WordPress.php:449; Model.php:309; 
   >    Model.php:411; Model.php:231; Piwik.php:300; CliMulti.php:390; CliMulti.
   >    php:335; CliMulti.php:165; CliMulti.php:149; CliMulti.php:374; CliMulti.
   >    php:102; CronArchive.php:379; CronArchive.php:321; CronArchive.php:225; 
   >    Access.php:560; CronArchive.php:231; ScheduledTasks.php:338; SystemReport.
   >    php:179; SystemReport.php:321; class-wp-hook.php:324; class-wp-hook.php:
   >    348; plugin.php:517; admin.php:259;)
   >  - Error plugin_update: 2024-02-12 09:57:04 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34;)
   >  - Error plugin_update: 2024-02-12 09:57:28 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34; plugins.php:10;)
   >  - Error plugin_update: 2024-02-12 09:57:40 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34; plugin-install.php:16;)
   >  - Error plugin_update: 2024-02-12 09:59:21 (Please reach out to us and include
   >    the copied system report ([more info](https://matomo.org/faq/wordpress/how-do-i-troubleshoot-a-failed-database-upgrade-in-matomo-for-wordpress/))
   >    
   >    You can also retry the update manually by clicking in the top on the “Troubleshooting”
   >    tab and then clicking on the “Run updater” button.Error while updating components:
   >    $abs_path/wp-content/plugins/matomo/app/core/Updates/5.0.0-b1.php:Error 
   >    trying to execute the migration ‘ALTER TABLE `wp_matomo_log_conversion` 
   >    ADD COLUMN `pageviews_before` SMALLINT UNSIGNED DEFAULT NULL;’.The error
   >    was: WP DB Error: [1118] Row size too large. The maximum row size for the
   >    used table type, not counting BLOBs, is 8126. This includes storage overhead,
   >    check the manual. You have to change some columns to TEXT or BLOBs SQL: 
   >    ALTER TABLE `wp_matomo_log_conversion` ADD COLUMN `pageviews_before` SMALLINT
   >    UNSIGNED DEFAULT NULL => Updater.php:247; Updater.php:147; Access.php:560;
   >    Updater.php:149; Updater.php:88; WpMatomo.php:218; class-wp-hook.php:324;
   >    class-wp-hook.php:348; plugin.php:517; wp-settings.php:643; wp-config.php:
   >    89; wp-load.php:50; admin.php:34;)
   > WordPress
   >  - Home URL: $site_url
   >  - Site URL: $site_url
   >  - WordPress Version: 6.4.3
   >  - Number of blogs: 1
   >  - Multisite Enabled: No
   >  - Network Enabled: No
   >  - WP_DEBUG: No
   >  - WP_DEBUG_DISPLAY: Yes
   >  - WP_DEBUG_LOG: No
   >  - DISABLE_WP_CRON: –
   >  - FORCE_SSL_ADMIN: Yes
   >  - WP_CACHE: Yes
   >  - CONCATENATE_SCRIPTS: –
   >  - COMPRESS_SCRIPTS: –
   >  - COMPRESS_CSS: –
   >  - ENFORCE_GZIP: –
   >  - WP_LOCAL_DEV: –
   >  - WP_CONTENT_URL: $site_url/wp-content
   >  - WP_CONTENT_DIR: $abs_path/wp-content
   >  - UPLOADS: –
   >  - BLOGUPLOADDIR: –
   >  - DIEONDBERROR: –
   >  - WPLANG: –
   >  - ALTERNATE_WP_CRON: –
   >  - WP_CRON_LOCK_TIMEOUT: 60
   >  - WP_DISABLE_FATAL_ERROR_HANDLER: –
   >  - MATOMO_SUPPORT_ASYNC_ARCHIVING: –
   >  - MATOMO_ENABLE_TAG_MANAGER: –
   >  - MATOMO_SUPPRESS_DB_ERRORS: –
   >  - MATOMO_ENABLE_AUTO_UPGRADE: –
   >  - MATOMO_DEBUG: –
   >  - MATOMO_SAFE_MODE: –
   >  - MATOMO_GLOBAL_UPLOAD_DIR: –
   >  - MATOMO_LOGIN_REDIRECT: –
   >  - Permalink Structure: /%postname%/
   >  - Possibly uses symlink: No
   >  - Upload base url: $site_url/wp-content/uploads
   >  - Upload base dir: $abs_path/wp-content/uploads
   >  - Upload url: $site_url/wp-content/uploads/2024/02
   >  - Custom upload_path:
   >  - Custom upload_url_path:
   >  - Compatible content directory: Yes
   > WordPress Plugins
   >  - AI Engine: 2.1.9
   >  - Auto Publish for Google My Business: 3.10
   >  - Business Hours Indicator: 2.4
   >  - Code Snippets: 3.6.2
   >  - Germanized for WooCommerce: 3.15.6
   >  - Legal Text Connector of the IT-Recht Kanzlei: 1.0.8
   >  - Loco Translate: 2.6.6
   >  - MailPoet: 4.43.0
   >  - Matomo Analytics – Ethical Stats. Powerful Insights.: 5.0.3
   >  - Media Cleaner: 6.7.2
   >  - Ninja Forms: 3.7.2
   >  - PDF Invoices & Packing Slips for WooCommerce: 3.7.7
   >  - Product Feed ELITE for WooCommerce: 4.5.6
   >  - Rank Math SEO: 1.0.212.1
   >  - Rank Math SEO PRO: 3.0.55
   >  - Real Cookie Banner: 4.4.1
   >  - Super Progressive Web Apps: 2.2.23.1
   >  - UpdraftPlus – Backup/Restore: 1.23.16
   >  - Variation Swatches for WooCommerce: 2.0.30
   >  - Variation Swatches for WooCommerce – Pro: 2.0.30
   >  - WooCommerce: 8.5.2
   >  - WooCommerce Amazon Pay: 2.5.1
   >  - WooCommerce Extended Coupon Features FREE: 3.3.3
   >  - WooCommerce PayPal Payments: 2.5.3
   >  - WooPayments: 7.1.0
   >  - Wordfence Security: 7.11.1 (Network enabled)
   >  - WP All Import – WooCommerce Import Add-On Pro: 4.0.0
   >  - WP All Import Pro: 4.8.5
   >  - WP Chat App: 3.6.1
   >  - WP Optin Wheel Pro: 4.1
   >  - WP Rocket: 3.15.9
   >  - YITH Request a Quote for WooCommerce: 2.29.0
   >  - Active Plugins: 32 (ai-engine:2.1.9 business-hours-indicator:2.4 code-snippets:
   >    3.6.2 legal-texts-connector-it-recht-kanzlei:1.0.8 loco-translate:2.6.6 
   >    mabel-wheel-of-fortune:4.1 mailpoet:4.43.0 matomo:5.0.3 media-cleaner:6.7.2
   >    ninja-forms:3.7.2 real-cookie-banner-pro:4.4.1 seo-by-rank-math-pro:3.0.55
   >    seo-by-rank-math:1.0.212.1 super-progressive-web-apps:2.2.23.1 updraftplus:
   >    1.23.16 woo-product-feed-elite:4.5.6 woo-variation-swatches-pro:2.0.30 woo-
   >    variation-swatches:2.0.30 woocommerce-auto-added-coupons:3.3.3 woocommerce-
   >    gateway-amazon-payments-advanced:2.5.1 woocommerce-germanized:3.15.6 woocommerce-
   >    payments:7.1.0 woocommerce-paypal-payments:2.5.3 woocommerce-pdf-invoices-
   >    packing-slips:3.7.7 woocommerce:8.5.2 wordfence:7.11.1 wp-all-import-pro:
   >    4.8.5 wp-google-my-business-auto-publish:3.10 wp-rocket:3.15.9 wp-whatsapp:
   >    3.6.1 wpai-woocommerce-add-on:4.0.0 yith-woocommerce-request-a-quote:2.29.0)
   >  - Warning Nicht kompatible Plugins: 1 (wp-rocket Matomo may work fine when
   >    using these plugins but there may be some issues. For more information See
   >    [this FAQ](https://matomo.org/faq/wordpress/which-plugins-is-matomo-for-wordpress-known-to-be-not-compatible-with/)
   >    WP-Rocket is incompatible from version 3.12. Until fixes, please reinstall
   >    version 3.11.5 if you have a newer version. For more information please 
   >    visit [How to downgrade Wp-rocket to be compatible with Matomo](https://github.com/matomo-org/matomo-for-wordpress/wiki/Downgrade-wp-rocket-to-a-version-compatible-with-the-Matomo-plugin))
   >  - Theme: flatsome (flatsome)
   > Server
   >  - Server Info: Apache
   >  - Apache AddHandler support: Supported
   >  - PHP OS: Linux
   >  - PHP Version: 8.1.27
   >  - PHP SAPI: cgi-fcgi
   >  - PHP Binary Name: /opt/php-8.1/bin/php-cgi
   >  - PHP Maxmind DB extension: Not loaded
   >  - PHP Error Reporting: 4437 After bootstrap: 4437
   >  - PHP Found Binary: /usr/bin/php -q
   >  - Timezone: UTC
   >  - WP timezone: Europe/Berlin
   >  - Locale: de_DE
   >  - User Locale: de_DE
   >  - Memory Limit: 512M (At least 128MB recommended. Depending on your traffic
   >    256MB or more may be needed.)
   >  - WP Memory Limit: 256M
   >  - WP Max Memory Limit: 512M
   >  - Timezone version: 2023.3
   >  - Time: 1707728363
   >  - Max Execution Time: 0
   >  - Max Post Size: 512M
   >  - Max Upload Size: 268435456
   >  - Max Input Vars: 7500
   >  - Disabled PHP functions: Yes (show_source, highlight_file, apache_child_terminate,
   >    apache_get_modules, apache_note, apache_setenv, virtual, dl, disk_total_space,
   >    posix_getpwnam, posix_getpwuid, posix_mkfifo, posix_mknod, posix_setpgid,
   >    posix_setsid, posix_setuid, posix_uname, proc_nice, openlog, syslog, pfsockopen)
   >  - zlib.output_compression is off: Yes
   >  - Curl Version: 7.74.0, OpenSSL/1.1.1w
   >  - Suhosin installed: No
   > PHP cli
   >  - PHP cli Version: 7.4.33
   >  - MySQLi support: ok
   > Database
   >  - MySQL Version: 10.5.23
   >  - Mysqli Connect: Yes
   >  - Force MySQL over Mysqli: No
   >  - DB Prefix: wp_
   >  - DB CHARSET: utf8
   >  - DB COLLATE:
   >  - SHOW ERRORS: No
   >  - SUPPRESS ERRORS: No
   >  - Uses Socket: No
   >  - Uses IPv6: No
   >  - Matomo tables found: 152
   >  - DB tables exist: Yes
   >  - Matomo users found: 1
   >  - Matomo sites found: 1
   >  - Erforderliche Berechtigungen: OK
   > Browser
   >  - Browser: (Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML,
   >    like Gecko) Chrome/120.0.0.0 Safari/537.36)
   >  - Language: de-de,de,en-us,en
 * Any idea?
 * Best Regards
 * Andreas
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Farchive-isnt-working%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Plugin Support [dizzyatinnocraft](https://wordpress.org/support/users/dizzyatinnocraft/)
 * (@dizzyatinnocraft)
 * [2 years, 3 months ago](https://wordpress.org/support/topic/archive-isnt-working/#post-17419921)
 * Hi [@cassi0712](https://wordpress.org/support/users/cassi0712/), the database
   is using an older row format which is causing problems with the upgrade. Can 
   you ask your hosting provider for instructions on how to change the row format
   of the database tables to ‘Dynamic’?
 *  Plugin Support [emermatomo](https://wordpress.org/support/users/emermatomo/)
 * (@emermatomo)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/archive-isnt-working/#post-17435063)
 * Hey [@cassi0712](https://wordpress.org/support/users/cassi0712/). Have you already
   had a look at our last comment or maybe any question about it?
 *  Plugin Support [emermatomo](https://wordpress.org/support/users/emermatomo/)
 * (@emermatomo)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/archive-isnt-working/#post-17452033)
 * Hi [@cassi0712](https://wordpress.org/support/users/cassi0712/) As we didn’t 
   receive a response after 1 week, we’re marking this issue as resolved. If something
   is not working, feel free to leave a comment and we’d be happy to assist.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Archive isn’t working’ is closed to new replies.

 * ![](https://ps.w.org/matomo/assets/icon-256x256.png?rev=3531741)
 * [Matomo Analytics - Powerful, Privacy-First Insights for WordPress](https://wordpress.org/plugins/matomo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/matomo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/matomo/)
 * [Active Topics](https://wordpress.org/support/plugin/matomo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/matomo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/matomo/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [emermatomo](https://wordpress.org/support/users/emermatomo/)
 * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/archive-isnt-working/#post-17452033)
 * Status: resolved