Problem/Motivation

In #2615922-13: Configure path auto for organizations, we identified that there were a few problems:

  1. An alias isn't always generated (e.g.: for https://www.drupal.org/node/2446211 )
  2. The form was not validating because of the not set "Supporting Technologies listing" field (may be related to above) — (e.g.: for https://www.drupal.org/node/2178413 )
  3. Aliases can contain apostrophes (e.g.: https://www.drupal.org/brady's-meat-deli )

Proposed resolution

  1. Figure out why https://www.drupal.org/node/2446211 didn't get an alias initially.
  2. Figure out why the the form was not validating because "Supporting Technologies listing" field was not set (maybe make it optional? or conditionally optional?)The supporting technologies listing field is a problem for org profiles created between the time the field was added and when a default was added to that field. There should not be many like that, but we need to run a query to see how extensive this problem is.
  3. Filter out apostrophes in the Pathauto settingsApostrophes removed.

Remaining tasks

TBD

User interface changes

TBD

API changes

TBD

Data model changes

TBD

Comments

mparker17 created an issue. See original summary.

joshuami’s picture

joshuami
he/him
Primary language English
Location Portland, OR
CreditAttribution: joshuami at Drupal Association commented
Issue summary: View changes

I'm updating this issue summary. We did some research and there is no need for the /o/ alias path for mitigating security concerns. For Google to respect the verification file, both the pattern would need to be matched and the content of the field would need to exactly match what Google expects. Since an organization node has a lot of other content, the verification would fail.

The rest of the items are great follow ups. We'll tackle them in our next sprint (starts on January 18th).

jan kellermann’s picture

jan kellermann CreditAttribution: jan kellermann at werk21 commented

We also didn't get an alias for https://www.drupal.org/node/2557985 after saving the node.
And we dont have a field called "Supporting Technologies listing".

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

I updated your organization page to use pathauto.

The “Supporting Technologies listing” field is access controlled for only the Marketplace webmasters.

dddave’s picture

dddave CreditAttribution: dddave commented

Do we want a . in our url pattern? https://www.drupal.org/acreative.

joshuami’s picture

joshuami
he/him
Primary language English
Location Portland, OR
CreditAttribution: joshuami at Drupal Association commented

That's interesting. I could have sworn we were stripping periods from the alias pattern. I would say we don't want a trailing period, but I don't have a strong preference for whether we allow periods in the middle of an organization name. It would be easiest to just remove that from the pattern as well to avoid confusion.

joshuami’s picture

joshuami
he/him
Primary language English
Location Portland, OR
CreditAttribution: joshuami at Drupal Association commented
Issue summary: View changes
Status: Active » Needs work

Periods have been removed from the path punctuation settings. That should clear up quite a few broken links in the future.

This still need a little research into a couple of the remaining bugs.

joshuami’s picture

joshuami
he/him
Primary language English
Location Portland, OR
CreditAttribution: joshuami at Drupal Association commented
fenstrat’s picture

fenstrat
he/him
Primary language English
Location Australia
CreditAttribution: fenstrat commented

Also didn't get an alias for https://www.drupal.org/node/2451797 (and not sure where to ask for a fix). Any chance its pathauto setting could be manually turned on?

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

fenstrat - I updated the alias on your page.