[horde] Kronolith month view broken

[Jan Schneider]

Zitat von Ruud Baart <r.j.baart at prompt.nl>:

> Sorry,  I meant is it solved in the upcoming kronolith 4.2.4 version?
>
> Yes, I have a test system and no, I don't follow blindly all the  
> updates of Horde.  I don't have a complicated or weird horde system  
> (Debian wheezy and postgres). So I don't hing I have a very  
> particular configuration. But when versions are declared stable I  
> assume I can install them. I install them on a test system, take a  
> look around and when I found nothing weird I install the updates on  
> the production server. I can't test everything. This looks like a  
> normal procedure to me.
>
> I report a bug and I ask whether the bug is known and solved in the  
> next version of kronolith. That's all. I have a great respect for  
> all Horde developers.
>
> Arjen de Korte schreef op 18-11-2014 om 16:31:
>> Citeren Ruud Baart <r.j.baart at prompt.nl>:
>>
>>> In one of the previous versions of Horde the month view of  
>>> Kronolith was broken. It was solved in the previous version(s).  
>>> Now with the latest versions of all modules there is again a  
>>> problem with the month view. No appointments are shown after  
>>> today. All other views (week, day etc.) are as far as I can see OK.
>>>
>>> Is this bug solved by version 4.2.2? One of the changes is:
>>>
>>>    Fix JS error in month view with more events today than the  
>>> maximum threshold.
>>>
>>> If so, when will it become available? So I can tell my users.
>>
>> Why don't you just try this out on a test system?
>>
>> Given the all the different configurations Horde supports, you  
>> should never assume that *your* particular configuration will not  
>> break upon upgrading. Rather than upsetting your users with broken  
>> webmail/agenda, you really should test new versions on a separate  
>> installation where you can try out things.
>>
>> Blindly running 'pear upgrade' on a production system is a recipe  
>> for disaster...
>>
>> Best regards, Arjen

And to answer your actual question: yes this is fixed with the next release.

-- 
Jan Schneider
The Horde Project
http://www.horde.org/
https://www.facebook.com/hordeproject