No data returned

I believe that OpenAmplify may have turned off the 1.x data feed that this module uses. I need to see if I should update to the 2.x version of OpenAmplify's service.

Exactly the same problem for me.

Tried the dev version also, none of the modules works.

Oops, my bad !

I check the log and I saw that:

Error: file_get_contents() [<a href='function.file-get-contents'>function.file-get-contents</a>]: URL file-access is disabled in the server configuration (/var/www/htdocs/site/public/sites/default/modules/querypath/QueryPath/QueryPath.php: 17)

I'll try to find a way to avoir this and report in here.

Any updates. I just started using this module and was wonderning why I could not get this working till I read the forum.

You have the same problem ?

When I save a amplified node, I get the error "Could not amplify the document. The remote server did not return the expected data."

Has there been any progress on this?

Yeah, again... the Amplify XML API has changed significantly, and I need to do a major module update. I'm swamped with work, though, and it's taking me forever. So if anyone is interested in pitching in, I'd really appreciate it.

Hi Matt,

What do you need to get your module up and running?

Basically, the module needs to be fixed to use this version of the API:

http://community.openamplify.com/content/2dot1docs.aspx

Getting started, simply changing the URL to the new API URL will get probably 80% of the way there. From there, it's just a matter of tweaking to adapt to the new XML format. And of course there are new features that could be added.

Hi, I am also experiencing the no data returned error. Has anyone worked on updating to the new API? I don't have the programming background to tackle this, but I am anxious to put this module to use. Thanks!

Hey guys! I just committed some updates to the 6.x-1.x-dev branch that should be coming online in the next dev tarball automagic build. Highlights are:

1. Updated the code to work with the v2.0 API (v2.1 still has some issues with large text blocks over ~2500 chars that I've got to suss out).
2. Optimized the code to reduce the number of OpenAmplify "transaction credits" that get sucked up (see Chapter 3.1. OpenAmplify Transaction Concept in the online docs for v2.0 for an explanation of how credits are consumed).
3. Added support for large documents to prevent the dreaded "503" timeout, per the OpenAmplify support team.
4. Changed the OpenAmplify query to use cURL instead of PHP stream contexts as these are documented to often result in HTTP 406 errors due to a combination of client and server configurations beyond our control (Google "file_get_contents http 406" to see what I'm babbling about).

So far it looks to be running as expected on my dev box which is a fairly stripped down D6.20 installation. Both "Basic Info" and "Mood" blocks appear to be working as intended.

Hopefully this will bring this module back to life while I'm working on some other optimizations and additions... Love to get some feedback from folks out there playing with this module to make sure I didn't miss anything (or botch anything).

Nobody's replied in two weeks, marking this as fixed at this point. If you find it most definitely is not, then feel free to re-open!