reason for max of 14 days for days_change

@dreist Thanks for asking this question.

When creating the code that scans ahead for a change in status, I do need to set a limit of some kind to prevent it from going on forever. The 14 days seemed like a suitable period to progress through each day, tallying up the seconds into accumulated total before a change.

I have added something to handle temporary closures – so you can use conditional text with the replacement variable: %closure_end% to include the end of a period of closure. There is more available within the Shortcodes section for [open_text].

Do you have an example for your situation? I can extend the calculations if there’s a requirement.

I’m using the code for a bar that’s closed in winter and %closure_end% is useful already. to make a countdown until the spring, i would currently need around 125 days.

@dreist Thanks for clarifying. This does make sense.

I’ll look into extending this in the future, perhaps with an additional parameter to avoid overworking when a place is either set to always closed or always open.