[MAGNOLIA-4415] Metadata - LastAction is not set correctly on public node after activation Created: 16/May/12 Updated: 17/May/12 Resolved: 17/May/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 4.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Richard Unger | Assignee: | Jan Haderka |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | activation, metadata | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Magnolia EE 4.4.6, Linux, Sun JDK 6 |
||
| Template: |
|
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
You probably hate me by now, but here's another problem I found (my customers reported) to do with activation: When content is activated, the lastAction is set to the publication date on the author system. Unfortunately this seems to happen after the content is sent to public instance. The result is that the activated content on the public instance always has the "previous" value for the lastAction metadata field compared to the author system. Eg: This means that after activation, content on author and public instances is different! This is a problem for us, as we use the publication date to sort the content for various listing type displays. |
| Comments |
| Comment by Richard Unger [ 16/May/12 ] |
|
I think a solution could look like this: 1. On Author: Determine a timestamp for the activation, and remember it. In this way, the timestamp for the activation will be constant for all content activated in the same request, and the timestamp will be the same on author and public instances. |
| Comment by Jan Haderka [ 17/May/12 ] |
|
Hi Richard, In this particular case however, I believe that this is not an issue. What you suggest might work on systems where versioning is not used, but as soon as you use versioning the contract is to deliver that exact version to the public instance, i.e. with whatever values are contained in it. If you want to sort content by the date I would suggest to use custom property for such values rather then value that is meant to be for internal use by activation. Alternatively, if you insist on using lastAction, you can either try to customize ReceiveFilter or you can add observer that will update the dates for you after activation (you can listen for all content changes, nothing else then activation should modify the content on public) or you can write custom flush policy for cache and when it receives list of content updates, you can selectively go and update that content values to whatever you feel like. We can continue this discussion in user list or over support, whichever you prefer. |