Using pathauto with content entity fails [#2866021]

HI
I've installed pathauto module and have it working fine with a custom entity type I created. However, when I try to apply a pathauto pattern to the event (or any) content type, no alias is created. I have tried bulk generate as well, it seems to find the content but it does not create an alias. Is there a better way to debug this? I swear I had this working before on an older open social install.

Comments

Comment #1

1 April 2017 at 18:14

tc33133 created an issue. See original summary.

Comment #2

bairlangga CreditAttribution: bairlangga commented 6 June 2017 at 05:25

Hi all, i +1 this. Actually it works and generates proper URL alias for SOME nodes, but then failed on others. Quite strange.

Comment #3

ribel

Ukrainian

🇺🇦Lviv

CreditAttribution: ribel as a volunteer and at Lemberg Solutions, Open Social, Drupal Ukraine Community for Open Social commented 11 June 2017 at 13:27

Component:	Other	» Front-End
Category:	Support request	» Bug report
Issue tags:		+CodeSprintUA

Comment #4

kedramon

Ukrainian

Uzhgorod

CreditAttribution: kedramon as a volunteer and at Lemberg Solutions, Drupal Ukraine Community for Open Social commented 11 June 2017 at 13:39

Issue tags:

+frontend

Hi guys, I just mage some investigation and looks like the issue is related to frontend bug.
form-element.html.twig template is overridden and some js related classes are removed, so if you click on Generate automatic URL alias it's became disabled and this option is not submitted with form.

Comment #5

peterpolman CreditAttribution: peterpolman at Open Social commented 18 July 2017 at 14:04

@kedramon Is this an issue in the socialbase or socialblue theme or an issue in one of the core themes? I'm currently having issues to reproduce this from a front-end perspective. I do see the problem tc33133 reports, but can't see why this should be a front-end issue...

This is what I discovered:
- Setting the pattern /event/[node:title] for event nodes succefull.
- Bulk generating the new aliasses for all existing conten succesfullt
- New content is referred to correctly in stream (referring to the new alias)
- Old content is maintaining it's old alias (node/*) which is a problem.

This all sounds very back-endy to me:P We don't officially support the pathauto module and probably have to do some custom development for it to integrate with the social profile. Changing the component to code and feature request for now.