ERROR: ‘The Daylife module must be properly configured before you can add feeds.’

[Vineet Gupta]

Darrel

We are not able to add feeds in the module. We have configured all credentials, but when you try to add a feed, it gives the error

‘The Daylife module must be properly configured before you can add feeds.’

This needs to be fixed very urgently.

vineet

---------- Forwarded message ----------
From: Eric Spector <email address hidden>
Date: Thu, Jul 10, 2008 at 4:26 PM
Subject: Re: source filter
To: Vineet Gupta <email address hidden>

I’m having problems configuring DayLife. The message that I’m getting is ‘The Daylife module must be properly configured before you can add feeds.’

[Darrel O'Pry (dopry)]

I will need more information I could not reproduce with valid credentials, but I have found a validation error.

The steps I went through to reproduce this issue...

1) setup a new Drupal 5 installation.
2) added the Daylife.module.
3) went to admin/settings/daylife
    a. entered my access key.
    b. entered my secret.
    c. clicked the save configuration button.
    d. repeated with the following variationas .
         i. incorrect access key...validation passed, this is a bug.
         ii. incorrect secret... validation failed.
         iii. missing access key...validation failed.
         iv. missing secret... validation failed.

4) went to admin/content/daylife/add - could add feed successfully when correct credentials were in place.

I need confirmation that the correct credentials are in place and we are not simply dealing with a validation issue and an incorrect access key.

[Darrel O'Pry (dopry)]

I have a fix pending for the validation error. I assumed that Daylife would consistently respond to errors with JSON objects RPC style, and was only checking for a response->code == -2001 to determine if the credentials were invalid. However, incorrect access keys get a Restful 403 Developer Inactive responses. I remember wondering how to tell the difference between an invalid access key and invalid secret/signature when originally writing the validation. I've modified the validation to use the 403 to set invalid access key, and response->code == -2001 to set invalid secret.

The code has been pushed to trunk.

[Vineet Gupta (vineet-daylife)]

Ok so this error was happening when the developer could not use json on his server

So he switched the url on line 1230 to use phprest instead of jsonrest

And he switched json_decode on line 1330 to unserialize

I think the issue is that unserialize... Is there a way to get this to work with json and php rest data?

[Darrel O'Pry (dopry)]

revision 50 switches to phprest which should solve this issue for php < 5.2 without PECL json extension, in combination with the validation fixes in revision 49 this error should be resolved across php5.

[Darrel O'Pry (dopry)]

fix available in 1.0-alpha3.
see: https://launchpad.net/drupal-daylife/1.0/1.0-alpha