# Summary

The Pathauto module automatically generates URL/path aliases for various kinds of content (nodes, taxonomy terms, users) without requiring the user to manually specify the path alias. This allows you to have URL aliases like /category/my-node-title instead of /node/123. The aliases are based upon a "pattern" system that uses tokens which the administrator can change.

# Project URL

https://www.drupal.org/project/pathauto

# Where is the code?

https://www.drupal.org/project/pathauto.

# Estimated completion date

Unknown.

# Dependencies

#2578451: [token] Token

# Who's doing the port?

Berdir, EclipseGc, juampynr

# What help do they need?

Testing!

# D8 roadmap

No official documentation as of DrupalCon Barcelona.

# Background and reference information

No official documentation as of DrupalCon Barcelona.

Comments

Aimee Degnan created an issue. See original summary.

Kristen Pol’s picture

Issue summary: View changes
Kristen Pol’s picture

Issue summary: View changes
webchick’s picture

Title: Pathauto » [pathauto] Pathauto
webchick’s picture

Priority: Normal » Major
pedrorocha’s picture

What is the best way to give feedback: Drupal issues or Github issues? There are some duplicates.

webchick’s picture

Issue summary: View changes

Clarifying "Where is the code?"

penyaskito’s picture

Issue summary: View changes
webchick’s picture

Priority: Major » Critical
Issue summary: View changes

Promoting to critical, since it's in the top 10.

While I was at it, re-checked development status and made some small tweaks to the issue summary. Looks like D8 repo has commits as recently as Oct. 14, which is a big improvement over a month ago. However, MD systems's repo still has several commits since then, and there's also a patch which has yet to be committed in #2168193: Pathauto for Drupal 8, presumably making many of the same changes in an attempt to get the module usable in D8.

webchick’s picture

Issue summary: View changes

One more.

Berdir’s picture

Issue summary: View changes

The 8.x-1.x branch on d.o is irrelevant, there's nothing there (it doesn't even have a 8.x info.yml file). Our github repository is only relevant version of the module right now for 8.x.

We're working on getting it back to d.o but for now, use that. Updating the issue summary to reflect that.

mgifford’s picture

babipanghang’s picture

I've used the dev release recently, and it appears to work very well.
Maybe time to put a new dev release on drupal.org?

webchick’s picture

My understanding (which is like third-hand information, so ymmv) is that the blocker to getting the changes in the MD Systems Github repo rolled into the official D.o repo is completing the refactoring that Dave Reid asked for as part of the D8 port. This hit-list is located at https://hackpad.com/Pathauto-8.x-Plan-ob3OeHCs5t3.

EclipseGc has been doing work on the "pathauto pattern" architecture change at https://github.com/md-systems/pathauto/pull/91 (now in the pattern-config-entities branch of that repo). Here's a list of the outstanding todo items to get that merged into the master branch over there: https://docs.google.com/document/d/1d2IjCiOHjguJM9_DDUDpLUBScrI6AI5Vr_rT...

juampynr’s picture

We are very close to merge https://github.com/md-systems/pathauto/tree/pattern-config-entities-simp... on top of https://github.com/md-systems/pathauto/tree/8.x-1.x. Then we will start pushing forward to move the source code to Drupal.org.

Berdir’s picture

Issue summary: View changes

We've now merged the branch into the main 8.x-1.x version. Please update your sites and report any bugs you find. Make sure you are using the latest version of token 8.x-1.x-dev (alpha1 is not enough).

juampynr’s picture

Also, make sure that you use the latest version of Ctools 8.x-3.x-dev.

flocondetoile’s picture

Hello.
Where should we report any bugs ? On the d.o issue queue or on github ?
Thanks

juampynr’s picture

@flocondetoile, please report them at the GitHub repository. We will post a message here when the code moves back to Drupal.org.

RenewG’s picture

I'm using Drupal 8 and very interested in using pathauto module. I've downloaded it but when I install the module I get this error:

pathauto-8.x-1.x-dev.tar.gz does not contain any .info.yml files
Same for the zip file.

Any thoughts on this?
thanks

webchick’s picture

Yes. In the issue summary (as well as the comment just above yours), it states that development is currently happening on GitHub, not Drupal.org. If you acquire the code from there instead (URL in issue summary under "Where is the code?"), you'll most likely have better luck.

That said, to the Pathauto team, is there a reason not to sync code changes over to D.o as you go? That would help eliminate these kinds of support requests.

babipanghang’s picture

The combination of comment #15 and #16 already suggests the d.o releases should be usable.

juampynr’s picture

@babipanghang, really? All references there point to the GitHub repository. How do you get that impression after reading those two comments?

babipanghang’s picture

#15 suggests that after code merge, the code will be pushed to drupal.org. #16 tells me that code merge has happened.

Berdir’s picture

Sorry, I wasn't very clear there. with main 8.x-1.x branch, I meant the 8.x-1.x branch on github, as opposed to a feature branch where that stuff lived previously.

