? Pending

User tests: Successful: Unsuccessful:

avatar ggppdk
ggppdk
13 May 2020

Pull Request for Issue #29015 , #29033 ?? (i have not tested) (i have only tested by own extension)

Summary of Changes

TagsHelper::createTagsFromField() is not setting
parent_id

But when not setting parent_id,

  • the DB 's default for the column parent_id is used, which is '0'

thus the tag is created with parent_id is 0 instead of the expected parent_id which is 1 (the id of the root record)

As said above in my case the tags were created with parent_id zero
NOTE: This PR does not fix the any tags already created with parent_id 0

Testing Instructions

Expected result

Actual result

Documentation Changes Required

avatar ggppdk ggppdk - open - 13 May 2020
avatar ggppdk ggppdk - change - 13 May 2020
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 13 May 2020
Category com_tags Administration Libraries
avatar ggppdk ggppdk - change - 13 May 2020
The description was changed
avatar ggppdk ggppdk - edited - 13 May 2020
avatar SharkyKZ
SharkyKZ - comment - 14 May 2020

I can't reproduce the issue with core components. Any idea why this would be needed? Shouldn't setting location as parent's child handle this anyways?

avatar ggppdk ggppdk - change - 14 May 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - change - 14 May 2020
Category com_tags Administration Libraries Administration com_postinstall com_tags Front End com_users Libraries
avatar ggppdk
ggppdk - comment - 14 May 2020

@SharkyKZ

Yes if location is set
then TableNested::store() should set parent_id

so using
TableNested::setLocation() before TableNested::store() should be enough

I am not sure what is happening,
and because i cannot replicate in Core extensions, i will close this PR

avatar ggppdk ggppdk - change - 14 May 2020
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2020-05-14 18:28:04
Closed_By ggppdk
avatar ggppdk ggppdk - close - 14 May 2020

Add a Comment

Login with GitHub to post a comment