No Code Attached Yet
avatar brianteeman
brianteeman
3 Oct 2023

Steps to reproduce the issue

Install 4.4 and the blog sample data.
Check the source of the blog page and you will see various schema settings and values

image

Upgrade to j5

Expected result

At a minimum the existing schema settings are maintained

Actual result

All schema settings are removed without any notification at all. Resulting in a site with changed schema (none at all) which will kill a sites seo

image

Additional comments

If you know the hidden secret you can discover that there is a plugin setting to enable the original schema data and prevent you from editing thousands of articles.

BUT if you check the plugin it shows that those hidden settings are enabled.

image

Ah wait with the new plugin the rich data is now inside a json file in the head. Lets check that and see what data is in it.

image

As you can see the data is not the same at all.

avatar brianteeman brianteeman - open - 3 Oct 2023
avatar joomla-cms-bot joomla-cms-bot - change - 3 Oct 2023
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 3 Oct 2023
avatar richard67
richard67 - comment - 4 Oct 2023

Ah wait with the new plugin the rich data is now inside a json file in the head. Lets check that and see what data is in it.

As you can see the data is not the same at all.

@brianteeman That's the structured data for the breadcrumbs, not for the blog or blog items.

avatar brianteeman
brianteeman - comment - 4 Oct 2023

@richard67 yes I know. The structured data for the blog items is completely gone. If you believe that structured data is important for SEO then, as the code stands, you will need to add structured data to every content item. And that is if you know about this on upgrade and not wait until your SEO is damaged

avatar brianteeman
brianteeman - comment - 4 Oct 2023

Looks like this bug was fixed once by @HLeithner in #41250 but broken again later - perhaps with #41260

avatar brianteeman
brianteeman - comment - 4 Oct 2023

and based on the screenshots I posted in #41231 we dont even get the json information now that we used to. So there is clearly a bug somewhere that has been introduced since the original pr was merged

avatar brianteeman brianteeman - change - 4 Oct 2023
Status New Closed
Closed_Date 0000-00-00 00:00:00 2023-10-04 14:44:31
Closed_By brianteeman
avatar brianteeman brianteeman - close - 4 Oct 2023
avatar brianteeman
brianteeman - comment - 4 Oct 2023

closed as we have a pr

Add a Comment

Login with GitHub to post a comment