@webchick: Yeah, we're working on that. As you know, it's complicated. The 8.x-1.x isn't just an outdated version of the same thing, it's a completely different branch. We'll need to somehow merge that together. And nobody of us has access to do that. Except Dave.

Dave Reid’s picture

Status: Needs work » Needs review

From https://www.drupal.org/node/2168193#comment-10768060:

I've added Berdir as a provisional maintainer, deleted the existing 8.x-1.x branch, and pushed the Github 8.x-1.x branch back here. Berdir will create an alpha release today or tomorrow.

I will be doing a full review of the port on Friday to look for any major issues that would need to be addressed before a beta release can be made.

I'm going to go ahead and mark this as fixed as the 8.x-1.x branch should be usable now, and we should file issues for anything that remains.

raj45’s picture

I have tested the module (Pathauto 8.x-1.0-alpha1) and it works fine. The problem is that CTools (currently Chaos tool suite 8.x-3.0-alpha21) doesn't play well with blocks, I have created an issue here: https://www.drupal.org/node/2656894
EDIT: This issue has been fixed.

juampynr’s picture

Issue summary: View changes
henrystrick’s picture

A small suggestion from an inexperienced newcomer to Drupal. I believe that the new Drupal 8 alpha version not only depends on Token, but also on (part of) CTools being installed - at least on my development website it would not be enabled until I had added that. If this is true, it may be worth adding it on the "Project" page. There may be others than me who are attracted to install it, as it is such a handy module, and who would immediately do the "right thing" if CTools were also listed as a dependency or requirement. Thanks for all your efforts to write this! Anything that brings D8 more fully to full "production" capability is ever so welcome - and it depends on so much voluntary effort!!!

banacan’s picture

Agree with #29. I attempted to install the alpha version only to discover that it has a CTools dependency that is not listed on this page. Please update the dependency info for all listing of PathAuto.

akalata’s picture

Re: CTools dependency issue or any other bugs, this should be reported on Pathauto's project page, and not here. This post is only meant to provide information on the state of the port.

banacan’s picture

akalata. Thanks, I wasn't aware of that. Yes it should be on the PathAuto project page.

Dave Reid’s picture

FYI dependencies can be viewed on the release notes of the version you are downloading: https://www.drupal.org/node/2654596

juampynr’s picture

I made a list of potential beta blockers at #2653610: Review for beta-blocking issues.

raj45’s picture

Thanks @Dave Reid for adding the dependencies to the Pathauto project page.

Berdir’s picture

I've recently released a new version, alpha2 for Pathauto. It fixes a number of pretty serious bugs so please update asap. We're ready for a beta release soon I'd say, see #2653610: Review for beta-blocking issues.

I have to say I'm somewhat surprised to see multiple reports about the ctools dependency. To me, that seems like a triviality. Keep in mind that you're using an *alpha* version, most other alpha projects don't even bother with an upgrade path. We already do. But in a way, that's actually very positive.

The thing is, Pathauto 8.x-1.x has some major architectural differences to 7.x-1.x that also result in a very different UI. And we now have thousands of installations already and one single person opened a support question and asked about how to configure it. To me, that implies that users have no trouble picking up the new version and understand how it works. Despite the fact that we have almost zero documentation on that right now. #2657376: Document installation and usage is one issue that is working on documentation. And we need help there, especially from new users. Please report there if you think the help text works, what needs to be improved about it, what you were struggling with when using the module the first time.

Also, as #31 said. Please to not report bugs or other suggestions here. This is issue has almost 100 followers, any comment here sends out email notifications to dozens of people. Use this only for notifications that are relevant for everyone, use the issue queue for anything else.

seabear’s picture

pathauto is very good module, Can increase the support of the Machine name.
for example:[node:field_term:entity: Machine name]..
thanks!

Berdir’s picture

Status: Needs review » Reviewed & tested by the community

The release candidate is now out, hoping to release a stable version soon.

One problem there is that we have a dependency on ctools for two features, one would be trivial to copy over, just a single API method, but we also rely on entity bundle conditions. Would be nice to get that into core, so we can remove that. I don't really see that ctools will become stable any time soon.

tim.plunkett’s picture

Synchrotron’s picture

Not sure if my question is relevant for this thread.
I am evaluating the migration from D7 and Pathauto likewise pretty much everything except core modules is not listed in available migration paths for me. Am I right in the assumption that Pathauto does not have the migration path for now? If yes, when do you plan for it at least approximately?

Berdir’s picture

Pathauto only has configuration, it doesn't store actual aliases. That's in core and should be migrated.

I have no plans right now to migrate the pathauto configuration, re-creating the patterns should not be that complicated.

hass’s picture

Every module should migrate it's old settings whenever technically possible. Pathauto is no exception. Config data must not get lost and personally spoken I do not like to configure all complicated settings again of every module around. If data is not migrated we end up in a mess as aliases are changing without beeing noticed maybe several months until noticed. Nobody expects that all paths are getting incorrectly generated after a migration.

What is the problem with doing a migration?

Berdir’s picture

Status: Reviewed & tested by the community » Fixed

There is a stable version now.

Status: Fixed » Closed (fixed)

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