bug
avatar rdeutz
rdeutz
1 Jan 2013

I made the change from #44 and checked if I get an entry in the asset table and there aren't entries for the new issues. I think that is a bug, can some check if it is just me ;-)

Cheers,
Robert

avatar rdeutz rdeutz - open - 1 Jan 2013
avatar rdeutz rdeutz - open - 1 Jan 2013
avatar mbabker
mbabker - comment - 1 Jan 2013

Probably a bug. I think I need to go through everything and make sure all issue handling code is working with assets correctly.

avatar mbabker
mbabker - comment - 2 Jan 2013

Something is definitely broken. I just looked at the database for tracker.babdev.com and every record is getting created with an asset ID of 0.

avatar mbabker
mbabker - comment - 2 Jan 2013

OK, to further clarify. All records in the #__issues tables report asset_id = 0 which is actually referencing the row with name = "com_tracker.issue.0" in the #__assets table. Looks like it might've stopped working while I was building the hooks because on tracker.babdev.com, #32 is the first record without a proper asset ID.

avatar rdeutz
rdeutz - comment - 2 Jan 2013

ok, good. Maybe I have time to look into it later, probably it is the JtableIssue implementation.

avatar mbabker
mbabker - comment - 2 Feb 2013

I'm finally realizing this isn't a fault of anyone here (well, maybe me). The change at joomla/joomla-platform@4e782fe changed the behavior in a way that the _tbl_key var in the class, in this case referencing our table's id field, doesn't have the value for the newly inserted ID anymore.

avatar mbabker
mbabker - comment - 2 Feb 2013
avatar mbabker mbabker - reference | - 2 Feb 13
avatar mbabker mbabker - reference | - 24 Apr 13
avatar elkuku
elkuku - comment - 19 Jun 2013

This has been fixed, since we don't have an assets table any more ;)

avatar elkuku elkuku - close - 19 Jun 2013
avatar - close - 19 Jun 2013

Add a Comment

Login with GitHub to post a comment