Hi guys,

elementdefaults is great! I find it very useful for situations where prepopulate might be too much.

While I'm falling in love with elementdefault's over-all performance, I'm kinda wondering if the other contributed-module fields will be supported as well.

Right now, I have strong emotional attachment with the following:

There are some modules that provide fields without the 'name' input parameter when rendered (such as Active Tags' input field). How do we address this with elementdefaults?

Thanks much,

Marc Robinsone

Comments

ershov.andrey’s picture

Check out version 6.x-1.4 of module. We add CCK Taxonomy support and Email support. Location API field is more complex and in this version does not support yet.

marcrobinsone’s picture

Version: 6.x-1.1 » 6.x-1.4

Hi Andrey,

Is there a special way to populate content taxonomy fields via url?

In my case, I tried populating the following content taxonomy fields:
--------------------------------------------------------------------------------
* checkbox
* select/multiple
* autocomplete

and I tried using the following (input properties) as parameters:
--------------------------------------------------------------------------------
* field name //example: field_taxonomy[value][321]
* field id //example: edit-field_taxonomy-value-321

such that it forms: http://examplesite.com/node/add/page?field_taxonomy[value][321]=checked

However, I can't seem to make it work. I even tried the solution you specified on this post, but no luck either. Usually this method works for form-api rendered checkboxes, but not for these kind of fields (I know you mentioned it does already).

By the way, I'm using elementdefaults 6.x-1.4 and content_taxonomy 6.x-1.0-rc2.

Am I missing something?

I would really appreciate your directions/guidelines on this...

Thanks!

bluestarstudios’s picture

This is a great module!
Thanks!

Can somebody please tell me how to populate a Node Reference using the "Nodereference Image Helper" module? Please help. Need this urgently.

ershov.andrey’s picture

to marcrobinsone:

We find the bug in version 1.4 with content taxonomy autocomplete widget and we will fix it in future release.
But two other widget style works fine. For populate values to content taxonomy field you need to write the name of field exactly as you give it on "Add new field" page. For example, if you give "field_cck_taxonomy" name to field, than you can populate it with url http://site.com/path_to_page_with_form?field_cck_taxonomy=1||2||3, where 1, 2, 3 - are termIDs.