この会話は、活動がないためロックされています。新しい投稿を作成してください。
この会話は、活動がないためロックされています。新しい投稿を作成してください。
Hi, another tricky one, under /etc/replication/treeactivation.html you can activate filtering by only modified and only activated and ignoring deactivated pages, is there a way (using curl) to activate only active pages but ignoring modified pages?
解決済! 解決策の投稿を見る。
表示
返信
いいね!の合計
Hi Ronny, I dont think there is an option for 'ignoremodified'
however, I didnt exactly get your usecase. what do you mean by 'to activate only active pages but ignoring modified pages'
do you mean ignoring modified pages which are already activated and activate only the new activated pages ??
表示
返信
いいね!の合計
Hi, you can use
curl -u admin:admin -F cmd=activate -F ignoredeactivated=true -F onlymodified=false
-F path=/content/project http://localhost:4502/etc/replication/treeactivation.html
表示
返信
いいね!の合計
Thanks, but onlymodified=false includes both modified and non-modified pages.
表示
返信
いいね!の合計
Did you tried executing it?
表示
返信
いいね!の合計
Yes, what I would need is a ignoremodified option, but it doesn't seem to exist, in order to do a reactivate=true and ignoremodified=true.
表示
返信
いいね!の合計
Ronny Fallas wrote...
Yes, what I would need is a ignoremodified option, but it doesn't seem to exist, in order to do a reactivate=true and ignoremodified=true.
I hope this link will help you
表示
返信
いいね!の合計
Hi Ronny, I dont think there is an option for 'ignoremodified'
however, I didnt exactly get your usecase. what do you mean by 'to activate only active pages but ignoring modified pages'
do you mean ignoring modified pages which are already activated and activate only the new activated pages ??
表示
返信
いいね!の合計
Thanks for the commands, but there is no indeed option to ignore modified pages, at least from the standard tree activation options.
This is the case:
There is a backup instance where we need to move content only when the release is approved in production and everything is working as expected.
We cannot move them via packages, because of a previous issue where doing in that way, previously deactivated pages were activated again. So, we switched to tree activation, where you have the option to do a replication ignoring deactivated pages, the downside, is that the tree activation bypasses the approval workflow, which is completely undesired.
Then, now I need a way to activate (that is, replicate in the end) only active pages that are not modified (that is, page updates that are pending to be approved).
表示
返信
いいね!の合計
If you want to move content from production instance to backup instance then why not create and copy packages separately for author and publish instance. You can create 2 packages one on Prod author and one on Prod publish and move them over to backup author and publish respectively. With this approach you don't need to activate any pages after the package install operation.
表示
返信
いいね!の合計
Hi Ronny Fallas
Please look at the cURL commends mentioned.
Activate | |
curl -u admin:admin -X POST -F path="/content/path/to/page" -F cmd="activate" http://localhost:4502/bin/replicate.json | |
Deactivate | |
curl -u admin:admin -X POST -F path="/content/path/to/page" -F cmd="deactivate" http://localhost:4502/bin/replicate.json | |
Tree Activation | |
curl -u admin:admin -F cmd=activate -F ignoredeactivated=true -F onlymodified=true | |
-F path=/content/geometrixx http://localhost:4502/etc/replication/treeactivation.html | |
For Full set of commands please have a look at the link: - https://gist.github.com/sergeimuller/2916697
I hope this would help you.
Thanks and Regards
Kautuk Sahni
表示
返信
いいね!の合計