[16.0][ADD] website_blog_scheduled_publication: add new module

[marcelsavegnago]

Summary

This PR adds a new module website_blog_scheduled_publication that allows users to schedule blog posts for automatic publication at a specific date and time.

Features

• Scheduled Publication Date: Adds a datetime field to blog posts for scheduling publication
• Quick Publish Button: One-click immediate publication from the form view button box
• Schedule Wizard: User-friendly wizard dialog to set the publication date
• Visual Feedback: Information banner displays the scheduled date on the post form
• Smart Publication Logic: Automatically prevents immediate publication if a future date is set
• Automatic Cron Job: Runs every hour to check and publish scheduled posts
• Notification System: Sends notifications to blog followers when posts are published
• Search Filters: Filter posts by Published/Not Published status and group by Publication Date or Scheduled Publication Date

Technical Details

• Extends blog.post model with new fields (scheduled_publication_date, schedule_type, next_departure) and methods
• Includes a transient model blog.post.schedule.date for the scheduling wizard
• Inherits and enhances form and search views from website_blog
• Handles edge cases: setting past dates, clearing scheduled dates, multiple record writes
• Comprehensive test coverage with 25+ test cases

Dependencies

• website_blog

Test Plan

• Install the module on a clean database
• Create a blog post with a future scheduled date and verify it's not published immediately
• Create a blog post with a past scheduled date and verify it publishes immediately
• Test the Schedule wizard dialog
• Test the Publish Now button
• Run the cron job manually and verify scheduled posts are published
• Verify notifications are sent to blog followers
• Test search filters and grouping options
• Run all unit tests: pytest website_blog_scheduled_publication/tests/

[yostashiro]

@marcelsavegnago I guess you could take a similar approach as https://github.com/OCA/e-commerce/blob/15.0/website_sale_product_publish_date/models/product_template.py? I think there could even be a generic module with a mixin model which can be inherited by regular models if it fits the core architecture (I haven't taken a thorough look on it).

[marcelsavegnago]

@marcelsavegnago I guess you could take a similar approach as https://github.com/OCA/e-commerce/blob/15.0/website_sale_product_publish_date/models/product_template.py? I think there could even be a generic module with a mixin model which can be inherited by regular models if it fits the core architecture (I haven't taken a thorough look on it).

@yostashiro You’re right — that approach looks like a solid reference point.

For now I’m handling a very specific case to solve the immediate need, but once I have a bit more time I’ll take a closer look and see if we can support a more generic solution (like a mixin / small reusable module) that fits well with the core architecture.

[ivs-cetmix]

Thank you for you contribution!
Some note - not an issue - how about adding a calendar view for the blog.post model so it would be easier to see the scheduled posts?

[ivs-cetmix]

Question: isn't scheduled_publication_date a Python datetime object already?

[marcelsavegnago]

Good point. When accessed from a record (post.scheduled_publication_date), it's already a datetime object. However, vals.get("scheduled_publication_date") can be a string when values come from forms, wizards, or API calls.
The _to_datetime() helper handles both cases safely — it converts strings to datetime and passes through datetime objects unchanged.
We're open to suggestions if you have a better approach.

[ivs-cetmix]

Noted, let's leave as is for now. Would be good to add some comment in the code though to avoid same question in the future.

[ivs-cetmix]

Code review LGTM