Timmmy

Hi Oliver,

I’ve offered to assist in updating the WordPress tested checks. Just bumped the version number with the test results.

Kind regards,

Timmmy

I need to correct the analysis.
It does not seem related to the child team at all…
Steps to reproduce: see above, just skip the child team step

Hi @barsha,

Any updates on this?
Just tested with 3.0.10, issue still seems to persist.

Kind regards,

Tim

Hi @vmarko,

Thanks for the quick reply!
Yeah that was a mistake, I was experimenting with redirection as a workaround but one of the wrong attempts got cached… Should have been fixed meanwhile…

Issue still persist. If I disable cache preload in W3TC, the entries do not show up anymore in the logs. If I change the time between checks, it clearly reflects in the logs. So quite sure it’s the W3TC page cache pre-load functionality that is causing these requests…

Kind regards,
Timmmy

Hi Barsha,

Any updates on this?
Issue still seems to present in 3.0.4…

Thanks in advance,

Timmmy

Hi @barsha04 ,

Just checking if you had any succes in replicating the issue…

Kind regards,

Timmmy

Hi @barsha04,

Sure, I just wanted to check if it’s a known issue to avoid spending a lot of time in troubleshooting a known issue.
I think I have some steps to reproduce

• Created a new site on wpsandbox.net with WP 6.0 and only Zakra installed.
• Installed and activated the child theme (How to add custom code to the theme using Child Theme? | Zakra Knowledgebase (zakratheme.com))
• Open the customizer and change the header typography to Open Sans (see first screenshot). Preview looks good.
• Publish the page and check: the font has changed (second screenshot)
• The computed font family is correctly set to Open Sans (screenshot 3), however the corresponding woff files are not loaded (screenshot 4)

Hope this provides enough information?

Thanks in advance,

Timmmy

Looks like a very persistent client side caching issue, but solved.

I might have found a pointer.

In my case the meta description of the affected page was empty. (It contained the standard page content field but because there was only the query loop on the page, it resulted in an empty string).
After putting some characters in, the page loads again.

Same issue for me, but not all themes seem to be affected. For example, the standard 2021 theme & Zakra have the issue but the 2023 theme doesn’t.

Steps to reproduce @wpsmort :
– In my case environment WP 6.2.2 and PHP 8.1
– Install AIOSEO (latest)
– Apply 2021 theme
– Make sure you have some posts.
– Create a page in Gutenberg, add a query loop over these post with a random layout.
– In the editor you see the preview of the posts.
– Publish the page. The published page is empty.

Delete either AIOSEO or switch to the 2023 theme to validate that the issue is gone.
If you want to check a page that is affected (but I’m testing some things at the moment to find a workaround: https://fiendedecker.be/in-de-media/ )

Hi all,

Quick update. Issue is unfortunately not solved yet.
However, I’ve found a workaround. Disabling the page header on the homepage removes the breadcrumbs and allows the page to pass validation without warnings.
The real cause of the issue is unfortunately still there.

Kind regards,
Tim

Hi @wpsmort @aurangajeb,

Thanks for the troubleshooting tips! (Did not know the troubleshooting plugin) Issue seems indeed to be caused by another plugin. With that plugin disabled it works.

Thanks for your help,

Timmmy

Hi @barsha04 ,

Issue unfortunately still exists after disabling other plugins. I’ve set-up a copy on another domain (https://test.uniekegeboortekaartjes.be) with all plugins disabled to allow further troubleshooting.

Please note that I’m not using Elementor.

Do you have any other ideas?

Thanks in advance,
Timmmy

Hi Barsha,

Apologies for the delays in response.
Disabling the breadcrumbs makes the error indeed disappear. I’m using the breadcrumbs from the theme. Please note that it worked without issue until Zakra 2.1.0
This is a screenshot of the error in the structured data test: https://i.postimg.cc/v8XSCjj5/image.png

Kind regards,

Timmmy

Hi @barsha04,

Issue solved ??

There is a page setting in the Guttenberg editor, there is an option “enable page header” which is checked by default. Apparently, up to Zakra 2.1.0, if you made an Elementor page with the “Elementor Full Width” template, it did not matter whether this was checked or not, the header was never shown.

It looks the template now does obey this checkbox from 2.1.1 onwards. Disabling the page header solved the issue.

(If anyone reading this tread would be looking for the checkbox: open your page in the normal WordPress page builder, scroll down, under page settings go to the page header tab and disable the checkbox. Please do note the setting only applies to that specific page.)

Thanks for your help!

Kind regards,

Tim