monthlyrecord.php problem - need help

[mm23]

I have a problem with this: http://www.vrijemeusibeniku.com/weather ... record.php
So, if you "click" on "Sij" which is actually January you can see in some rows that is a "veljaca" (February) appears. It seems to me that is a all ok with my php script. Maybe It is a something with Cumulus?
PHP file attached.............
Somebody help me please?

[steve]

What do the corresponding dates look like in Cumulus itself? What (in English) are the items for which the dates are apparently in the wrong month? If they are wrong in Cumulus itself, what does the record editor in Cumulus find for those items when you get it to fetch the data from the log files?

There's an error in your template here:

<#ByMonthLowDailyTempRangeT mon=1format="d. mmmm, h:mm 'h'." >

You can't run parameters together, the parser has no way of knowing where each one ends if you do that. You need to check your template carefully yourself to see if there are any other similar errors.

Edit: And another one: <#ByMonthMonthlyRainHT mon=4format="d. mmmm, h:mm 'h'." >

[mm23]

Thanks for your reply Steve,

.....on which parameters exactly do you mean ...... the temperature and time?
Details are correct. For example, in the first line of siječanj (January) which is for the maximum temperature, the data for February is correct, however on this place should stand a maximum temperature for January not for February
Now I am removed date format, but it still shows the date for February (veljača) http://www.vrijemeusibeniku.com/weather ... record.php
.... all wrong dates (February instead of January) is for February 1.

I have to say that for January I have data measured for only one (January 31 - beginning of a measuring) day

[steve]

I mean this:

mon=1format="d. mmmm, h:mm 'h'."

There has to be a space between parameters:

mon=1 format="d. mmmm, h:mm 'h'."

But if you've removed the format now, then that (now) clearly isn't the problem. Perhaps it's because you only have data for January 31st. All of my dates are correct, so it must be something to do with your data, or your template. Have you checked it carefully? And did you not see all the other questions that I asked? The first thing to establish is whether the problem is in the data in Cumulus or just on the web page.

[mm23]

Steve,

the problem is solved (almost). In monthly all time editor I copied the data from the log value. Data in dayfile value were also inaccurate (for January were displayed data for February, which was the problem actually) .....How is it possible?
In any case I would not bother with it more. Anyway measurement is in the test phase still and all previously measured data will be erased, hope soon ...
Thanks for your help.....