Scheduler options aren't exposed to Views for fields

+1 but also, +1 for exposing an argument.

Use case - you have 8 views: front page, sports, metro...etc., and these represent landing pages and you have a ton of content that you've got working with the scheduler. Essentially, you can create a staging system, to check what your sections will look like ahead of anything going public (this would require making duplicate views with extra privileges, or putting a permission on the argument which I believe is not yet supported...).

Therefore, you could have:

yoursite.com/metro/04082007 (where 04082007 is a date arg. of the scheduler) and it would show what the metro section would look like on 04/08/2007 based on what you have scheduled.

Does anyone else see this as useful? You then have the effect of a views_staging.module :)

+1

I was considering having a "queued" section..possibly a block with "scheduled for release"

Great idea..I was just going to post

I would need this for 4.7 though..

Should I submit a new request or is this fine?

Thanks

I thought of a decent work-around for this problem. Since I will no longer be using the 'promoted to front page' option for nodes, I thought I would tag that to indicate that a node has been given a scheduled release. That way, you can test for it with views, just make sure when you set a schedule, you make sure you check front page as well.

Pretty much my entire site is composed of views, so there really isn't a regular "front page"

Hope that helps some of you.

I do intend to add Views compat into Scheduler when I come to do the next major piece of work on HEAD. However, that'll be for Drupal 5. I may packport it to Drupal 4.7 time permitting. My real problem is that I have a few modules to maintain so I normally follow the simple rules :

1. I support the current Drupal release (in this case 5) and the previous release (in this case 4.7) for bug fixes.
2. New features go into the latest release (as it stands now that's 5).

If I don't do that I can end up doing *alot* of work on the same thing stretching right back! Help always appreciated if others want to submit patches.

Yes! If there was a way to use the Date Fields Scheduler uses to schedule/unschedule in views, well that would be just fantastic!

Or any other way to show users posts about to expire.

Idea:

What about just creating a CCK date field? And using this date value as the value "Scheduler" uses for the Data Value to "Schedule/ Unschedule".

If someone could elaborate on how to do this, problem solved!

CCK date field. Reasonable idea. However, when upgrading from old scheduler to new, how will the update script know what new cck field to use as it's target for all those dates it has? CCK is dynamic and therefore Scheduler needs to know (by admin setup) which field is to hold the dates. That info will almost certainly now be avaiable at update.php time.

Tis a good idea thou and will give it some thought.

Here is a patch that exposes the fields publish_on and unpublish_on to views thereby making it possible to show and sort on these fields in your own views.

Committed, thanks.

http://drupal.org/cvs?commit=79109

is there a dev version of Scheduler to test how it works with Views?

This patch only exposes scheduler to views fields, not to sort or filter.

Do you know it if exposed the date for Arguments?

I think this whole concept would be better reverse-engineered. By that I mean, using the work that has already been done with CCK and allowing Scheduler to use CCK date Fields for publishing/unpublishing. Just my 2 cents.

This only exposes them for fields.

More work is necessary to integrate them for filters and/or arguements. In my opinion, that work should be done in a new issue to keep the issues manageable.

Subscribe. Is there any new development on exposing scheduler for arguments? I need to show on a calendar the content that is coming up for scheduling... seems like others would need this as well.

Hopefully I'm just missing new developments... thanks!