[#41251] - [5.0] schemaorg unexpected destructive behaviour
- Closed
- 21 Nov 2023
- Medium
- Build: 4.3-dev
- # 41251
Steps to reproduce the issue
- Add some values to the blogposting schema, save and close and check that the schema you entered is included on the front end
- Re-open the article. Switch to the schema tab and add some values to the person schema, save and close and check that the schema you entered is included on the front end
- Re-open the article and go to the blogposting schema. Do Nothing. Go to the main tab and edit the article. Save and close and check that the schema you entered is included on the front end
Expected result
- Blogposting Schema is used in the json+ld
- Person Schema is used in the json+ld AND the data -previously entered in the Blogposting schema is still present in the admin
- Person Schema is used in the json+ld AND the data -previously entered in both the Blogposting and Person schema is still present in the admin
Actual result
- Blogposting Schema is used in the json+ld
- Person Schema is used in the json+ld AND the data -previously entered in the Blogposting schema has been removed WITHOUT any notification of this destructive change
- empty Blogposting Schema is used in the json+ld AND the data -previously entered in the Person schema has been removed WITHOUT any notification of this destructive change
Additional comments
Perhaps I added all the fields in one schema and saved, went to look at another schema to see if it was relevant decided it wasnt. changed something else in the articvle and saved. Now I just lost all the data I previously entered
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
sorry - typos now corrected in original post
tag => tab
name => person
about the removed content, why do you think it's unexpected? You change the type and you don't see it any longer right?
So it's gone like everywhere else in joomla too, like changing the category. We don't save data somewhere hidden if you switch types. That wouldn't make anysense for me.
Changing the category is not comparable. That is a switch from one category to another and can just as easily be switched back. This is user created data that is completely removed without any notification. There is nowhere in Joomla that does a destructive change without notice.
If you look at fields that is why we dont allow you to change a field type after it has been created because you would lose user created data.
Changing the category is not comparable. That is a switch from one category to another and can just as easily be switched back. This is user created data that is completely removed without any notification. There is nowhere in Joomla that does a destructive change without notice.
it is compare able, in both cases you get new fields
If you look at fields that is why we dont allow you to change a field type after it has been created because you would lose user created data.
and it not nice for the user, I have in mind to change this that you at least can switch between compatible field types, like text,phone,email,url or similar fields.
it is compare able, in both cases you get new fields
Only if you set up custom fields
AND only if you setup those fields per category
Hey and guess what if you change the category back then the data the user entered is still there.
chrome_2023-07-26_11-58-34.mp4
thanks you found a bug in custom fields, can you please create a issue based on your finding, it's not ok that we leave garbage in the database.
No it is NOT a bug
of course it's a bug, data that are no longer used by the article have to be removed. As example if you use the custom fields to filter for articles which has a field "awesometext" and you search for "yes" in this field you will still get the articles which are not longer belong to your filter criteria because it is not longer in the relevant category and this is wrong.
after x years is not an expected feature?
how is that even remotely related
an answer of your
after x years is not an expected feature?
just because something behaves like that for years it doesn't mean that it's expected.
so completely off-topic and unrelated. And you wonder why people dont contribute
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-11-21 21:20:34 |
| Closed_By | ⇒ | brianteeman |
Closed as clearly no one else sees this as a problem
not sure what you mean with schema "tag", I can'T find a Schema Type "tag" also the "name" schema doesn't exists. can you please be specific which types you select where?