[DOCU-208] Update command path in Synchronization module document Created: 07/Sep/11  Updated: 07/Apr/14  Resolved: 29/Sep/11

Status: Closed
Project: Documentation
Component/s: content
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Antti Hietala Assignee: Antti Hietala
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

As pointed out in the user comment, the Synchronization module document is out of date. The command definition was moved in MGNLSYNC-7. Update document and delete comment. You can mail the user a thank you note. Email address is in IntenseDebate comment history.

Standardize the Installing section too.



 Comments   
Comment by Ruth Stocks [ 07/Sep/11 ]

Updated page at http://documentation.magnolia-cms.com/display/DOCS/Synchronization+module
I did the following:

  • Installed the module, but did not test it, because that would require creating a new instance etc.
  • Changed all previous references on the page to what I could see from the installation, i.e. previous references to "re-activation" are now "synchronization" etc. In the Synchronizing - Current status section, I have changed the Status messages in the table to read, for example "Synchronization is starting". I didn’t test/observe this and hope it is correct.
  • In the Configuration section, I added the following text and link "Individual subscriptions are configured in the /subscriber/subscriptions node in exactly the same way as normal subscribers. For more information see Subscribers - Subscriptions.
  • In the Synchronizing section point 3, I added a link to the Cookbook - JCR browser article.
  • In the Scheduled synchronization section, I changed the catalog and command properties, removed "If you leave this field empty Magnolia will look for the command in the default folder." and created a new image.
Generated at Mon Feb 12 01:06:57 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.