? Pending

User tests: Successful: Unsuccessful:

avatar SharkyKZ
SharkyKZ
17 May 2019

Pull Request for Issue # .

Summary of Changes

Use the field mapped to core_content_item_id instead of hardcoded id field.

Testing Instructions

To test this properly one would have to find a component that uses tags and has core_content_item_id other than id. On such component the module does not work without patch.

Other than that, test that the module continues working properly on core components.

Documentation Changes Required

No.

avatar SharkyKZ SharkyKZ - open - 17 May 2019
avatar SharkyKZ SharkyKZ - change - 17 May 2019
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 17 May 2019
Category Modules Front End
avatar ghazal
ghazal - comment - 18 May 2019

Namespace wise, should not you use:
$app = Factory::getApplication();
instead of
$app = JFactory::getApplication();

or:
$now = Factory::getDate()->toSql();
instead of
$now = JFactory::getDate()->toSql();

Not sure if this one has been corrected yet:
$tagsHelper = new JHelperTags;

avatar ghazal
ghazal - comment - 18 May 2019

After checking this list:

Use namespaced classes

looks like JHelperTags; has not been modified yet.

avatar SharkyKZ
SharkyKZ - comment - 18 May 2019

@ghazal This is for 3.x. I did not add the code you mention. It was already there and has already been converted in 4.0.

avatar ghazal
ghazal - comment - 18 May 2019

ok. My bad and sorry.

avatar SharkyKZ SharkyKZ - change - 25 May 2019
Labels Added: ?
avatar Milglius
Milglius - comment - 20 Feb 2020

what still we need to do here ?

avatar SharkyKZ
SharkyKZ - comment - 20 Feb 2020

Test it.

avatar zero-24 zero-24 - change - 8 Aug 2021
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2021-08-08 20:08:55
Closed_By zero-24
Labels Added: ?
Removed: ?
avatar zero-24 zero-24 - close - 8 Aug 2021
avatar zero-24
zero-24 - comment - 8 Aug 2021

Dear @SharkyKZ

in preperation of the upcomming release of Joomla 3.10 we have used GitHubs rename feature to rename the staging branch into 3.10-dev. Usually GitHub moves all existing PRs towards the new branch just fine, but here it didnt work. The reason seems to be that the fork of the CMS that was used as base for this PR has been deleted so GitHub does no longer have a base to rebase the PR against the new branch and we are also not able to reopen the PR. For that reason GitHub closed this PR in my name, when this issue is still valid It would require a new PR against the new 3.10-dev or 4.0-dev branch.

Add a Comment

Login with GitHub to post a comment