I am starting this issue as a meta-issue in the hope of helping people that get lost in the vast number of issues related to i18n sites and their path aliasing. The second and third post of this issue (posts #1 & #2) will be this issue's summaries and I promise to keep them updated with latest news, patch releases, feedback received etc (the reason I am using post #1 & #2 is because I can edit them while this description I cannot). Post #1 is for D6 while post #2 is for D7. These posts will serve three purposes:

1. They will be a summary for developers/project maintainers so they have a clear(er) overview of the issues that need to be addressed first. ([off-topic]: this won't be required if/when either #44162: Relationships between issues: support for parent issue and related issues or #569552: Provide a mechanism for issue meta discussions get implemented or https://github.com/shomeya/pi_related is realized as a d.o project).

2. They will be a summary of issues that need to be followed by patch testers & reviewers. It will help get feedback for current available patches and how they get along when used together. This eventually will translate to faster advancement - I hope.

3. They will be a summary for end-users. In other words people seeking an actual solution for their real-life problem. It will be a hierarchical list of patches that need to be applied. A step-by-step guide to a workaround if you like (till we have a final solution and there is no need for patches).

The project this issue belongs to will be changing (between core/i18n/pathauto) depending on which issue is identified as the 'deepest' issue in this list. In other words which is the issue that currently blocks the rest from being implemented. If *a lot* of issues depend on another issue (either directly or because they depend on issues that depend on that final one in the long run), then this issue is qualified as such a 'deepest' issue. This issue can then be 'targeted' and developers' focus switched to it. It will be marked bold in the list.

On to it then...

Comments

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

D6 list (placeholder while I'm gathering and organizing info). Work in progress...

1st approach:

2nd approach:

Related issues:

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

D7 list (placeholder while I'm gathering and organizing info)

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

Status update: ...got a bit frustrated and it is only at the point where I started putting things together - before I even start testing things. This justifies the use of the word 'havoc' in the issue's title ;)

Because this seems really promising: #936222: Merge in pathauto_persist module functionality to prevent losing manual aliases with node_save() calls, I've asked a status update from the maintainers. Waiting on it...

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Issue tags: +pathauto

Adding pathauto tag so I can keep track of this.

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

...I am willing to continue my work on this (it is basically a documentation of what I try to do after each time I setup drupal), but no one cared or had the time to reply in my questions in #936222: Merge in pathauto_persist module functionality to prevent losing manual aliases with node_save() calls so far. I am basically interested to know if we're going the pathauto_persist path for sure or not.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.