duts2020

Hi @dizzyatinnocraft,

In my case the issue hasn’t been fixed with your latest 5.2.2 release.

@dizzyatinnocraft,

Yes, I still have the same issue.

@dizzyatinnocraft,

Thank you for your help. I will try to find the cause of the issue myself later on. I will post the result here.

@dizzyatinnocraft, deactivation of page-optimize plugin doesn’t solve the issue.

In terms of changes, no there were no major changes. The same theme has been used for years.

              # Matomo

• Matomo Plugin Version: 5.1.2
• Config exists and is writable.: Yes (“$WP_CONTENT_DIR//uploads/matomo/config/config.ini.php” )
• JS Tracker exists and is writable.: Yes (“$WP_CONTENT_DIR//uploads/matomo/matomo.js” )
• Plugin directories: Yes ([{“pluginsPathAbsolute”:”\/srv\/htdocs\/wp-content\/plugins\/matomo\/plugins”,”webrootDirRelativeToMatomo”:”..\/plugins”}])
• Tmp directory writable: Yes ($WP_CONTENT_DIR//cache/matomo)
• Matomo Version: 5.1.0
• Matomo Blog idSite: 1
• Matomo Install Version: 1.2.0 (Install date: 2020-08-13 22:16:11)
• Upgrades outstanding: No
• 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 time: 2024-07-20 05:16:57
• Blog time: 2024-07-20 01:16:57 (Below dates are shown in blog timezone)
• Sync users & sites: Next run: 2024-07-20 22:16:10 (20 hours 59 min) ( Last started: 2024-07-19 22:16:21 (-3 hours 0 min). Last ended: 2024-07-19 22:16:21 (-3 hours 0 min). Interval: daily)
• Archive: Next run: 2024-07-20 02:16:10 (59 min 13s) ( Last started: 2024-07-20 01:16:37 (-20s). Last ended: 2024-07-20 01:16:38 (-19s). Interval: hourly)
• Update GeoIP DB: Next run: 2024-07-23 22:16:10 (3 days 20 hours) ( Last started: 2024-06-23 22:16:21 (-26 days 3 hours). Last ended: 2024-06-23 22:16:23 (-26 days 3 hours). Interval: matomo_monthly)

Mandatory checks

• PHP version >= 7.2.5: ok
• PDO extension: ok
• PDO\MYSQL extension: ok
• MYSQLI extension: ok
• Other required extensions: ok
• Required functions: ok
• Required PHP configuration (php.ini): ok
• Directories with write access: ok
• Directories with write access for Tag Manager: ok

Optional checks

• 64-bit PHP Binary: ok
• Tracker status: ok
• Memory limit: ok
• Time zone: ok
• Open URL: ok
• GD > 2.x + FreeType (graphics): ok
• Other extensions: ok
• Other functions: ok
• Filesystem: ok
• Last Successful Archiving Completion: ok
• Warning Database abilities: warning (UTF8mb4 charset Your database supports utf8mb4 charset, but your database tables have not been converted yet. You can do this by executing the command $WP_CONTENT_DIR//plugins/matomo/app/console core:convert-to-utf8mb4 or activating the automatic conversion in General Settings. This is required to be able to store 4-byte UTF8 characters. Unless utf8mb4 is available special characters, such as emojis, less common characters of asian languages, various historic scripts or mathematical symbols will be replaced with ?. You can read more details about this topic in this FAQ. CREATE TEMPORARY TABLES Changing transaction isolation level Your database version indicates you might be using a MariaDb server. If this is the case, please ensure to set [database] schema = Mariadb in the “config/config.ini.php” file, to ensure all database feature work as expected. )
• Max Packet Size: ok
• Geolocation: ok
• Update over 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
• Warning Proxy header: HTTP_X_FORWARDED_FOR (A proxy header is set which means you maybe need to configure a proxy header in the Advanced settings to make location reporting work. If the location in your reports is detected correctly, you can ignore this warning. Learn more)
• Had visit in last 5 days: Yes
• Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app)
• Warning YML files should not be accessible: warning (The .yml files in the wp-content/plugins/matomo/app/vendor directory are accessible from the internet. This can cause some web security tools to flag your website as suspicious. If you are using Apache, it is probably due to your server configuration disabling the use of .htaccess files. If you are instead using nginx, it is due to your nginx configuration allowing .yml files. You may need to contact your hosting provider to fix this.)

Matomo Settings

• Track mode: default
• Track ecommerce: Yes
• Track codeposition: footer
• Track api endpoint: default
• Track js endpoint: default
• Last tracking settings update: 1597433732
• Last settings update: 1597433732
• Version history: 5.1.2, 5.1.1, 5.1.0, 5.0.8, 5.0.6
• Core version: 5.1.0

Logs

• Warning archive_main: 2024-07-19 22:16:22 (1 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:473; CronArchive.php:468; CronArchive.php:226; Access.php:567; CronArchive.php:230; ScheduledTasks.php:371; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
• Warning archive_errors: 2024-07-19 22:16:23 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2024-01-01&format=json&trigger=archivephp. Response was \'{“result”:”error”,”message”:”The unserialization has failed! – in plugin Actions.”}\” ‘1 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:385; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
• Warning archive_main: 2024-07-19 23:19:28 (1 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:473; CronArchive.php:468; CronArchive.php:226; Access.php:567; CronArchive.php:230; ScheduledTasks.php:371; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
• Warning archive_errors: 2024-07-19 23:19:28 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2024-01-01&format=json&trigger=archivephp. Response was \'{“result”:”error”,”message”:”The unserialization has failed! – in plugin Actions.”}\” ‘1 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:385; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
• Warning archive_main: 2024-07-20 01:16:37 (1 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:473; CronArchive.php:468; CronArchive.php:226; Access.php:567; CronArchive.php:230; ScheduledTasks.php:371; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)
• Warning archive_errors: 2024-07-20 01:16:38 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2024-01-01&format=json&trigger=archivephp. Response was \'{“result”:”error”,”message”:”The unserialization has failed! – in plugin Actions.”}\” ‘1 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:385; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)

WordPress

• Home URL: $site_url
• Site URL: $site_url
• WordPress Version: 6.6
• Number of blogs: 1
• Multisite Enabled: No
• Network Enabled: No
• WP_DEBUG: No
• WP_DEBUG_DISPLAY: No
• WP_DEBUG_LOG: No
• DISABLE_WP_CRON: –
• FORCE_SSL_ADMIN: No
• WP_CACHE: Yes
• CONCATENATE_SCRIPTS: –
• COMPRESS_SCRIPTS: –
• COMPRESS_CSS: –
• ENFORCE_GZIP: –
• WP_LOCAL_DEV: –
• WP_CONTENT_URL: $site_url/wp-content
• WP_CONTENT_DIR: $WP_CONTENT_DIR/
• 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: /%year%/%monthnum%/%day%/%postname%/
• Possibly uses symlink: No
• Upload base url: $site_url/wp-content/uploads
• Upload base dir: $WP_CONTENT_DIR//uploads
• Upload url: $site_url/wp-content/uploads/2024/07
• Custom upload_path:
• Custom upload_url_path:
• Compatible content directory: Yes
• WP_Filesystem Initialized: Yes

WordPress Plugins MU Plugins

• Health Check Troubleshooting Mode: 1.9.1
• wpcomsh-loader.php:

Plugins

• Ads.txt & App-ads.txt Manager: 1.1.7.1
• Akismet Anti-spam: Spam Protection: 5.3.3
• All-in-One Video Gallery: 3.7.1
• All-in-One Video Gallery (Premium): 3.7.1
• AMP: 2.5.4
• Attachment Pages Redirect: 1.1.2
• Classic Editor: 1.6.3
• CoBlocks: 3.1.12
• Disable WP Sitemaps: 1.8.3
• Elementor: 3.23.1
• Elementor Header & Footer Builder: 1.6.37
• Envato Elements: 2.0.13
• Footer Putter: 1.17
• Gutenberg: 18.7.1
• Health Check & Troubleshooting: 1.7.0
• Jetpack: 13.7-a.3
• Layout Grid: 1.8.4
• Matomo Analytics – Ethical Stats. Powerful Insights.: 5.1.2
• Newsletter: 8.4.7
• Newsletter – Addons Manager and Support: 1.2.8
• OneSignal Push Notifications: 2.4.4
• Open Graph and Twitter Card Tags: 3.3.3
• Page Optimize: 0.5.5
• Sassy Social Share: 3.3.64
• Simple Noarchive: 1.0
• Simple Yearly Archive: 2.2.2
• Site Kit by Google: 1.131.0
• Virtual Robots.txt: 1.10
• Widget Options: 4.0.6.1
• WordPress.com Editing Toolkit: 4.28277
• WP-Optimize – Clean, Compress, Cache: 3.4.2
• WPCode Lite: 2.2.0
• WP Rollback: 2.0.7
• XML Sitemap & Google News: 5.4.9
• XML Sitemap Generator for Google: 2.0.7
• Active Plugins: 31 (akismet:5.3.3 all-in-one-video-gallery-premium:3.7.1 app-ads-txt:1.1.7.1 attachment-pages-redirect:1.1.2 classic-editor:1.6.3 coblocks:3.1.12 disable-wp-sitemaps:1.8.3 elementor:3.23.1 envato-elements:2.0.13 footer-putter:1.17 full-site-editing:4.28277 google-site-kit:1.131.0 gutenberg:18.7.1 header-footer-elementor:1.6.37 health-check:1.7.0 insert-headers-and-footers:2.2.0 jetpack:13.7-a.3 layout-grid:1.8.4 matomo:5.1.2 newsletter-extensions:1.2.8 newsletter:8.4.7 onesignal-free-web-push-notifications:2.4.4 page-optimize:0.5.5 pc-robotstxt:1.10 sassy-social-share:3.3.64 simple-noarchive:1.0 simple-yearly-archive:2.2.2 wonderm00ns-simple-facebook-open-graph-tags:3.3.3 wp-rollback:2.0.7 www-xml-sitemap-generator-org:2.0.7 xml-sitemap-feed:5.4.9)
• Theme: twentytwenty (twentytwenty)

Server

• Server Info: nginx
• PHP OS: Linux
• PHP Version: 8.1.29
• PHP SAPI: fpm-fcgi
• PHP Binary Name: /root/roles/nginx-php/usr/local/php8.1/bin.buster/php-fpm
• PHP Maxmind DB extension: Not loaded
• PHP Error Reporting: 4437 After bootstrap: 4437
• Timezone: UTC
• WP timezone: America/New_York
• Locale: ru_RU
• User Locale: en_US
• Memory Limit: 512M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
• WP Memory Limit: 512M
• WP Max Memory Limit: 512M
• Timezone version: 2023.3
• Time: 1721452617
• Max Execution Time: 1200
• Max Post Size: 2047M
• Max Upload Size: 2146435072
• Max Input Vars: 6144
• Disabled PHP functions: No
• zlib.output_compression is off: Yes
• Curl Version: 8.7.1, OpenSSL/1.1.1n
• Suhosin installed: No

PHP cli

• PHP CLI Version: (The detected PHP CLI version does not match the PHP web version. To avoid archiving errors, enable archiving via HTTP requests, or manually set the path to your PHP CLI executable to the one for PHP version 8.1.29.)
• MySQLi support: missing (Your PHP cli does not load the MySQLi extension. You might have archiving problems in Matomo but also others problems in your WordPress cron tasks. You should enable this extension)

Database

• MySQL Version: 10.4.26
• Mysqli Connect: Yes
• Force MySQL over Mysqli: No
• DB Prefix: wp_
• DB CHARSET: latin1
• DB COLLATE: latin1_swedish_ci
• SHOW ERRORS: No
• SUPPRESS ERRORS: No
• Uses Socket: No
• Uses IPv6: No
• Matomo tables found: 207
• DB tables exist: Yes
• Matomo users found: 1
• Matomo sites found: 1
• Required permissions: OK

Browser

• Browser: (Mozilla/5.0 (Windows NT 10.0; rv:109.0) Gecko/20100101 Firefox/115.0)
• Language: en-us,en

Hi,
I rolled back to previous version and everything is back to normal for me. I had to disable automatic updates and would wait for a more stable version.

Hi michellei,
I had a chance to talk to WordPress’ customer support regarding this issue. Lately, they have been having issues with .mp4 after encoding. Files loose sound after encoding and in order to fix it they switched to .m3u8 format.
I am unable to add video file from my Library using your video block because this particular format is not supported.
It is my understanding that you either have to add the support for .m3u8 format or post a workaround guidelines which would help in this situation. For now, I can’t use Elementor’s video block to add files from my library with .m3u8 format.
You can reach WordPress’ customer service department for more info regarding this.

Yes, I meant that sitemap. I have disabled all options except for creating two sitemaps- one for posts and the other one for videos. Everything else is compensated by sitemaps created by your plugin.
Your plugin is showing the correct time and I am not sure why the other plugin is not showing the same. In any case, it shouldn’t be the reason to cause any issues

Hi RavanH,
Yes, I agree that everything should be working but in my case somehow it doesn’t. For me there is no need to test the plugin you have mentioned since I am already using another plugin that supports video sitemap. The sitemap is not dropping in that case, at least for now.
I will mention one more strange behavior that might help you in the future to update the plugin. Right now my video posts are split into two sitemaps which are sorted by year, namely:
https://arbalettv.com/sitemap-posttype-aiovg_videos.2020.xml
https://arbalettv.com/sitemap-posttype-aiovg_videos.2021.xml

At the same time the following sitemap is also fully accessible:
https://arbalettv.com/sitemap-posttype-aiovg_videos.xml

When I add this sitemap along with two others (sorted by the year) it is not dropped(only this sitemap) for some videos. The other videos drop all these sitemaps after 5-6 hours. It is very strange.

RavanH.
August 23, 2021 update.
I have tested an option not to split video URLs into sitemaps by year. All videos now contained in one sitemap – https://arbalettv.com/sitemap-posttype-aiovg_videos.xml
The results are the following: the vast majority of videos did not list this sitemap or its parent – https://arbalettv.com/sitemap.xml when the URL inspection tool in run. Several videos listed these sitemaps for 5-6 hours and then dropped.
The whole issue is somehow connected to the video sitemaps. If I do not split the sitemap by year then it’s basically non operational for me.

RavanH,
I have tested Custom sitemap using 4 URLs -two regular posts and two videos. The results are the following:
1) Both video pages dropped the Custom sitemap after 4-5 hours. They also dropped the https://arbalettv.com/sitemap-posttype-aiovg_videos.2021.xml and https://arbalettv.com/sitemap.xml i.e. the whole hierarchy.
2) One regular post kept all three sitemaps including the Custom sitemap. The other regular post dropped just the Custom sitemap but kept https://arbalettv.com/sitemap-posttype-post.2021.xml and https://arbalettv.com/sitemap.xml
The only difference between these two regular posts is that one contained a photo and the other one didn’t. It was plain text. The post that contained the photo only dropped the Custom sitemap.

I have added some videos and posts before the issue was noticed. A few of the additional links were added for testing purposes later on.
The only pages that are affected listed in the following sitemaps:
https://arbalettv.com/sitemap-posttype-aiovg_videos.2020.xml
https://arbalettv.com/sitemap-posttype-aiovg_videos.2021.xml

The sitemaps are dropped after 4-5 hours only for URLs listed in those just mentioned sitemaps. The vast majority of links were not added to the Custom sitemap so that couldn’t be a cause of this issue. I can clear this Custom sitemap but I don’t think it would have any effect.

The pages listed in the above-listed two sitemaps are considered custom post type pages (videos).

So far I haven’t find a clue in regards to the potential cause of this issue. If the URL inspection tool lists the sitemaps for any particular page then why they are dropped after 4-5 hours or sometimes a bit longer? This doesn’t make any sense. I can only think about one thing: at the end of July Google had issued a spam update. I have started to see the issue with those sitemaps on or around the time of this update. At the same time, I have nothing to do with spam but very frequently Google updates are causing variety of different issues.

I have some additional information for you. My sitemap – https://arbalettv.com/sitemap.xml
The regular type posts are not affected by the issue I have described and when you run the URL Inspection tool the sitemaps are never dropped.
The only affected pages are video pages recorded in the following sitemaps:
https://arbalettv.com/sitemap-posttype-aiovg_videos.2020.xml
https://arbalettv.com/sitemap-posttype-aiovg_videos.2021.xml
When you run URL inspection tool for any page recorded in those sitemaps the sitemaps itself are dropped after 5-6 hours. The video pages are considered Custom Post Type pages.
I have narrowed down the issue.
Please let me know if you find anything.

RavanH,
As I have mentioned before I have been using the second set of sitemaps generated via another plugin. I have had indexing issues/crawling issues and I couldn’t find the reason. Then I found out that your sitemaps were dropped and the discovery section was empty. I have added another set of sitemaps via different plugin and they are not dropping. The issues with indexing and crawling have cleared once I added additional sitemaps. Now I am trying to figure out why your sitemaps are dropping in the first place because until the end of July everything worked more or less normally. I have schema markup for video pages and I have had issues when Google failed to show my thumbnail and was showing my site’s logo instead. I researched all the possible reasons and found that those pages were re-crawled and re-indexed when the sitemaps were dropped and the discovery section was empty. This is very strange issue. I have added a second set of sitemaps and re-crawled and re-indexed the pages which are not showing the correct schema thumbnail. All these attempts to figure out the issue have led me to the fact that your sitemaps are dropping off from the discovery section for no apparent reason and when this is happening the pages are experiencing issues with crawling and indexing.

Since the other plugin’s sitemaps are not being dropped and I have tested at least 3 other plugins so far (including Jetpack’s sitemaps) then I guess it’s reasonable to suggest that there is some sort of conflict between Google and sitemaps created by your plugin.The URL inspection tool is supposed to remember the information read at the time of the test.

• This reply was modified 3 years, 7 months ago by duts2020.