Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Ok, there is http://drupal.org/handbook/modules/pathauto to explain everything about Pathauto,
BUT user interface keep showing contradictory warnings.
So, the question keeps arising: to raw or not to raw?
Each time a new administrator/developer of the site review the configurations keeps asking the same question over and over again.
Why don't you remove the inapplicable warnings?
Or perhaps adding another explanation or even a link. Immediate link I mean, because every time somebody try to figure it out why it sounds so contradictory has to go and look for help (asking or searching online) without being strictly necessary in the particular case of Pathauto.
It is a recurrent question without an immediate answer.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | Screenshot.GIF | 21.5 KB | arhak |
Comments
Comment #1
gregglesThis question has been asked and answered several times. Is your hope to get some change made to the module or did you just not find those old discussions of the issue?
I added an entry on http://drupal.org/node/86994 to help provide some guidance so I'll mark this fixed.
Comment #2
arhak commentedBut I started saying that there is the question AND the answer, BUT the question continues coming up.
So, WHY the user interface can't reflect it?
Just a few more word explaining the apparent contradiction.
Mitigate the second warning would be IDEAL, but if it's too much trouble, WHY don't you make the first warning more explicit, actually nullifying the second one???
I still go for the "MINOR support request"
I understand there is a lot of work to do in much more important matters, that's why it its a minor issue.
If having it opened bothers you, ok, I give up. But, please, lets be honest, the request is not "fixed", but it "wont"
Comment #3
gregglesWell, so far you are just making a summary of a known problem. The interface is bad. Yes, I know.
What I need is concrete, non-duplicate suggestion on how to improve it. There are issues and feature requests in this queue and in the token queue to do a variety of things to improve the interface. If you have a specific way to improve it then I welcome more issues.
Rather than saying "X is confusing" please state "It would be less confusing if the module said 'Y'".
The best format for that is a patch to the existing code. Second best is a drawing or screenshot as a mockup of what you would prefer.
Comment #4
arhak commentedThe message above states: "Use -raw replacements ... to avoid problems ..." which matches the documentation.
But then, below several messages state: "WARNING -raw user input"
And any responsible administrator would ask him self if he knows what he is doing.
I might read the documentation several times, and once again I ask to myself why do you go for the first advise when the second one is more scary and in capitals?
Actually I don't ask that to myself, because I read the doc and toke note about it, but think on new administrators, or old administrators with memory flaws.
I suggest to remove the warnings, but if it's a Token matter, then make the first advice more explicit, stating that the others warning shouldn't be taken into account and why.
"The warnings below come from the Token module, there is absolutely no risk on selecting -raw data over here because Pathauto will transform the text into a slug. On the other hand, selecting the non-raw data will ..." ...what?
I hope I made my point, right?
Comment #5
arhak commentedSorry, it seems like I forgot the image...
here it is
Comment #6
gregglesYes, this is now a concrete suggestion for improvement. Thank you!
Transform the text into a group of boxes that move on the conveyer as one set? That doesn't seem very helpful to me.
How about that?
Comment #7
arhak commentedYes! that sounds much better.
And sounds very reasonable without making me go dive into the code or google.
I didn't know which module caused the warning (I thought maybe it was Token, but I was wrong)
And once read the documentation I stick more with the "do the opposite of what the warning says" than the HTML entities issue.
A slug? Well... I'm exposed:
http://www.symfony-project.org/forum/index.php/m/35893/
http://www.symfony-project.org/forum/index.php/mv/tree/10325/
slug: which for Pathauto is transliteration plus sign removal
Comment #8
seanrSubscribing.
Comment #9
beginner commentedThis is definitely a bug. The UI contradicts itself and warns about critical issues on both sides 8-|
Very scary.
#373168: UI: raw patterns: confusing/conflicting instructions!
Comment #10
dave reidBumping back to 6.x since -raw tokens are no more in 7.x.
Comment #11
mably commented