Cumulus Support

Hi everyone,

I noticed that since I reset my data, the lowest maximum date has always been 1 day behind, this is a bug with Cumulus MX and not my website (in the past people have blamed the issues to be with my website and not the data itself for some reason)...

On both my data and my website, the value is shown as 18 November on the this month page, 17 November on the this year page and 18 November on the records page. 18 November is correct.

I've cleared the data correctly so I don't know what it could be, I've double checked the web tag in use and it's correct according to the Sandaysoft Wiki.

Thanks,

William

Do you use a midnight or 9am roll-over?

Midnight.

Can't look at this just now myself as we are on the move again, with limited facilities. Currently parked up for the night at a pub about 5 miles from Mark

William, can you post the source code for the affected line on the "this year" page. I'll check my tags against the ones you are using.

Steve, you should have called in for a brew, just been tidying up after decorating today. Hope it's a good pub

It's the Egerton Arms at Chelford. Very good beer, and the food wasn't bad either. Moving on tomorrow to Gloucester to possibly change the RV for a smaller one. Sorry to take the thread off topic

The web tags in use are correct according to the Sandaysoft Wiki.

They're <#YearMinTempHD> and <#YearMaxTempLD>.

Yep, those are the correct tags. I just checked my <#YearMaxTempLD> tag and it is giving "16 January" which is correct. A quick SQL query shows 1.8°C on 16-Jan as my lowest maximum. So MX is getting it right for me, which possibly points to something awry in your data files. The value is stored in year.ini, so you could just edit that file to correct the date, and the put cause down to your data reset?

*off topic* Steve, I know the pub quite well, used to go in there for lunch sometimes when I was working at Barclays, Radbrook Hall. I have never ventured there since though - too many others around the area.

Thanks, Mark! I've fixed it! Please feel free to keep talking about the pub! Steve, are you going to be visiting near me at all?

Ok, the issue has reappeared, it can't be the data, it's a problem with Cumulus MX itself. I've just had to edit the year.ini file again, surely I don't have to keep doing this? I didn't have to before.

It's possible that the code which determines the date for this year's lowest maximum gets the wrong date, and the other dates for that record correct. I'll check the code and fix it if it's wrong.

Oh, thanks very much Steve, you're a star.

I can confirm it on mine as well, since breaking that record yesterday (Thursday)

Yes, I found a bug, fixed in the next build, whenever that is.

Currently parked up for the night on a small site near Scarborough.