This may be more of an issue for my specific site but i'll explain whats happening.

I am using OG to create projects, which then lists a workflow. Each workflow step is a node. I display the workflow steps with views.
Editable fields offers great usability to modify the workflow... except when i add a new node via the form that comes with edit views, it does not create the new node in the OG and therefor doesn't show up in the view.... so the form doesn't work in OG.. the workstep is created, yes, but does not ask if it should be associated with the og.

possible solution (from an drupal ignoramus): check if form is in an OG and if so use node/ognodeadd instead of node/add.

Comments

markfoodyburton’s picture

markfoodyburton commented

Complicated plan - but sounds like a nice idea.

Anyway, one thing Editablefields is SUPPOSED to do is pre-fill the form.

So - for instance, if you have your nodes with an element inside them which points back to the OG (either a node-reference, or maybe a taxonomy widget or some such), and then you set up an argument to the editable fields such that it only displays nodes associated with one OG (in this case), then, the form at the bottom SHOULD be pre-filled with the node-reference or taxonomy pre-filled in.

Maybe this would help?

somebodysysop’s picture

somebodysysop commented

As the maintainer of the OG User Roles module, I think it's important to note that "ognodeadd" is NOT a feature of the OG module. It's a forced feature of the OG User Roles module. Therefore, if a modification is made, it should NOT replace "node/add" for OG, but rather, *include* "ognodeadd".

Again, this is just a clarification note.

acidpotato’s picture

acidpotato commented
Status: Active » Closed (won't fix)

Closing legacy issue.