Create a node type of Path Redirect so that users with the correct access permissions can create their own path redirects.

Comments

jjeff’s picture

One of the main focuses of this module is performance. Since the module needs to query the database on every page load during hook_init(), we want to be sure to keep the overhead as low as possible.

What is the use case for redirects-as-nodes? I suppose that hook_nodeapi() could just insert information into the current table and hook_init() would work the same way as it currently does. But if we're talking about a full node_load() at the beginning of every page call, that's a deal breaker. IMHO :-)

robloach’s picture

Yeah, I meant work around the Path Redirect system, so that when you create a node, it would add the path redirect to the table. When you delete the node, it would remove the path redirect. The use case is a TinyURL clone. Once I get the time, I'll put together a patch.

jjeff’s picture

Sure.

Maybe this could be handled as a separate module so that the feature could be turned on/off.

path_redirect_node.module?

We just want to make sure that we've still go the "old" interface for site admins. The node interface might be cumbersome for creating a lot of redirects.

Dunno... prove me wrong. :-)

robloach’s picture

You're never wrong, Jeff!

robloach’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.