First I just want to say, awesome module like it a lot!
One thing that I would like to improve is to make the paths url friendly when using replacement patterns.
For instance, if I have a article called "Great article" and I use that title as path is gonna link to "http://mysite.com/Great article" but is should be "http://mysite.com/great-article"
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | friendly-paths-1866558-1.patch | 2.65 KB | StoraH |
| #1 | panels_breadcrumbs.png | 87.58 KB | StoraH |
Comments
Comment #1
StoraH commentedHere's a patch for it :)
Comment #2
devuo commentedHello StoraH, the problem is that sometimes you might want the text capitalized and with spaces. Say you want to pass a parameter in the URL that will fill the title of a node, how would you do that if we do it like that? Assuming all replacement patterns are to be lower case and dashed is a mistake. The only alternative I'm seeing is if we use some additional pattern wrapping the replacement pattern to be lower-cased and dashed, like {[node:title]}.
Comment #3
StoraH commentedHi devuo, I see your point. But the patch is not forcing anything you can still use plain replacements, it's just simply adding two options, two checkboxes. One for lowercases and one for replacing spaces.
Comment #4
philyWhy not run the breadcrumb path through Pathauto and Transliterate?
Field Field Path module does this for either path or file name and its very convenient.
Comment #5
IreneV commentedShould not be implemented to module - just specific case could be avoided with other tools )
Comment #6
IreneV commented