Using the timed-content-rule affects page load time

The way how server side rules work is to calulcate a list of possile date ranges and then check if the current date is in one of the date ranges or not. So if the rule is really until year 6000 then the plugin has to calculate about 200000 values (3978 years, 50 weeks per year) which may take a while.

The calculation is done for future events as well to be able to show a list of projected dates/times in the backend.

Please reduce the end date to a year which makes more sense like like 2100. This is still more or less “unlimited” since it is not very likely that your website will still be around exactly in this form in 78 years.

I will also implement an internal limit to avoid too many values to be calculated since indeed it makes little sense to calculate dates for 1000 years into to the future.

I see. That fixed the issue.
Isn’t there a way to set a rule ro work indefinitely all the time?
Like let’s say, mondays and tuesdays, every week, for ever?

No there is no option to say “indefinitely”. This may be added in future versions, but first the internal calculation procedure has to be fixed to limit the number of calculations needed even if one sets a date like year 6000.

• This reply was modified 2 years, 4 months ago by Arno Welzel.

Version 2.70 now contains a fix to limit the number of calculated date/time values, so you should now be able to even use year 6000 as the upper limit without any performance issues.

That is ok for me. Having a time rule that expires is a small price to pay for having such a wonderful functionality.

Thank you for the great plugin by the way!

Thank you so much for the 2.70 fix. You really nailed it with it.