pathauto not resolving patterns of group content:

If the pattern configuration is as shown in the image - created via group content: There is a special ID created and I can only suspect that this prevents it from resolving.

No check mark for automatic URL generation is created on the node edit itself.

If one creates a pattern using regular content it works fine - although the patterns for the group are inaccessible then.

(I set it to major because the bug breaks designs and hinders development.)

CommentFileSizeAuthor
2017-03-08_19h08_24.png4.61 KBmaxilein

Comments

maxilein created an issue. See original summary.

kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
commented
Priority: Major » Normal

Okay before this is bumped to major please provide the following:

  • In one paragraph, what are you expecting?
  • What isn't working about it?
  • Do you have steps to reproduce this problem?

Please keep in mind that GroupContent is the relationship between the Node and the Group, not the actual Node itself.

maxilein’s picture

maxilein commented

it is very hard to specify, since there is no documentation on the various routes/paths.
So I cannot be more specific than: I am confused by the multiple versions of paths.

Maybe this is the question: https://www.drupal.org/node/2821513#comment-11778120

You/we/I should perhaps look into allowing people to view the node at any of the following:

group/X/content/Y/entity Where Y is the GroupContent ID
group/X/node/Y Where Y is the Node ID

I'd prefer the first option as it aligns nicely with what we already have and would allow us to show the tabs for the node relationship in that group. I've not thought it through, so there may be some UX disaster I'm overlooking :)

The latter option would mean multiple node-serving plugins could end up fighting over the /node/Y path, so we may want to avoid that.

And this the desired scenario: https://www.drupal.org/node/2821513#comment-11778281

In a real-life scenario, we would never have group/X/content/Y/entity as the actual path, though. We *might* have something like /site-section/group-name/content-name though.

I presume what you are saying is that the node should be accessible using path 1. even though the user is not actually looking at it via that url?

Where is the specification for me to see the proper urls + their expected outcomes?
Then maybe I could be more specific.

For now I will add the case https://www.drupal.org/node/2821513 as a parent case. I think it is the closest of all to my real world scenario.
I will try to be more specific once I get back to that pathauto issue.

maxilein’s picture

maxilein commented
Parent issue: » #2821513: How can I create a block view "Content in this group"?