Bug #4430
closedScheduled Posts Not Working
0%
Description
Hi,
Scheduled posts haven't been posting on murphyinstituteblog.org. This has been going on for a number of months but hasn't really been a problem until now. Is there something that can be done to remedy the situation?
Thanks so much!
Leah
Related issues
Updated by Matt Gold over 9 years ago
- Category name set to WordPress (misc)
- Status changed from New to Assigned
- Assignee set to Boone Gorges
Updated by Boone Gorges over 9 years ago
- Assignee changed from Boone Gorges to Daniel Jones
- Priority name changed from Normal to High
- Target version set to 1.8.8
Probable duplicate of #3541. Dan, can you take a look please?
Updated by Boone Gorges over 9 years ago
- Target version changed from 1.8.8 to 1.8.9
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.9 to 1.8.10
Dan, can I ask you to circle back around to this when you have a chance?
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.10 to 1.8.11
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.11 to 1.8.12
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.12 to 1.8.13
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.13 to 1.8.14
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.14 to 1.8.15
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.15 to 1.8.16
Updated by Boone Gorges about 9 years ago
- Target version changed from 1.8.16 to 1.8.17
Updated by Daniel Jones about 9 years ago
Well this is extremely embarrassing, but the issue was that I forgot to call "the_post()" on the new query, and was calling it on the main query by accident, which caused an infinite loop. I'm really really sorry about that, but it ought to be fixed here, along with one other typo - https://github.com/cuny-academic-commons/cac/commit/fbf5111dd42c65ded139915be80b031a4514568e
Again, it's hard to test because I don't know how to reproduce the error locally, but I did re-confirm that an event is being scheduled, and that there weren't any infinite loops going on.
Updated by Daniel Jones about 9 years ago
Remembered to reset the post data after the new loop here: https://github.com/cuny-academic-commons/cac/commit/7c1c7cac9838e31af965188bdf41741fae930237
Updated by Boone Gorges about 9 years ago
- Status changed from Assigned to Resolved
OK, let's give it a try and see what breaks :-D
Moved to 1.8.x in https://github.com/cuny-academic-commons/cac/commit/3dacb3e8917c65d679e7db2943a0346872824c21 https://github.com/cuny-academic-commons/cac/commit/b9dae385e6a7511c4341e95795edd937ae9ef81b