Closed (won't fix)
Project:
Views Scheduler
Version:
master
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Oct 2006 at 14:49 UTC
Updated:
18 Apr 2007 at 01:08 UTC
views_scheduler_select_schedules() should use the "publication_id" field instead of the "schedule_id" field.
Don't ask me why, but that's how the rest of the code works. I am puzzled why "publication_id" is used like a primary key in the code, and yet the database does not describe it as such.
Without this patch, cron jobs will probably have no effect.
Comments
Comment #1
flk commented