NOtice and warnings with very latest update

Whoa! Thanksk for letting me know. I’m not sure why this is occuring as that constant should definitely work, and does work just fine on my local install :/

I’ll remove that section for now until I can work out what is wrong.

Thanks for letting me know!

I’m uploading version 1.4.5 right now, which will fix this problem immediately.

I’m not sure what is causing it, so I just removed the plugin review notice. It’s not critical for the functionality of the plugin anyway. I’ll work out what is causing the error when I have more time to look into it.

Thanks for making me aware of this problem so quickyl.

I think I know where the problem lies. WordPress includes constants for MINUTE_IN_SECONDS, WEEK_IN_SECONDS, YEAR_IN_SECONDS etc., but of course a months have varying lengths, so it wouldn’t make sense to include a constant for MONTH IN SECONDS. The plugin was doing a calculation which involved dividing by that constant, and it was probably defaulting to a value of zero, which of course will be an infinite number and trigger a fatal error like that.

I guess my test sites were not triggering the month limit, so it didn’t fire off that error and so I wasn’t aware of it myself :/

Thanks for helping with improving the plugin. Bug reports like this are super helpful ??

great news! and thanks for being so up to speed on making changes – and yeah lol those month dates are annoying ??

This plugin did work really well however so many themes don’t use the header tags that I sadly had had to find something else – this time – but it certainly worked like a charm
Thanks
Sarah

Unfortunately there is not much I can do about themes not supporting the WordPress custom header system :/