Firstly. my apologies for being vague. I'll give what information I can but if I was able to locate a more exact reason for this I would have fixed it myself ;)

When I try to login via the FUDforum user block it authenticates against the forum database correctly but I get a page not found error and the following unusual print for the URL.

http://www.example.com/?q=%3Ftime%3D1155845162&time=1155845162

I'm guessing this is supposed to be something like
http://www.example.com/?time=1155845162

The end result is that it logs me in via the user data provided in FUDforum but I get the above error and it does not log me in to FUDforum as well (perhaps not a part of the functionality?)

My temporary fix is to use the regular user module and I'll edit user.module to point the create new account link to fudforum's registration.

Comments

naudefj’s picture

naudefj commented

What version of Drupal are you using? I had similar problems with earlier Drupal 4.7 releases.

melchoir’s picture

melchoir commented

4.7.3 looks to be, I should have mentioned that earlier. Also using Gentoo, Apache 2.2.3 (custom build not emerged, but nothing too unusual), and php 5.1.4 (same story). mysql 4.1.21

naudefj’s picture

naudefj commented

I've scanned through the code, but cannot see how it would be generate such URLs.

Can you please debug the code to see where things go wrong? I would like to do it myself, but I cannot simulate the problem right now (Drupal 4.7.3).

djpumpkin’s picture

djpumpkin commented

I have exactly the same problem. I have the odd time format:
http://www.mysite.com/%3Ftime%3D1157323258?time=1157323258

Followed by a 'page not found' message.

Is this module intended to sync log in status between the forum and drupal - so if one logs into a drupal site they don't have to log in to the integrated forum?

This would be fantastic if it could be fixed.

I am running drupal 4.3.7, PHP 4.3.11, MySQL 4.0.25

djpumpkin’s picture

djpumpkin commented

I meant to say I'm running Drupal 4.7.3

vm’s picture

vm commented
Status: Active » Closed (won't fix)

This was an issue with Drual and not with the module itself. The issue was fixed with the release of Drupal 4.7.4