Adding an entry directly to a CCK field results in an entry ID with a comma at the end [#912648]

Steps to reproduce:

Add a "Kaltura Media" CCK field to a content type
Create a node and upload an image (or anything else) to the CCK field and save the node
Using devel, check the node's object. You will notice that the field's value is something like 1_283xj6es, instead of 1_283xj6es

Comments

Comment #1

chrisloos commented 26 February 2011 at 00:05

I'm having the same issue here. I can see in the table for the kaltura cck field that there's an unwanted comma at the end of the ID number. Big problem.

Comment #2

chrisloos commented 26 February 2011 at 00:12

Also, it seems to only happen when uploading new media (I tried it with a video). I edited the node that experienced the comma issue, and then used the 'Browse Interactive Videos' to select a different video in its Kaltura CCK field. This time, I browsed to a video that had already been uploaded, rather than uploading a new one. It worked, no comma. Editing the same node, and selecting the 1st video from the Browse list also worked- no comma. So this only happens when using the upload form. Hope this info helps the module maintainers debug the issue.

Comment #3

Zohar.Babin commented 26 February 2011 at 08:12

Issue tags:

+cck field, +entry id

Hey,

How does it affect the flow except for keeping the comma next to the id?

I'm guessing this field might be able to hold more than a single Id and the code that should read the id and generate a player view is able to remove the comma?.. if this is the case, than the comma at the end is not really an issue.