[TYPO3-calendar] MonthView endPointCorrection

[Yilmaz Backir]

Am 29.10.2011 21:34, schrieb Thomas Kowtsch:
> Hi Yilmaz,
>
> On 29.10.2011 20:07, address_is at invalid.invalid wrote:
>> Thomas Kowtsch<thomas at kowtsch.de> wrote:
>>> On 29.10.2011 06:23, Yilmaz Backir wrote:
>>>> I am using cal version 1.3.3 and CSS-based template (cal) in my own
>>>> lib.ext_cal (mot in the root template).
>>> Wooops. This makes the world a bit more difficult since lots of things
>>> got changed (and fixed) in the meantime; and we lost our svn
>>> history...
>  > [...]
>> No I do not use recurring events. Would be very happy to get a solution
>> for this problem.
>
> I found it; but you need to patch your cal instance manually (which does
> not really matter b/c once you update to v1.4 or newer, this will be
> included anyway).
>
> You need to change ./cal/service/class.tx_cal_event_service.php
>
> Somewhere around line 131, you can find two statements that get attached
> to the SQL queries.
>
> You need to remove the // from the first line and coment out the second
> one:
>
> $additionalWhere = $calendarSearchString.' AND tx_cal_event.pid IN
> ('.$pidList.') '.$this->cObj->enableFields('tx_cal_event').' AND
> ((tx_cal_event.start_date>='.$formattedStarttime.' AND
> tx_cal_event.start_date<='.$formattedEndtime.') OR
> (tx_cal_event.end_date<='.$formattedEndtime.' AND
> tx_cal_event.end_date>='.$formattedStarttime.') OR
> (tx_cal_event.end_date>='.$formattedEndtime.' AND
> tx_cal_event.start_date<='.$formattedStarttime.')' . $recurringClause .
> ')'.$additionalWhere;
>
> //$additionalWhere = $calendarSearchString.' AND tx_cal_event.pid IN
> ('.$pidList.') '.$this->cObj->enableFields('tx_cal_event').' AND
> ((tx_cal_event.start_date>='.$formattedEndtime.' OR
> tx_cal_event.end_date>='.$formattedStarttime.')' . $recurringClause .
> ')'.$additionalWhere;
>
> This should do the work for you.
>
> In any case, I highly recommend to switch over to v1.4.2 (current
> SVN-version, to be released pretty soon) because lots of other bugs got
> resolved in the meantime and due to the missing svn history, it gets
> very hard for us to reproduce problems...
>
> Regards,
>
> Thomas
>

Hi Thomas,

thank you so much, it works fine now!

I will follow your recommendation and switch to the v1.4.2 asap.

Kind regards,

Yilmaz