If you enable project_legacy_paths, all sorts of things become broken:

For example:
project/autocomplete [works]
project/autocomplete/p [page not found]

Another example:
project/issues/update_project

I thought at first this was caused by views that live at project/% taking precedence, but that didn't solve it. Turning off project_legacy_paths did. So, we need to debug this and figure out what's going wrong in there causing it to hijack other paths it shouldn't be caring about.

Futhermore, we might need to change project_legacy_paths a lot more if we change the URLs more, e.g. #180316: fix project/mymodule URI insanity...

Comments

dww’s picture

Most of the trouble is caused by the fact that project_legacy_paths defines a menu item at project/%/%, which takes precedent over project/foo.

gábor hojtsy’s picture

Is this an important bug for the upgrade of drupal.org?

aclight’s picture

Issue tags: +6.x-1.0 blocker

This should be fixed before an official release.