Notification subscription problem

[tonreproc]

Hi Alec,

no, I was not logged in when I tried to unsubsrcibe.

Regards,
COr

[asmecher]

Hi Cor,

Hmm, we must have different implementations of the subscribeGuest function in classes/notification/NotificationSettingsDAO.inc.php; look for a call to the $accessKeyManager->createKey. What do you see for that call? I have:

Code: Select all

$password = $accessKeyManager->createKey('MailListContext', $assocId, $assocId, 60); // 60 days

Regards,
Alec Smecher
Public Knowledge Project Team

[tonreproc]

Hi Alec,

here I find in line 290:
$password = $accessKeyManager->createKey('MailListContext', $assocId, $assocId, 60); // 60 days

that looks the same as what you mailed me.

Regards,
Cor

[asmecher]

Hi Cor,

We must be garbling information somehow. From your previous post, you're getting the following debug information when you unsubscribe:

The context is MailListContext
The userId is 58
The keyHash is 6f0e4e910716394477c4e3ef63b75014
The assocId is (nothing here)

This should correspond to the following in check in the DB:

Code: Select all

SELECT * FROM access_keys WHERE context = 'MailListContext' AND key_hash = '6f0e4e910716394477c4e3ef63b75014' AND user_id = 58 AND expiry_date > now();

This is not returning a result, when it should be. Can you check in the DB to see what of these fields is not matching properly?

Regards,
Alec Smecher
Public Knowledge Project Team

[tonreproc]

Dear Alec,

the record in the access_keys table with key_hash = '6f0e4e910716394477c4e3ef63b75014' reads:

Edit Delete 39 MailListContext 6f0e4e910716394477c4e3ef63b75014 62 62 2011-03-06 19:40:44

so the userid is 62 not 58. Beats me.

The record with userid=58 looks like:
Edit Delete 35 MailListContext e2903996aae61452094b6a291f04197b 58 58 2011-03-05 21:35:54

Regards,
Cor

[tonreproc]

Dear Alec,

do you think there is a possible way out of the problem?

Cordial regards,
Cor

[asmecher]

Hi Cor,

I passed this thread along to the developer who wrote that code; he should be getting back to you shortly. As you can see, it's sometimes very difficult to debug remotely, so you'll have to be patient.

Regards,
Alec Smecher
Public Knowledge Project Team