Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I am trying to change the url from "www.mysite.com/classified/6" to "www.mysite.com/for-sale/appliances". on the replacement pattern for "Pattern for all Classified Ads categories paths" i entered "[term:url]". it doesnt change anything on the url. What do I need to put in the replacement pattern to make the url a specific category?
Comment | File | Size | Author |
---|---|---|---|
#7 | 0001-WIP-on-Issue-1667618-Allow-automatic-aliasing-of-Cla.patch | 1.69 KB | fgm |
Comments
Comment #1
fgmSorry, your request is not very clear. It looks like you are using other modules in addition to Classified Ads, maybe pathauto (which version ?). Can you describe step by step what you are doing starting from a clean install, what you expect, and how what you get differs from what you expect ?
Comment #2
ebitiba CreditAttribution: ebitiba commentedsorry. i have looked at the other issues and haven't found this particular problem. yes, I am using pathauto ver.7.1.1. So when I click on one of my categories, I want the link to take me to the url of "mysite.com/services/legal." "Services" is a one of the terms of the categories taxonomy and "legal" is a term child of the services term. As it is, the url that it is linked to now is this: "mysite.com/classified/6." But I don't like that url, so I want to go into pathauto, into the alias pattern settings to change the urls for all category taxonomy term paths. What replacement patterns do I need to use to accomplish this?
Comment #3
fgmThe classified pages are not standard taxonomy term pages like the ones you can alias with pathauto on core: for the same term, they point to a different content. So if you want to alias them, you have to
Comment #4
fgmActually, this could be an interesting feature, although I don't have time for it now. Retagging accordingly.
Comment #5
ebitiba CreditAttribution: ebitiba commentedthanks for the response. closed
Comment #6
fgmClosed support issue, but active feature request for the future :-)
Comment #7
fgmI had this start of work in a local repo. Submitting here as a patch to avoid losing it. Definitely not finished.
Comment #8
fgmWith this module end of life approaching along with Drupal 7 EOL, this issue is now moot.