disable pathauto for one or more types of nodes

From Pathauto pattern recipes:

When the pattern for a node type is left blank, the default pattern will be used. But if the default pattern is also blank, Pathauto will be disabled for that node type.

Also, I believe that you did some investigation and found that Project module has a namespace collision with Pathauto. I believe (based on my investigation today) that it is actually a collision with the core path module.

If you believe it is more specifically with the Pathauto module could you please update #284300: Pathauto (or just core Path module) conflicts with project* with your thoughts?

Thanks.

Ok, good to know.
However, I am not 100% happy with it.
It means that you can not have a default pattern, and at the same time have it disabled for some node types.

Of course instead of the default pattern I could simply do some copy+paste.
The annoying part is when I create new node types: These will not have any alias by default, if I leave the default blank. So for every new type I have to go again to the pathauto page.

Maybe I would be less unhappy about this, if the pathauto pattern for a node type could be edited from the content type configuration page.

Thanks!
(I might produce a patch, we'll see)

Don't re-open long-closed issues. I am sure there is an issue in the queue somewhere for adding the pattern UI to the content type forms.

I really don't think there is a solution that involves a simple UI for this other than #273104: Using "progressive disclosure" for alias patterns.

Let's focus on that issue instead of this.

crosspost.

#5 (Dave Reid).
While this is an old issue, the problem description is still 100% valid. I don't see any benefit in opening a new one.

> adding the pattern UI to the content type forms.
> Using "progressive disclosure" for alias patterns.

On second thought, I no longer think any of these is a sufficient solution to the problem of explicitly and intentionally disabling pathauto for a specific type.
There has to be a difference between "explicitly disabled for this type" and "noone took the time to configure this yet, so we use the default".

I suggest that we introduce a <none> pattern for explicit disabling.

I'll repeat: Don't re-open long-closed support issues.

File a new feature request.

I totally don't see the point.
Whatever.
#1218952: Introduce a <none> pattern to explicitly disable pathauto (e.g. for specific node types)

Link to new issue.