Bug 750784 - Pull a refreshed content spec
Summary: Pull a refreshed content spec
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Joshua Wulf
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-02 11:35 UTC by Joshua Wulf
Modified: 2014-10-19 22:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-04 08:58:39 UTC


Attachments (Terms of Use)

Description Joshua Wulf 2011-11-02 11:35:19 UTC
This would be useful:

an option to 

skynet pull -c --post --refreshed

When this is executed, the post-processed content spec is retrieved by the processor, which then updates all the topic titles to the latest in the database.

This means that I can do all my title edits in the database, then pull an updated content spec.

That would be safer than pushing with --permissive.

Comment 1 Lee Newson 2011-11-04 03:10:34 UTC
Right now this can be accomplished by:

skynet pull -c --post <ID> -o tmp.txt
skynet push -ce --permissive tmp.txt

That will update the Content Spec on the server to the latest Topic Titles.

Comment 2 Joshua Wulf 2011-11-04 08:58:39 UTC
OK, so the best way to do it now is:

skynet pull -c --post <ID> -o tmp.txt
skynet push -ce tmp.txt
# Take a note of all the mismatching topic titles. If you want to update the content spec to the latest versions of the topic titles in the database
skynet push -ce --permissive tmp.txt
rm tmp.txt
# to see the updated content spec with the latest topic titles:
skynet pull -c --post <ID>


Note You need to log in before you can comment on or make changes to this bug.