[MGNLSYNC-8] Synchronization Module does not work for DMS repository Created: 18/Nov/11 Updated: 29/Mar/22 Resolved: 29/Aug/12 |
|
| Status: | Closed |
| Project: | Magnolia Synchronization Module |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.0.1, 1.1.2 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Richard Unger | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dms, synchronization | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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: | |||||||||||||
| Team: | |||||||||||||
| Description |
|
The synchronization module DOES NOT work correctly for the DMS repository. Current behaviour: When (recursively) synchronizing content from the DMS repository, folders are handled correctly, but the documents are handled incorrectly. Expected behaviour Inactive (red) document nodes should NOT be synchronized to public instance. I think this is because of a problem with the Syndicator. Folders are type "mgnl:content" (like pages in website tree). Document Nodes are type "mgnl:contentNode" (like paragraphs in website tree). I tested this under magnolia 4.4.2 with synchronization module 1.0.0 |
| Comments |
| Comment by Richard Unger [ 18/Nov/11 ] |
|
Okay. Looking at the code, I think the problem is that there is no special treatment of the DMS workspace. Synchronize module uses SynchronizationCommand: and this is incorrect for DMS. In DMS, when activating this is somehow handled from the Tree --> see DMSAdminTree.getCommandContext() I have to say: the code for activation is very complicated!!!! |
| Comment by Jan Haderka [ 29/Aug/12 ] |
|
Tests committed only in master, not backported to 1.0 branch. |