1.5.1 with serendipity_plugin_currently problem

[tizroc]

I recently upgraded to 1.5.1 and began having problems with the front page of my blog. If I had anything in one of the entries for the plugin (examples would What I am currently Reading, Listening to, Watching etc...). Which ever row of sidebars I place the serendipity_plugin_currently in nothing appears in that row except the words of my entry. All frames/boxes (depending on skin) are gone including the ones in that row.

I have removed and re-installed the plugin. Tried moving it to all available areas of the site. I cannot say with 100% certainty but I believe the previous version installed of serendipity_plugin_currently worked with 1.5.1 okay. It seems to have been when I upgraded the plugin that this began to effect the blog, however I did all the upgrades the same day and I cannot be 100% sure that is the case.

I have the newest version of the serendipity_plugin_currently which is 2.1

I have tried several times to upload a screenshot of the website but every time I do it returns an error saying the server is unavailable. I can re-send or link it if that is necessary.

[garvinhicking]

Hi!

Could you maybe post the URL to your blog with that problem? The HTML source would reveal much more information rather than a screenshot...

Best regards,
Garvin

[tizroc]

Just to clarify. You would like me to put the plugin back in play and send you the link? That isn't a problem. If I have not understood you please re-send your instructions.

-Forest
http://www.undsoweiter.net/serendipity/

[garvinhicking]

Hi!

Okay, what seems to happen is that a fatal PHP error prevents the site from emitting its complete content.

It seems you have PHP error reporting off, can you edit your .htaccess file and insert

Code: Select all

php_value display_errors On

at the top of the file, and then see if you see an error message in your blog? This should lead us to further clues.

Thanks,
Garvin

[tizroc]

Here is what I have in response to your suggestion to turn the .htaccess to 11. (joke)

Fatal error: Uncaught SoapFault exception: [aws:Client.RequestExpired] Request has expired. Timestamp date is 2010-01-11T10:48:11Z. in /htdocs/undsoweiter/serendipity/plugins/serendipity_plugin_currently/soap.inc:36 Stack trace: #0 [internal function]: SoapClient->__call('ItemSearch', Array) #1 /htdocs/undsoweiter/serendipity/plugins/serendipity_plugin_currently/soap.inc(36): SoapClient->ItemSearch(Object(SoapVar)) #2 /htdocs/undsoweiter/serendipity/plugins/serendipity_plugin_currently/serendipity_plugin_currently.php(204): find_best_image('The Doors - ', 'Music', 'US', '', '', '') #3 /htdocs/undsoweiter/serendipity/plugins/serendipity_plugin_currently/serendipity_plugin_currently.php(289): serendipity_plugin_currently->search_database('The Doors - ', 'Music', 'US') #4 /htdocs/undsoweiter/serendipity/include/plugin_api.inc.php(850): serendipity_plugin_currently->generate_content('Currently...') #5 /htdocs/undsoweiter/serendipity/include/functions_smarty.inc.php(603): serendipity_plugin_api::generate_plugins('right') #6 /h in /htdocs/undsoweiter/serendipity/plugins/serendipity_plugin_currently/soap.inc on line 36

I don't know what apparently changed between one revision and another that is causing php to error, if that is what is happening. My php-fu is not very strong.

[garvinhicking]

Hi!

Hm, did you enter your amazon associates ID etc. inside the plugin config? Amazon changed its webapi recently, so the old way shouldn't work anymore, and the new one requires this ID...

Regards,
Garvin

[tizroc]

Actually the search string appears alright, you can still do searched without logging in. (I spend a lot of time on Amazon). The associate tag they are talking about is for agents who have created corporate accounts and make money off of linked sales from users on my end(merchant agent "on demand"). I looked it up the first time I put that pluginin (back when it was like 1.2 or something)

[garvinhicking]

Hi!

Hm, I thought that the ID is required for any API requests that the plugin makes. I don't use the plugin myself, maybe Dustin Hawkins can help (the author of the plugin): http://dustinhawkins.com/

HTH,
Garvin

[tizroc]

Thank you.. apparently (according to his website) he was aware that the client API has to be signed but the soap request method is supposed to work around it. I will see if I can chat him up.