Due to this line in function user_logged_in, the module will fail with a rather meaningless error message for anyone not using PHPSESSID as their session cookie name:
$sid = $_COOKIE['PHPSESSID'];
This is often changed by people who run more than one PHP app on the same server (like me). IMHO this should be an option in the config section.

Comments

sbouckae’s picture

sbouckae commented

I have been trying to get the Webcalendar integration to work today on a Drupal 5.2 install without success. The problem I have is probably closely related to the hard-coded cookie name. From what I have found, it seems that Drupal 5.2 is now generating a unique cookie name for every installation. This causes following error when trying to visit the calendar page:

"Warning: assert() [function.assert]: Assertion "! empty ( $user )" failed in /WWW/webcalendar/includes/access.php on line 335"

This error disappears when changing $sid = $_COOKIE['PHPSESSID']; in user-app-drupal.php to point to the correct cookie name (which looks something like SESS9e9e5800e0f49b00d3a6eab70c5143d). However, problems remain: when I try to visit the calendar page, I can see that month.php is called, but then the browser (both firefox and IE) keeps 'pingponging' between /webcal and month.php. Month.php is never executed any further than the first line of code (include_once 'includes/init.php').

I've been trying to find a solution but without any luck.

Perhaps a good thing to mention: I am trying to get webcalendar 1.1.3 to work instead of the suggested 1.1.2 version. However, looking at the changes between 1.1.3 and 1.1.2, I doubt that the Webcalender version is causing the problem.

atratus’s picture

atratus commented

Take a look at what I posted under http://drupal.org/node/176815 and see if it helps with this issue. I think it will.

unicorn2k5’s picture

unicorn2k5 commented

After hours of trying to get webcal work with drupal 5.6 and webcalendar 1.1.6, i finally succeeded!! Nothing of the ideas mentioned above had worked, so I (as act of exasperation, because I doubted that it would make any difference) downgraded webcalendar from 1.1.6 to 1.1.2 (as this was the version the module was tested) and look: it worked!!!!!

duaelfr’s picture

duaelfr
he/him
Primary language French
Location Montpellier, France
commented
Status: Active » Closed (won't fix)

This version of WebCalendar integration is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.

This issue has been automagically closed by a script.