Trials and Tribulations
Sorry i havent posted in while been busy with so many different things, so much to learn/do so little time hehe :D.
Anyways for past few weeks i have been attempting to create a plan of how go about each stage of the project. But because of what i need to learn and acheive the project just seemed bigger everytime i had a look at it :(.
After a session with drupals SoC pyschiatrist (webchick ;P), I do believe i have it figured out, well the first part anyways (first lesson learnt; dont think about the whole project, take it a chunk at a time).
I spoke to earls about it aswell and this is what i i think is the best way to get moving and seeing some progress will probably help,so to begin with i think its best if I got a list of exactly what i need from the schedule.module, whats missing.
This basicly means see if code is hijackable and what is needed on top of that code to make a ideal schedule module for our use.
Btw this could also be approached from the other end figuring out what i need form the views and whats missing etc.
From the views point, whats missing is an ID, an Entry point, and way to control the schedule.
now taking into consideration the schedule.module db design which i see as:
ScheduleID: This an integer auto incremented, unique
Title: This is a human readable title, which will probably go at the top of the view ‘Monday Headlines’
Type: what type of node will this list hold? blog, book, page story or all nodes?
Pub ID:what’s being scheduled, here I want use the views schedule ID rather than a nodeID, I have bit of a doubt if this is possible…..)
Start:time
Next:time
Last:time
Every:when does the release take place? every day, month, year, hour?
Frequency:the number which will be linked to 'every'
Schedules are tied to content/actions by publication_id - which could be a view id, or any other id number on another table.
So i think its best if I make the publication id an id for a single schedule. This schedule --> works on this view (earl suggested that i use view name " it's guaranteed unique and codebases work with view names" ).
It uses this many nodes (num_nodes) from the view (where 0 might mean all nodes) and is its linked to this action.
| Attachment | Size |
|---|---|
| tables.jpg | 51.35 KB |
i forgot to mention
That currently the schedule.module which i intend to use to schedule the publication only works with drupal 4.6 so for the past few days i have been trying to upgrade it to 4.7 with not much a luck :(.
I am still kinda of confused between the difference of 4.6 an 4.7, so for the time being i have decided that i would just make my own forms etc to add the schedules to the schedule table and let the cron functions of the schedule module take care of the publishing....this in the long run might be a waste of resource but Robert castello who maintains the module said that he wont be updating it until next month..........
I dont like doing it this way but time is of the essence.
feel free to leave any comments. :D
status?
Not sure what you are struggeling with currently, but we managed to get scheduler run in 4.7 last week or so...
hope I find some post to link for you...
meanwhile you can take a look at my patched versions, that also include schedule_actions to be used in the workflow module
hu... no attachments?
please see attachments here http://drupal.org/node/53008
Post your scheduler progress here
If porting that scheduler module is essential (I'll let Earl make that judgement), then we've got to get it ported. Post your progress here and enlist as many people to help explaing things and look at your work as possible. You said one very important thing; "dont think about the whole project, take it a chunk at a time". This is the ultimate truth.
Hang in there, give it your best!