As per the discussion here:
#934920: Add to Custom (Form) destination module?

Would the maintainer be interested in collaborating to include the functionality of the node_destination module. I've had a look at your module, and what we could do, is include the destination path on the content type settings, but allow it to save, and be available under the custom_destination settings page too.

I'd happily close down my module, and contribute a patch to yours to make this so, if you like?

Comments

flevour’s picture

flevour commented

Hi Alex,
very interested in such a merge. I quickly gave a scan at the issue cited above and I think custom destination module would benefit from this integration. I had a couple of issues at least related to node add/edit/delete problems.

Approach @1
I'd suggest to integrate with the custom destination system settings form rather than form altering the content type settings page: I think it's better from a UX point of view if all the custom redirects are centralized in the same page.

I think you could add a set of fieldsets, one per content-type, below the current settings table. Each fieldset would give options to customize redirection for each node type.

Would you be able to provide a patch for this? Would the current module schema be enough for implementing this functionality?

Approach @2
Provide a simple UI/suggestion that shows the correct form ids for each define node type. A click would load the "add new custom destination" form with the "form id" field preset with the correct value.

What do you think?
Francesco

bryancasler’s picture

bryancasler commented

subscribe