Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I can open the browser and choose a video. The video thumbnail is shown in my cck fied. But nothing is stored.
As soon as I edit the node again, there is no vimeo data at all.
Any idea?
Comments
Comment #1
Fanaile CreditAttribution: Fanaile commentedI'm having this same issue with version 6.x-1.0-beta1.
In Firefox, I can select the video; when I try to save or preview nothing gets stored. On save nothing appears at all and when I click on edit there's nothing in the Vimeo field. On preview the edit page comes back up and there is nothing in the Vimeo field. But in both cases the "remove" link is there - as if the page thinks there's something there.
In IE8, I wasn't able to even get the video inserted. The browser would come up and I could choose the source, but as soon as I clicked on it the box seemed to freeze (the arrow still moved though).
Comment #2
jdwfly CreditAttribution: jdwfly commentedMarked #1046698: Video Array is EMPTY duplicate of this.
I find it strange that I haven't run into this problem. I'm using the module extensively and everything is working fine.
Comment #3
magb27 CreditAttribution: magb27 commentedSame problem here.
When node is saved, on DB nothing is stored see (db_01.PNG).
I tried inserting any clip id there, for example (20002979). see (db_02.PNG)... but same result.. see(vimeo_on_page.png)
And finally I inspecting the code on page I found the follwing
"http://vimeo.com/moogaloop.swf?clip_id=&server=vimeo.com&show_title=1&sh..."
Look at clip_id field... no clip_id is added.. but if you insert this code (20002979), it works.
So.. something is not working well nor at DB or nor at code... I will try to find this bug, but it will be nice if someone confirm too if this is a bug
Comment #4
magb27 CreditAttribution: magb27 commentedMay be for help...
Uploading only one video, cache table shows this, see(db_03.PNG)...
Comment #5
magb27 CreditAttribution: magb27 commentedGood News...
I'm trying to know what I done, but now it works. It could be neccesary a time for vimeo to recognise your account, or some thing like to check your url from what you are trying to get video clip???
Recently I solved a trouble with my php library mcrypt... I will check this posibility and I will post it.
Comment #6
lauri CreditAttribution: lauri commentedI had this same problem with 6.x-1.0-beta1. After hours of debugging I was able to resolve this problem simply by changing the field name to "field_vimeo".
It seems that at least the beta version still has some hardcoded field names here and there and it expects to find "field_vimeo".
Otherwise good job! Very nice UI and seems to work well.
Comment #7
lauri CreditAttribution: lauri commentedOK, it seems I was bit too hasty on my analysis. After some testing and quick code review, I think the root cause was that I had an underscore in the user defined part of the field name (field_vimeo_video). field_video, field_vimeovideo both work fine, but break as soon as I add another underscore in the name.
I was also able to get rid of that cache row with empty cid (and the error messages cause by it) shown in post #4, by adding the following row:
It's a bit ugly hack, but doesn't seem to break anything. I didn't bother to find out why the function gets called with the empty string in the first place.
Comment #8
EvaldsUrtans CreditAttribution: EvaldsUrtans commentedThank you!!!
this is the way to fix it:
"I had this same problem with 6.x-1.0-beta1. After hours of debugging I was able to resolve this problem simply by changing the field name to "field_vimeo"."
Comment #9
manischewitzbacon CreditAttribution: manischewitzbacon commentedI can confirm that removing an underscore from my field name fixed my problems as well...
i'm guessing it starts around line 1002 of vimeo.module:
$field_name = explode('_', $element['#field_name']);
as you then use
$field_name[1]
in a bunch of places.
maybe replacing line 1002 with
$field_name = str_replace('field_', $element['#field_name']);
then just using $field_name as a string instead of an array would fix this??