Closed (fixed)
Project:
Demonstration site (Sandbox / Snapshot)
Version:
5.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 Apr 2009 at 19:30 UTC
Updated:
31 May 2009 at 01:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
wiredescape commentedThanks John,
Possibly same issue as #336216: Automatic reset not always executed in configured interval ?
Be nice to find a solution for this annoying bug!
Comment #2
john.money commentedPatched against 5.x-1.x-dev (2009-Mar-13)... not heavily tested but should work in theory. :)
Comment #3
sunThanks! Looks good, needs some positive confirmation.
Comment #4
wiredescape commentedFound an error in patch. A missing left parenthesis in this line:
+ if ($time - $interval) >= variable_get('demo_reset_last', 0)) {should be:
+ if (($time - $interval) >= variable_get('demo_reset_last', 0)) {(note second left parenthesis required between 'if' and '($time - $interval)'.
Comment #5
john.money commentedBizarre. Not sure how patch got out of sync with my module changes, but you're of course right. Attached is corrected one.
Comment #6
wiredescape commentedPatch has been running on live site with no problems for about a week now but still has some odd behaviour.
When cron set to 60 minutes & Demo set to 30 minutes everything works correctly. If cron and Demonstration site are set to the same time interval, i.e. cron & Demo both set to 60 minutes, the database restoration is inconsistent. Cron fires correctly but Demo will skip the BD restore often but with no pattern. Basically the same problem I reported before #336216: Automatic reset not always executed in configured interval.
Comment #7
sunThanks for reporting, reviewing, and testing! Committed with slight modifications to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.