Bug in Activity

Hi Kyle,
I have commenting enabled on a third party extension using auto action. I then installed the new activity and auto action etc... and then the comments on the third party plugin did not work anymore (actually broke the component completely). I had to go into the auto-action then and save it again for it to work...

Were you adding commenting using CB Auto Actions or did you hardcode in CB Activity API. I need more details in order to better fix the migration. What was broken with your usage? Was the Asset migrated correctly if using CB Auto Actions. Please understand I have completely rewritten CB Activity from the ground up so the more detailed these reports are the better I can fix any migration issues.

Hi Kyle, the easiest is if I copy paste the entry into auto action in here.

And yes, from what I have seen in the tables, the assets got migrated correctly...

Further bug. I had created an auto action which was based on a trigger. One problem that happened was that the "PUBLISHED" field was empty. It recognised the empty published field as 0, thus left it unpublished. That was quite annoying a bug to find... It would be better if the PUBLISHED field would see "empty" as a 1 value...

Hi Kyle, the easiest is if I copy paste the entry into auto action in here.

And that was supposed to be a comment stream? Looks like it migrated to an Activity stream for some reason. Do you have a clone of your site you can load a backup to and provide a screenshot of the previous configuration for comparison?

Further bug. I had created an auto action which was based on a trigger. One problem that happened was that the "PUBLISHED" field was empty. It recognised the empty published field as 0, thus left it unpublished. That was quite annoying a bug to find... It would be better if the PUBLISHED field would see "empty" as a 1 value...

That is supposed to be the case, but appears it's bugged. Have added a bug ticket. Note this is not a CB Activity bug and is a bug in CB Auto Actions.

forge.joomlapolis.com/issues/6568

Looks like CB Auto Actions may have some migration bugs as you've experienced and some possible bugs with the storage of activity. Will see about having a new build pushed tomorrow to get the current 2 known issues fixed.