[ 
https://issues.apache.org/jira/browse/OFBIZ-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772009#comment-16772009
 ] 

Jacques Le Roux commented on OFBIZ-10595:
-----------------------------------------

OK, this is exactly what I have done
# Started from scratch as explained above
# Got to https://localhost:8443/workeffort/control/FindICalendars
# Copied https://localhost:8443/iCalendar/CALENDAR_PUB_DEMO/ from there
# Created a demo calendar and synced it
# Created a new event
Works, no warning icon, the default event and new one are created and showing

# Created a new public test calendar
# Got to https://localhost:8443/workeffort/control/FindICalendars
# Copied https://localhost:8443/iCalendar/10002/ from there (why 10002 instead 
of 10000, don't ask, anyway only 2 calendars)
# Created a test calendar and synced it
# Created a new event
Works, no warning icon, the event is created and showing

So it seems this solution is session dependent or something. I'll try again 
later today after restarting the instance (more than 1h, session duration)


> The query iCalendar/CALENDAR_PUB_DEMO/ no longer works
> ------------------------------------------------------
>
>                 Key: OFBIZ-10595
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10595
>             Project: OFBiz
>          Issue Type: Bug
>          Components: workeffort
>    Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 16.11.06
>
>         Attachments: Image 001.png, iCalendar.patch, iCalendar.patch
>
>
> ControlFilter does not allow the untypical iCalendar/CALENDAR_PUB_DEMO/ query 
> to pass.
> This feature works in the stable version. So it's a change since then
> Thanks to Jyri Sillanpaa for the detailled report: 
> https://markmail.org/message/pfd62nom3ftnpgll



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to