I need to research how Panels contexts, layout, and content changes are going to work with node revisions, which Scheduler uses to schedule updates to nodes.

Comments

awebb’s picture

awebb commented

Ideally we will want these two systems (Scheduler and Panelizer) to work seamlessly together.

merlinofchaos’s picture

merlinofchaos commented

Panelizer doesn't currently panelize specific revisions, only the 'current' revision. Which, IMO, is probably want people want most of the time. That said, we may need to be able to panelize the revisions as well. As long as it uses the revisioned version of the node I think that would work correctly.

awebb’s picture

awebb commented

I'm going to put this on my project radar. This would be very handy for us because our editorial staff have become pretty dependent on scheduling content changes. It would be awesome if they could schedule layout, context, content changes as well. I like the idea of versioning our Panels.

It needs an integrated interface (checkbox and date selector?) with the Panel edit forms though, or some way of saving state between tabs until the node edit form is saved with the typical scheduler form.

awebb’s picture

awebb commented
Title: Look into how Panelizer would behave with Scheduler project » Look into how Panelizer would behave with scheduling of revisions

Ok, we use some convoluted system of scheduling revisions that is custom coded. This may tie into the scheduler functionality but it is certainly not what scheduler does (publishing and unpublishing of nodes).

I need to research our implementation further.

dww’s picture

dww
we/he/they
commented

Note: I'm approaching this problem from a different angle. I'm using a panelized node type called "edition" for different editions of the front page for a newspaper site. The editors can clone these editions (now that #1205304: Clone the panels display if using node_clone to clone a panelized node and #939016: Use $node->clone_from_original_nid consistently are fixed) to layout the next day's front page, etc. I'll be publishing my code (which is mostly a feature for the node type and a few views, with a bit of additional code) as a real d.o project in the near future. I'll link here when it's available. But, the idea is to have a way to say "put this particular edition as the front page at midnight", stuff like that.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Version: 6.x-1.0-beta1 » 7.x-1.x-dev
Issue tags: +Needs backport to D6

This just came up for me too, and because our site is heavily built upon node references just doing a new done won't work. Bumping it to the D7 branch and tagging it for later use.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

BTW the Revisioning module might also be a good approach for this?

awebb’s picture

awebb commented

The revisions module looks pretty promising. I like what I see, especially the integration with the other contributed modules. I noticed they already integrate with Panels module so maybe integration with Panelizer would not be a big deal.

I'll look more into this as I am dealing with scheduling a lot these days.

awebb’s picture

awebb commented
Status: Active » Closed (fixed)

This has been accomplished with the entity_revision_scheduling module.

http://drupal.org/sandbox/merlinofchaos/1349690

Maybe someday, it'll have it's own home ;-)