Let's make path.module compatible with all entity types and convert hook_node_insert and hook_taxonomy_term_insert into hook_entity_insert.

Comments

jody lynn’s picture

jody lynn
she/her
Primary language English
commented

Functions that will need to be dealt with:

path_form_node_form_alter
path_form_taxonomy_form_alter
path_node_insert
path_taxonomy_insert
path_node_update
path_taxonomy_update
path_node_predelete
path_taxonomy_delete

jody lynn’s picture

jody lynn
she/her
Primary language English
commented

Thoughts about creating a new field type for 'Path'? This way it could be optionally included on any bundle (we could still have it added by default to nodes and taxonomies)

In that paradigm the pathauto settings could actually be configured as field settings, rather than all together on one config page.

Being able to use field-level permissions would be an advantage too.

jody lynn’s picture

jody lynn
she/her
Primary language English
commented

See also #1553358: Figure out a new implementation for url aliases and #1154180: Make URL aliases revisionable

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

I'm not willing to jump down the road of paths as fields yet. There's too much unknown and no good plan for it.

jody lynn’s picture

jody lynn
she/her
Primary language English
commented
Issue summary: View changes
Status: Active » Closed (duplicate)

Well, looks like you managed to demotivate me on helping out but they indeed did become fields in #1980822: Support any entity with path.module.