Great plugin :)

@mikelidbetter Thanks for the review.

With the midnight issue, this is a known bug and I will be addressing this in the future. I’ve left it until now because very few people have mentioned having a problem with this specific issue and if it were raised as a feature/bug fix, I would have elevated this. It’s also potentially quite complex logically and programmatically.

You’re welcome to ask for this to be resolved in an upcoming release. If so, please do this in the forum so other’s may have a change to +1 this.

Thanks for the very fast response to this, much appreciated. I was thinking myself about how you would programme this. I wondering if one easy way to be to compare the actual opening time (only) with the current time (only). If the current time is after the opening (or closing) time it can be assumed to indicate tomorrow. If however, the current time is before the opening time, it can be assumed it is today? Would that work? I will take a look at the forum.

So, if the current time is 6am and the shop opens at 9am, it should indicate ‘opens today at 9am’. If the current time is (say) 7:30pm and the shop opens at 9am it should indicate ‘opens tomorrow at 9am’. This would only work if this bit of code was nested inside the other function on deciding when the shop was next open. This would work without the need to compare dates etc., I think.

@mikelidbetter This logic has plugin-wide implications and this is where the complexity comes in. It’s ok, I’ve figured it out, it’s just a sizable task to implement and thoroughly test it.

This conversion is better suited to the forum.