[MGNLACTIVATION-59] When activating, mgnl:lastActivated is not updated on public side Created: 14/Apr/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Activation
Component/s: None
Affects Version/s: 5.0
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Nickolaus Wing Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


Attachments: Text File ReceiveFilter.java.patch     Text File ReceiveFilterTest.java.patch    
Template:
Patch included:
Yes
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Testcase included:
Yes
Date of First Response:

 Description   

We are using the exchange-simple module for activations, and tried to key off of mgnl:lastaction for one of our template features (a reminder when a page has gone unedited for a long time). We wanted to key off of lastaction instead of lastmodified so that someone could simply re-activate to clear the reminder.

However, the author side of the activation transaction updates lastaction AFTER the activation completes successfully, so the public side is left with a one-activation-too-old lastaction date.

To fix it, I used the attached patch. It only updates the lastaction, and only for the page, NOT for any of the content inside the page. A more complete patch might also update the activatorid, and do it for all the content below the page (but not pages below the page). I'll leave the more complex patch to you guys, if you decide it's worthwhile. This one works for our purposes.



 Comments   
Comment by Jan Haderka [ 28/Aug/15 ]

It was actually never meant to be updated on public. What is sent to public is exact copy of the content on author before publication. I can see however how this would be helpful.

Thanks for the patch.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Sun Feb 11 22:59:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.