https://forge.joomlapolis.com/https://forge.joomlapolis.com/favicon.ico?17095821032015-12-01T20:00:33ZJoomlapolis forgeCB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137102015-12-01T20:00:33Znant
<ul></ul><p>Update - the system action looks like it also has bad logic if approval is turned on - perhaps uploading an image that needs approval should not be tracked as it just displayes the pending approval image.</p> CB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137212015-12-13T00:06:51Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Rejected</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Nothing to do with any of that. The activity is static. It's not being parsed on display and pulling the avatar field. It's logged once and the HTML stored is directly output. CB Activity needs built in trigger handling for internal activity like that. Basically the same way GJ has built in handling of its own activity.</p>
<p>Rejecting this ticket and linking it to the ticket in CB Activity to hardcode core activity parsing.</p> CB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137222015-12-13T00:06:56Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/5407">Feature proposal #5407</a>: Hardcode support for core activity</i> added</li></ul> CB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137432015-12-14T18:25:53Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Rejected</i> to <i>Assigned</i></li><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li><li><strong>Target version</strong> set to <i>6.3.4</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>0</i></li></ul><p>Re-opening as this activity should only maintain 1 activity entry like some other activity. Meaning it should edit the old entry and update it with new information and a new date or delete the old entry first. Even hardcoding the activity output won't really help with this as the activity just isn't valid anymore.</p> CB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137772015-12-16T21:28:52Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Old activity entries will now delete before a new activity entry is logged for canvas and avatar.</p> CB Auto Actions - Bug #5630: System Action logic for canvas and avatar update activities not accounting for removal of uploaded imageshttps://forge.joomlapolis.com/issues/5630?journal_id=137942015-12-17T17:59:16Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>