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

Usage of #__jcomments_objects table #141

Open
Giuse69 opened this issue Jul 1, 2023 · 5 comments
Open

Usage of #__jcomments_objects table #141

Giuse69 opened this issue Jul 1, 2023 · 5 comments

Comments

@Giuse69
Copy link

Giuse69 commented Jul 1, 2023

Hi, historically JComments uses the table #__jcomments_object_table to link the commented article in the backend, but:

  1. it stores the title and URL of the commented object/article, so if the title or the alias or the base root is changed => the title and URL becomes obsolete/wrong.
  2. it stores the absolute URL of the article, not the relative to the Joomla base folder, so when moving the site => URLs becomes wrong.

Would it be possible to overcome these limitations getting rid of this table and using #__assets and specific table (#__content) with joins?
thanks

Giuse

@Globulopolis
Copy link
Collaborator

Globulopolis commented Aug 17, 2023

to link the commented article in the backend
Not only in backend. In frontend too.

Partially, the problem can be solved by clearing the table cache in the admin panel in the comments list.
The problem with links will be fixed in the new version.

Would it be possible to overcome these limitations getting rid of this table and using #__assets and specific table (#__content) with joins?

No. Not all objects stored in assets table.
To get data about an object, the component uses plugins for each component.

@Giuse69
Copy link
Author

Giuse69 commented Aug 17, 2023

thanks

@Giuse69
Copy link
Author

Giuse69 commented Jan 13, 2024

Hi, has the new release addressed this issue?
thanks

Giuse

@Globulopolis
Copy link
Collaborator

Hi, has the new release addressed this issue?
thanks

Giuse

No.
"New release"... I apologize for the inaccuracy, i meant 4.1 branch(still in development).

@Giuse69
Copy link
Author

Giuse69 commented Jan 15, 2024

ok

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

2 participants