I have two problems with TS node_referenced fields, while js is enabled.

1: The "default value" selector always keeps the first term (sorted alphabetically)
This is on page: admin/content/types/nodetype/fields/field_nodereference. See attached image #9
Here "Credits et mention" is the right term for me. But if I select another term as default, I always get "Credit et mentions" as default choice in the node add/edit page. Going back to this node_reference field page witnesses that the default choice had not been stored. This is a problem if I need another set up or if I add a term which would rank first alphabetically in my Texte vocab.

2: The "referenced node" is stored but wipped out when editing the node again
Once the referenced node is selected in the node add/edit page (still with problem 1 mentioned above), it is stored and the node view page shows it correctly. Yet when editing the node, the nodereference fieldset shows the first term from the selected vocab (pb 1) but without the previously referenced node ("None" is displayed). See attached image #11.

This are two serious problems, especially n°2. What would you need to help you tracking this bug out?

Greetings, Arsène

CommentFileSizeAuthor
Image 11.png10.4 KBdoc2@drupalfr.org
Image 9.png24.74 KBdoc2@drupalfr.org

Comments

markfoodyburton’s picture

markfoodyburton commented

MMmm
these seem to be related problems

I've just made a new release of the module, but I'm afraid I did not look at this code,

I will TRY and look at it sometime this week, but I dont have a lot of time right now....

Please contact me directly and I can let you know how I am getting on (BTW, I'm near Bordeaux, I guess you are in France too :-))

keithmorr’s picture

keithmorr commented

First, thank you for an excellent module, it is the only module I have found that suits my needs to have a large taxonomy list made easily manageable for my users.

In addition to the items listed above that I also am having a problem with there is one other item that would be good to add.

I would like the module to be able to link the selector field to the node so that I can later search using that field. For example, I use the module to select airports that are available in each US state. Therefore the user first select the state and then then is presented with a lising of the airports refined to only be in that state. Later when they are searching the content I would like them to be able to sort by looking for the state. Since right now that information is not stored in the node it is impossible to do so.

Please let me know if this is clear and if t would be possible to add this functionality.

Thanks!!!!!

doc2@drupalfr.org’s picture

doc2@drupalfr.org commented

Dear keithmorr, this is a feature request you're asking for and therefore, eventhough I'm interested in it, I should say that it should be a different topic.
Anyways, have you tried the hierarchical select module? That MIGHT do what you want.

keithmorr’s picture

keithmorr commented
Status: Active » Closed (fixed)