Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect UCM Asset Tracking #43669

Open
sanderpotjer opened this issue Jun 18, 2024 · 0 comments
Open

Incorrect UCM Asset Tracking #43669

sanderpotjer opened this issue Jun 18, 2024 · 0 comments

Comments

@sanderpotjer
Copy link
Member

Steps to reproduce the issue

  • Create Joomla article
  • Add Tag

Expected result

  • A) New row (e.g. id 43) in database table #__assets with name com_content.article.X (X = id of article) created.
  • B) New row (e.g. id 44) in database table #__assets with name #__ucm_content.X (X = id of article) created.
  • C) In database table #__content a new row with id X (article id) is created and asset_id has row value of A (e.g. id 43)
  • D) In database table #__ucm_content a new row with core_content_id X (article ID) is created and asset_id has row value of B (e.g. id 44)

Actual result

  • A) New row (e.g. id 43) in database table #__assets with name com_content.article.X (X = id of article) created.
  • B) New row (e.g. id 44) in database table #__assets with name #__ucm_content.X (X = id of article) created.
  • C) In database table #__content a new row with id X (article id) is created and asset_id has row value of A (e.g. id 43)
  • D) In database table #__ucm_content a new row with core_content_id X (article ID) is created and asset_id has row value of A (e.g. id 43)

So the new row in #__content and #__ucm_content both link to the same asset_id and the #__ucm_content.X asset has no relation in other tables. This is not correct.

Additional comments

This behavior is introduced with PR #39165 which sets the flag $this->_trackAssets = false; for the UCM content table. This indeed reduces useless assets rows. However this change did not take into account the fact that a new UCM content row is created when tags are added.

The incorrect asset_id store is also mentioned in the comment of the PR: #39165 (comment)

As long as data is created in the #__ucm_content the $this->_trackAssets = false; should be removed. Or the asset_id in #__ucm_content should not be set at all and the column can be removed as the asset for #__ucm_content does nothing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants