[#41252] - [5.0] schemaorg missing data or default values
- Closed
- 21 Nov 2023
- Medium
- Build: 4.3-dev
- # 41252
Steps to reproduce the issue
- Create an article - do not add a schema. Display the article in a single article menu item and make sure it is set to show the created date. Check the values in the json+ld in the frontend
- Edit the article - add some values to blogposting schema. Check the values in the json+ld in the frontend
- Edit the article - add some values to the date fields in the bloposting schema
Observed Results
- "dateModified":"2023-07-26T07:27:37+00:00", (kown bug that it says modified but thats not the issue being discussed here)
- New schema data used but date fields now blank
- Date fields now have the values from the schema
Expected Results
Any field that has a fallback value should be used unless it is changed in the schema
The same can be observed with any field that has a fallback value
Additional comments
Any schema field that has a matching field in the existing article fields should use those fields. Maybe pre-fill the field in the schema so I can edit them.
The important thing is that you shouldnt have to enter the same thing twice
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
The legacy/fallback plugin is not intended to work if a schema is selected in the article. That would be unexpected for the user and for us.
Why is it unexpected for the user. There is no legacy/fallback plugin it is all in the system plugin
Easy solution
The content plugin is a fallback if you don't use the schema.org implementation and is not for extending other schemas.
not sure what you suggest with the image, if you leave it blank then you can't leave it empty, what's if you don't want that a date is shown, or the author should not be shown in the json+ld data.
The content plugin is a fallback if you don't use the schema.org implementation and is not for extending other schemas.
There is no content plugin. There is only the system plugin, as I said before, which makes no mention of it being a fallback AND it is required if you do use the schemaorg.
This plugin adds the "article" schema as fallback if real schema.org types are not used.
Wow I would never have guessed it was there. Especially for contacts
So can you please confirm exactly what the minimum settings are for the fallback behaviour to be active
would need to look at the code, so only @bembelimen can do this, but iirc this option in the plugin must be yes and you have no schema selected in the article and of course the schema system plugin must be active.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-11-21 18:27:35 |
| Closed_By | ⇒ | brianteeman |
closed
The legacy/fallback plugin is not intended to work if a schema is selected in the article. That would be unexpected for the user and for us.
Autofilling is a thing we already talked about and how to solve it, so it's on the list but it's not so trivial as it sounds at a first glance. But I'm optimistic we solve it.
For example, pre-filling the fields doesn't work
any ideas are welcome