Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.A new feature is being worked on for Strongarm (#870040: Provide hook to allow modules to define what variables they own) which would help manage variable exporting, it'd be great if Auto_NodeTitle could support it.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | pathauto-n871132-v6x1x-2.patch | 3.37 KB | damienmckenna |
| #3 | pathauto-n871132-v6x2x-2.patch | 3.02 KB | damienmckenna |
| #1 | pathauto-n871132-v6x1x.patch | 2.96 KB | damienmckenna |
| #1 | pathauto-n871132-v6x2x.patch | 2.87 KB | damienmckenna |
Comments
Comment #1
damienmckennaHere are patches for v6.x-1.x and v6.x-2.x. FYI for the v6.x-2.x patch I did not verify that all of the variables from v6.x-1.x are still used, will do so shortly.
Comment #2
damienmckennaBoth patches are missing several variables for core Drupal functionality, updated patches on the way.
Comment #3
damienmckennaUpdated patches that cover all of the variables created via the settings pages when all core modules are enabled.
Comment #4
gregglesNitpick: The module name is Pathauto, not PathAuto.
Bigger question: I'm in favor of this idea, but not sure I see the value of this hook. Ideally I'd prefer to use a variable pattern like path_redirect and comment_notify where the name of the variable AND its default value is returned by this function. Any reason that strongarm doesn't work like that? It makes this function much more useful in general and makes people more likely to use it. Is there time to change it?
Comment #5
damienmckennaCare to raise the point in #870040: Provide hook to allow modules to define what variables they own (so we can centralize the discussion)?
Comment #6
dave reidThe patch in features seems to have been dropped. Going to close this out too.