## blog.models.py Added BlogPostUpdate model and have added BlogPost save method.
## core.models.py Added abstract update model and next_scheduled_update field in Displayable. ## core.managers.py Added updated method to PublishedManager, also the pages/blog posts returned would be checked for pending updates before being returned. https://gist.github.com/XuryaX/fe023edc5b1faff2b14b17db7eda792d Similar things can be done to what you mentioned in your workflow. My implementation seems to be a bit in the direction of what Sean suggested. After an update has been logged. 1. The update wont be modifiable but viewable and deletable.(Should there be an update to an update?) 2. The groups for publishers and normal users could exist. 3. The update would be implemented once it has been used to update the post(not yet done.) There might be instances for which multiple scheduled updates should be there. If we include the updates in the same table with a reference to the post to be update, there might be alot of data piled up which are not for displaying, though it will simplify the written Python Models. -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
