You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are sufficient number of sites being syndicated (I've seen this with 71 sites) then adding a new site or editing an existing site results in a 500 error (PHP Fatal error: Maximum execution time of 30 seconds exceeded).
The reason is that editing, creating or deleting a site clears the cron jobs and so triggers a content pull. If the content pull takes too long, the user gets a white screen.
but I'm not sure if those two lines are strictly necessarily or not. Beyond not having to do a manual pull or wait till the next scheduled pull for changes to be reflected, there doesn't seem to be any advantage.
The text was updated successfully, but these errors were encountered:
Doh! Obviously, resetting the cron jobs is required, when you're adding a new site. Instead I've set the initial time for the cron job to be time() + 60 rather than time() - 1 since the latter seemed to be triggering the job immediately and as part of the same request.
This 'breaks' the 'pull now' which doesn't quote pull now, but in a minutes time...
If there are sufficient number of sites being syndicated (I've seen this with 71 sites) then adding a new site or editing an existing site results in a 500 error (PHP Fatal error: Maximum execution time of 30 seconds exceeded).
The reason is that editing, creating or deleting a site clears the cron jobs and so triggers a content pull. If the content pull takes too long, the user gets a white screen.
The obvious fix is to remove these too lines: https://github.com/Automattic/syndication/blob/master/includes/class-wp-push-syndication-server.php#L50-L51
but I'm not sure if those two lines are strictly necessarily or not. Beyond not having to do a manual pull or wait till the next scheduled pull for changes to be reflected, there doesn't seem to be any advantage.
The text was updated successfully, but these errors were encountered: