*Feature Request - Scheduled publishing for exsiting content #411* I have two approaches for this problem
1) Implement an update queue, where the user would update the post/page and schedule multiple updates that would be published in the future. Ex:- A) I update the post to be updated @ 12 AM. Then i update the post to be updated at 3 AM. Then the post would be updated at 12 AM and then subsequently update at 3 AM. For this we would need to implement another model for updates. With the old data we can do 2 things I) Delete the update data after they have been updated. II) Keep the data in the DB , for future references to the update. 2) Implement a singular future update option. The user would update the post and schedule it, and if he updates again before the content going live it would be overwritten. Ex:- I update for data to be published at 12 AM then i again update to be published at 3 AM. then the post will be updated at 3 AM, as i ovewrote the update whichw as to happen at 12AM. For this there would be a need to have an update model as well. These are the high level conceptualisation of the feature. Would proceed once you guys review it and tell me what should be better to implement. Regards Shaurya -- 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.
