Page copy #379
Merged
Page copy #379
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds a "copy" method to pages.
By default, this will make an exact copy of the page and place new page immediately after the old page in the tree.
Basic usage:
page.copy()Options:
recursive - Setting this to True will copy the entire subtree of the page as well (default is False)
to - This lets you specify a different parent page to copy the page into. The page would be added as the last child of this page
update_attrs - This is a dictionary of attributes and values to change before saving the copy. Eg:
page.copy(update_attrs={title: "New Title", slug: 'new-slug'})This is ready for review/merge. I'll create the admin UI in a separate PR