Skip to content

Comments

Add mechanism for a separate publishing workflow#1

Open
kurtrwall wants to merge 1 commit intostable/1.1.xfrom
dual-wield-site
Open

Add mechanism for a separate publishing workflow#1
kurtrwall wants to merge 1 commit intostable/1.1.xfrom
dual-wield-site

Conversation

@kurtrwall
Copy link
Owner

This is to more easily see what was done to make the separate site publishing work.

@kave

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just trying to understand the scenarios:

if page is shared & live

  • then it is removed from the content site but is still visible on the www site.
  • they will need to do an extra step of unpubishing it on www

if page is unshared & not live

  • then they can unshare it which removes it from being visible on the content site

is this correct? @kurtw

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So page.unpublish() was wrong on line 513. It should have "unshared" the page.

In terms of your question, publishing a page will make it appear on content. Unsharing won't work for pages that are on published.

kurtrwall pushed a commit that referenced this pull request Aug 8, 2016
As of taggit 0.11.0 self.tags.all() no longer performs an extra query if the tags were prefetched.

See: https://github.com/alex/django-taggit/pull/140/files#diff-61d51a325171d97c8a56e59ea525339bR351
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants