Jump to:
| Project: | Embedded Media Field |
| Version: | 6.x-1.7 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
I'm trying to upgrade a site from emfield 6.x-1.7 to 6.x-1.15. When I run updates, _emfield_update_fix_data() never finishes. A few bits of information:
$result = db_query_range("SELECT * FROM {{$context['sandbox']['table']}} WHERE vid > %d ORDER BY nid ASC", $context['sandbox']['current_node'], 0, $limit); is called with vid being equal to the highest vid in the table.
This causes the while loop at line 190 to return FALSE, and means that the progress variable is never incremented.
Strangely enough, in my case progress is stopping at 365, while the max variable is 581. So perhaps the issue is deeper then I think. I think the fix might just be to check if no rows are returned and set the finished variable to 1, but I'm not really clear as to what the entire function is doing.
I checked -dev and it currently also has the same issue.
Comments
#1
whoops! looks like it's the order by nid, whereas we're filtering on vid. i've fixed this in the dev version. please re-open if you still have the problem.
thanks!
#2
Thanks - the latest -dev now properly updates for me.
#3
I am using 6.x-1.17 and experiencing this. When I run update.php it hangs at 98%..
#4
I tried the Dev from 2009-Nov-20. Same deal. Now I'm seeing the following in my logs : Could not connect to youtube, HTTP error 404
#5
I'm pretty sure that the update connects to various providers to update metadata. Perhaps your host is blocking external HTTP requests? When you SSH into your server, can you wget / curl files over HTTP?
#6
@deviantintegral
Thank you for replying. In my logs, where the error is being displayed, I see the locations as: /taxonomy/term/23/all/feed
I've been using emfield 6.x. 1.0 for close to a year now with no issues. This only came up after upgrading to 6.x.1.17
Example:
Type emfield
Date Saturday, November 28, 2009 - 09:49
User Anonymous
Location http://www..../taxonomy/term/23/all/feed
Referrer
Message Could not connect to youtube, HTTP error 404
Severity warning
Hostname 188.*.42.*
Operations
#7
It still sounds like your webserver can't contact YouTube and is being blocked. Many ISPs block *outgoing* HTTP requests from websites. Does update status work on your site?
#8
Yeah update status works no problems. The module has worked seamlessly close to a year till this update. According to that error it cannot contact youtub on a RSS feed page.
Type emfield
Date Saturday, November 28, 2009 - 09:49
User Anonymous
Location http://www..../taxonomy/term/23/all/feed
Referrer
Message Could not connect to youtube, HTTP error 404
Severity warning
Hostname 188.*.42.*
Operations
#9
Whatever your issue is, it looks like it's unrelated to the bug initially filed for this issue. You should open a new issue (and search again for existing ones) describing your problem.
#10
It only occurred after update.php failed to run after the upgrade. Highly relevant and not fixed. Even with the dev update.php did not complete, and it's since that event that these errors are being logged. Thank you.
http://drupal.org/node/625822#comment-2314504
#11
@HS: Please stop hijacking this thread. Your issue, though serious, has nothing to do with the reported (and resolved) issue in this thread. I strongly suspect that it was a coincidence that you discovered the error during update, as it seems to be a problem communicating with YouTube, rather than the update per se (which coincidentally attempts to query YouTube). Please open a new issue (and feel free to link to this issue for cross-reference). Otherwise, people who may be subscribed to this issue will experience unnecessary and unwanted spam. It also helps keep the issue queue clean and manageable.
#12
@ Aaron
How do you suspect this is a coincidence?
Thanks. I will start a new thread but it will have the same topic as update status did not complete.
I couldn't care less about the youtube issue because I have not lost functionality. My concern is that update.php did not complete.
It did not complete even with the Dev version as suggested in this thread! Why would I then start a new issue???
#13
@HS: How many nodes w/ youtube videos do you have on your site?
#14
setting back to active till we sort this out
#15
@aaron,
Thanks for looking into this mate.
I have approx. over 50 but below 100. I hope that is not too broad a response.
#16
No, that's fine, I was just exploring possibilities. YouTube has a limit of 50,000 API calls per day, which might be a problem on monster sites. But it sounds like you're well within the limit. (emfield caches the API calls too, to help ensure sites stay in the limit even with high volume).