Martin Kliehm

As I said, your server needs to be connected to the Internet on a domain so that Amazon can fetch the XSL file. If you run your own server at localhost that is not possible. In the meantime I changed the error messages so that they give a more detailed feedback on the cause of the error. Still you need to run the plugin on a real web server with an IP address and DNS entry connected to a domain.

@ed4becky: you confused me with that mapping orgy… Anyway, does that mean you are using WordPress MU, or the single install of WordPress? Recently I tried to use my plugin on a MU site, and I had a similar error. However, there were none with ordinary WordPress installs.

I’m sorry you’re having trouble getting started. Indeed your question is not in the FAQ (yet), but there is detailed information about this on the plugin homepage.

The error message means you are running the blog on something like localhost. AWS needs to get an XML file from your server, obviously that is impossible when it’s not located on a server that can be accessed with a public IP address from the outside.

Hi Shageman,

sorry for the late reply, I didn’t monitor this page. Why didn’t you post on the plugin’s page? Anyway, I think I fixed the problem, but I can’t test it because I have no idea which widget you are referring to. Could you please provide a link?

Thanks, Martin

It still worked in posts and in the sidebar, alas there was a bug that prevented the display of items on the home page. That is fixed in version 1.1.0 now.