[#37153] - [4.1] tags assets invalid data
- Closed
- 6 Nov 2022
- Medium
- Build: 4.1-dev
- # 37153
Create a clean install
Check the #__assets table and you see (apart from root.1) that all the names are in the form com_something
Create a new article and give it a tag
Check the #__ucm_content table and you will see a record has been created for the article you just created
For that record check the value of asset_id (it will be a number)
Now go to the #__assets table and you will see some new records. Find the record with the id matching the asset_id from above.
The name and title are both in the form #__ucm_content.xx
Fairly sure thats not intended and may have consequences
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
I have no idea if there are consequences. I presumed there was a reason for the record to be created but it was created wrongly
| Labels |
Added:
J3 Issue
|
||
It was also in j3. Let's see if we resolve it in J3
There is no reason for having an assetid field in com_ucm_content as much as I see.
Is it perhaps needed for the version history which is available with tags?
If every version can have different permissions - maybe. I must build tests with many different roles / permissions for testing that.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37153.
Please correctly tag this issue as for J4
zero-24
- | Labels |
Added:
J4 Issue
Removed: J3 Issue |
||
I can confirm this issue. These entries have no use and we should remove them. Especially since they are all empty, even when their original content item does have entries in there. This is just wasting lots of time and slowing down sites.
thanks for confirming. I can work on this tomorrow now.
I got it fixed. Writing a PR right now.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-11-06 21:05:00 |
| Closed_By | ⇒ | brianteeman |
great - one less thing for me to look at
Well I never would have found that solution. So thanks again
Confirmed. I assume that it has no consequences except flooding the assets table with useless data.
There is no reason for having an assetid field in com_ucm_content as much as I see.