On the project page, the module name is "Menu path autocomplete", which is an accurately descriptive name for the module. But with this new Drupal 7 version, in mpac.info, the module name is "Multi path autocomplete", which is inconsistent, fails to convey its prior meaning, and causes confusion when the user searches his or her module list page, looking for the project name.

Comments

stborchert’s picture

stborchert
he/him
Primary language German
commented
Status: Active » Closed (won't fix)

With Drupal 7 the behavior of the module changed so it doesn't alter menu-fields only, but other field also. There the Drupal 7 version is named "Multi path autocomplete" instead of "Menu path autocomplete".
The old name is valid until Drupal 6 gets deprecated.

I've added a short description to the project page.

adamgerthel’s picture

adamgerthel commented

On a side note: Which other fields does it alter? I read that on the project page but couldn't find any more info on the subject

stborchert’s picture

stborchert
he/him
Primary language German
commented

If you have path.module installed you will get autocomplete values while adding a custom path to a node/page/whatever. Same for shortcuts: adding a shortcut will be easier with mpac because the field to enter the path transforms into an autocomplete textfield.

rooby’s picture

rooby commented

I would argue that menu path autocomplete is a better name.

It is still auto completing the path field when adding a menu item.

I think for most end users, multi path autocomplete is more confusing because they don't care about the differences between aliases and node stitle ar whatever.