Module update needed for new API?
WildBill - October 13, 2009 - 19:45
| Project: | Zemanta |
| Version: | 6.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | andraz |
| Status: | closed |
Jump to:
Description
Hello,
Is a new version of the module needed in order to be compatible with the new Zemanta API that was announced recently? My Zemanta block stopped working recently (stuck on "Loading Zemanta..." forever) but I'm not sure exactly when. Is anyone else having this problem?
#1
In addition, my efforts to refresh the page and get the Zemanta block to show up have generated a lot of 404 errors in my logs (not on the screen)... so I think that's related...
#2
Hmm,
API hasn't changed in a way that would prevent old modules from working.
Which exact version of Drupal and theme are you running?
Just yesterday I was demonstrating Zemanta in Drupal 6.13 live at SF Drupal User Group meetup. :)
#3
I'm using Drupal 6.14. The theme is Newsflash, but I've switched my admin pages (including node edit) to Garland to see if that would help, but it didn't.
The 404 errors were unrelated.
But still the Zemanta block isn't showing up. I thought it might be my internet connection (sometimes very slow) but there's no activity at all while I'm waiting... no slow downloading... nothing at all. It's just dormant... "Loading Zemanta..."
#4
My system at home is a Mac using Firefox 3.5.3. However, I can confirm that I'm seeing the same issue ("Loading Zemanta..." forever) with a different computer: a PC running IE 6.
#5
I finally got the Zemanta block to display by commenting out lines 90 through 99 of zemanta.module. I'm not sure why this was required.... it shouldn't be this difficult. My hunch is that the API update in early October changed something.
#6
Same thing happened to me using Drupal 6.13. The way I see it there is some problem with gzip compression used by Zemanta's loader.js file that is not recognized as compressed javascript ... this results in syntax error. This type of compression is also not compatible with Drupal's JS optimization and caching (because Drupal puts all scripts in one file). Now, I think (it is only a guess) that the file is not really compressed on zemanta site (where the file is downloaded from) but it is compressed by webserver to optimize the transfer and that PHP somehow fails to decompress it at the end ... perhaps some php configuration problems.
What worked for me: go to your files/zemanta directory and decompress loader.js using gzip. If you are using Drupal's JS optimization also flush the cache. I am not sure how long this fix will last as a new file is probably transfered from the zemanta site when the code is updated.
#7
Whoops, forget my fix in #5 above. Commenting out the lines was simply allowing my Firefox Zemanta plugin to kick in. Which I guess is all I have left, since the module isn't working. It's a shame, because I had more confidence in the module. The fix in #6 doesn't work for me - there's nothing wrong with my loader.js, and it's not compressed.
#8
We identified the bug and we are on top of it!
Expect a fix soon!
Thanks so much for reporting this!
#9
Sweet! I look forward to the fix. Thanks!
#10
The bug has now been fixed and deployed!
Thank you so much for this bug report. Can you confirm it now works for you?
#11
Apologies for the delay, I had a non-Drupal emergency.
Yes, this fixed it. Thanks so much!
#12
Fantastic news!
I am now moving this bug from fixed to closed.
Whenever you have any more ideas/bugs/something else to report about Zemanta, don't hesitate to contact us. We love to help our users!