I'm getting one that might be a system bug. In the news module, there are those links at the bottom to view additional pages (1, 2, 3, etc) the PHPSESSID is showing in the links on my site. They don't show on the XOOPS site (go figure, the broken appliance always works for the repair man).

Any idea what causes that? I didn't hack any modules, especially the news engine.

Could this possibly be a PHP system option causing problems?

I'm using XOOPS 2.0.6 on a Debian (stable) linux box running PHP 4.3.3

Normally, this case occures when it failed to create a cookie file on your computer ... so it uses the adress link to store it.

In other words, if the user doesn't allow cookies, it stores it in the URL?

But when I test the page, I'm allowing cookies. There's gotta be some other issue at hand, as if the test isn't working, or something.

So I was able to get rid of PHPSESSID, or so I thought.

There's an option in the General Preferences Admin panel called 'Use Custom Session'. If I uncheck that, it dissappears. Now I don't know what that option is really for -- I thought it allowed logins. But people can still log in. What is that option for?

So I pull up the web page now, regardless of whether or not I'm logged in, and the PHPSESSID tags are missing. But then I go to W3C's Validator, and it still sees it. I'm completely baffled by that one. I checked my source....it's not there.

So I'm even more baffled now than I was before. And Validator still spits out a bunch of erors pertaing to the PHPSESSID tag -- and only the PHPSESSID tag.

Hi,

Hm, yes I know that's quite an old topic, but maybe it will help someone :

I have noticed that if you add the full path in the templates (eg : "<{$xoops_url}>/modules/mylinks/visit.php" instead of the default "visit.php"), the PHPSESSID disappears (and that makes the W3C validator happy ).