Problem/Motivation

We have a website where we didn't have the URL-alias enabled to be cleaned up. Then I read the issue #3570653: Really easy to forget to turn on Trash for URL aliases when enabling for content and enabled it as we also had the problem with -0 suffixes.
But when deleting a taxonomy term, all the aliases are not found anymore even tho they still exist.

Unchecking the URL alias support, brings back all aliases.

I did not check with other entity types. But feel like this can create the same issue?

Steps to reproduce

  • Have a site with content and the path alias set up.
  • Enable URL alias support.
  • Have a node with a url alias.
  • Enable pathauto for taxonomy terms.
  • Create a term and delete the term.
  • Check content overview and the url alias is not found anymore when you hover the title.
  • Disable URL alias support and recheck, the alias is back.

Proposed resolution

Make sure this doesn't happen.

Remaining tasks

See above.

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

tim-diels created an issue. See original summary.

tim-diels’s picture

tim-diels
He/Him
Primary language Dutch
Location Belgium 🇧🇪
commented
Issue summary: View changes
amateescu’s picture

amateescu commented
Status: Active » Postponed (maintainer needs more info)

I tried to reproduce the problem following the steps in the issue summary, but I couldn't.

After deleting the term, its path alias was correctly trashed, but on /admin/content the node was still showing its URL Alias when hovering over it, as well as when accessing it.

Are you on the latest version of the module? And are there some additional steps that should be taken into account?

tim-diels’s picture

tim-diels
He/Him
Primary language Dutch
Location Belgium 🇧🇪
commented

I did not test this on a brand new install but on a running project that I had little context of. Could be another module or something is triggering something extra here. I've linked to this issue in our company and when needed we'll test it more in depth. If possible to leave this open for a few months in the current status that would be nice. I'll try to review this myself after a couple of months and close when not anymore relevant.