Hi

I have improved the user interface of node_widget with some major changes:

  • All items were now listed as table (more compact display)
  • Support for more node types (current version supports only one node type)
  • Duplication of nodes and linking of nodes
  • Per field prepopulation settings

For those new features i have made some changes on the ground of the code. All the multi value handling is now inside the module and not any more in the content module. There are also some other changes in the handling of the display of items, but the "modules" for the fields were complete recycled without any big change.

You could see some screenshots below. Now i want to ask if there are some interests to implement this changes to node_widget module or should I start a new project?

CommentFileSizeAuthor
#2 nodereference_widget.tar_.gz15.71 KBcustomweb
settings.png64.88 KBcustomweb
multi-node-types.png47.64 KBcustomweb
node-2.png41.43 KBcustomweb
node-1.png39.4 KBcustomweb

Comments

ademarco’s picture

ademarco commented

Very interesting, especially the custom multi-value handling. Could you submit a patch with those changes?

customweb’s picture

customweb commented
StatusFileSize
new nodereference_widget.tar_.gz15.71 KB

I have rename the whole project, because of development. My changes replaces the "unformatted" view of the node. So I dont think it make sense to submit a patch. I submit only the whole new module.
If there are interests in merging this two projects, i can rename the project back to "node_widget" and add the option to decide between this two display mods.

pkej’s picture

pkej commented

This looks amazing, from your screenshots. I will try to test this tomorrow.

Count this message simply as "subscribe"

:)

pkej’s picture

pkej commented

I created a few content types:

event_unary : field_person_1

event_binary : field_person_1 field_person_2

event_trinary : field_person_1 field_person_2 field_person_3

The settings form behaved very strangely with these three enabled.

customweb’s picture

customweb commented

I have setup a similar use case. I don't have any problems in the settings form. Can you please post a screenshot or more details description of the misbehavior? But I have found some other bugs:
The first bug is that you could not save the new order (weights) of items. The second bug is, that fields, which were in two different node types, will not be shown up. But at the moment i have no time to solve this problems. But i will post here if i have the solution(s).

pkej’s picture

pkej commented

Yeah, I was thinking of the screenshot, after I decided to go for another datamodel. I never liked that solution in the first place. I will recreate it and post a screenshot. Just have to enable your module again, as I went with a datamodel where I just use one field_actors and add a utility node which links the person to the actor and a field describing the role. This is more extensible.

The screen showt will appear shortly.

pkej’s picture

pkej commented

You know what? I can't seem to reproduce anything. I was pretty sure I had used autocomplete nodereference fields, but now I just get a message that the field type is unsupported. I have no idea what I did the first time around anymore.

Crom’s picture

Crom commented

I agree that this would be a superb addition to the module - to be able to see what has been created already. I tried your alternative module and can get it to create nodes etc but in the space where I expected to see the previously created nodes, all I get is "2rder" printed out.

I'm happy to do further testing if you have a more developed version available.

Cheers.
Crom