Post new reply

Doss,
I did some testing and analyzing and came to the following conclusions:
1. Using firefox, edge, chrome, opera and safari I could reproduce the same problem by using an iframe to load a calendar from an other domain.
2. In all browsers the problem was identical: Session expired - 'no session cookie' message in the bottom status bar.
3. I searched the web for a reason and found that cookies cannot be used cross-domain.

Item 3 means that the calendar (or any program) in domain x, loaded in an iframe of a website in domain y cannot set cookies in the browser visiting domain y.
Consequently when the calendar in domain x cannot set a cookie in the browser visiting domain y, the calendar cannot function. The display of the initial calendar page will work, but as soon as the user tries to go to an other calendar page, a PHP session is needed (to remember the user) and PHP sessions use a cookie to store the session ID.

Why it works for you in safari, is a mystery to me. For me it didn't work in any browser.

Roel

Schwartz : Thanks for the words of support.

Roel :
Thanks for the prompt reply.  Have changed calendar root index to $calPath = '/'; flushed the browsers cache, etc. and (still) have the same outcome : Full functionality on safari / post successful load; 'Session expired - restart' error message in center of the calendar frame, and 'no session cookie' in the status bar after successful load with edge and chrome.

Hello Doss,
I'm not sure but . . . .
You are using the calendar cross server. In this case it could be that because of security measures in the calendar it is a problem to set a PHP session cookie.
The fact that it works with safari maybe means that safari is a little bit less strict w.r.t the cookie path.

Could you try the following:
- edit the index.php file (in the calendar root) and
- change line 78 ($calPath = . . . .) into

$calPath = '/';

If this doesn't solve your problem, please let me know. I will then try to reproduce the problem and analyze it.
Roel

Hello Doss

I don't think you are doing anything stupid.
I often use an iframe to display the calendar. Also calendars from other domains.

It has clearly something to do with the session-cookie. Maybe the creation of the cookie is made by some PHP and that the server with the iframe, prevents the cookie to be created.
I think we need some help from Roel.