Closed (fixed)
Project:
Content Distribution
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Dec 2009 at 09:15 UTC
Updated:
23 Feb 2010 at 14:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
greg.harveyWoah, now you're asking. My deep and foggy memory thinks this is the last run cron time and this is a sort of debug option allowing you to "fake" the last cron run for testing. But I'm not 100%... Actually, it doesn't run on *every* cron - I think the module keeps its own variable
(I should note, I started prototyping this abou 2 years ago and tayzlor did most of the work for the last year...)
Comment #2
tayzlor commentedi *think* if you just change the time and click on 'save settings' it will get reset to the specified time. as greg mentioned above this is kind of a debugging option so you can set it to say yesterday and try and bring over some content again.
we should probably change the description text for the form field so it does not mention anything about clicking 'reset this... blah..'
I think there was previously a reset button, but it looks like it got removed.
Comment #3
joachim commentedThe other thing is that saving the settings insists on this value being filled. Which means you're forced to either make up a date and mess up the system, or find out the current date.
Comment #4
joachim commentedOk, so I think the simplest thing is just to allow this field to be empty if you don't want to reset the date variable.
(In the long term, I would split the server settings that you don't touch once they're set up from the date changing and the 'Get stuff' buttons.)
Committed this patch to 6--2.
#663798 by joachim: Fixed date reset option insisting on a date.
(Wacky line numbers probably; due to being cherry-picked out of all my other changes... but applies ok.)
Relevant to 6--1 so marking as needing to be ported.
Comment #5
joachim commentedCommitted to 6--1.