Colorpicker CCK

Testing required here, let me get back to you. One quick question, just to eliminate the obvious, do you have JavaScript enabled (required for this module)?

This is probably caused by a bug discussed here: #352761: warning: Missing argument 1

subscribe

subscribe

I confirm having the same error

container is undefined
[Break on this error] return container.farbtastic || (contai...Query._farbtastic(container, callback));

Hello, this should be a great module, but all of 6.x versions don't displays the CCK field if I added to a content type, and then I going to create a content with this type.

Otherway, this will be really a significant module for CCK, so keep up the good work!

Thanks.

subscribe

Sorry folks, I've been pretty busy with real life stuff outside of school. I haven't had a chance to look at this module for a while. I suspect it might be a while before I get back into active Drupal development. If you want to submit patches that you've tested, I'm sure Skilip (or myself if I get a free moment) can commit them.

Thanks,

Dave

same problem ... subscribe

and i thought i was losing my mind! the colorpicker and colortext fields also don't appear on edit node screens for me. subscribing...

Sorry guys, both dwees and me are too busy ATM for replieing faster in colorpockers issuequeue. I will do my best to fix this this WE.

I needed a colorpicker cck field so I gave it a go - upgrading the cck module to work with Drupal 6. The module takes a slightly different approach than the orginal module.

I hope this helps get the module upgraded to work with Drupal 6 sooner.

Known bugs: only one field per node... not sure why multiple fields don't work. Perhaps someone has an idea?

Cheers,

Alex

subscribe

I've committed a RC1 wich is ready for testing.

The new RC1 works for me...

The only thing that you might consider changing is how default values are handled when a colorpicker textfield is added to an existing node. At the moment it'll always default to red regardless of how you set the default value in the widget settings.

changing this line

  $value = isset($element['#value'][$field_key]) ? $element['#value'][$field_key] : '#FF0000';

to this fixes it

  $value = isset($element['#value'][$field_key]) ? $element['#value'][$field_key] : $field['widget']['default_value'][$element['#delta']]['value'];

But this probably means we need to ensure that a default value is always set.

Thanks for the good work...

Alex

Just one problem found on RC1:
Using multiple values you can't delete fields. So if you add 3 colors to your node, you cannot remove any, just add more.
And it even adds one value every time you edit your node.

Thanks for the work anyway!

Claudio

Thanks for reporting guys!

subscribing