Posted by jasom on August 25, 2010 at 6:36pm
I'm using rules to create path alias after saving new user. Values are:
Existing path: user/[account:uid]/blog
New alias: [account:user-raw]/blog
Example
User name: Kotuha Matuha
Current result: http://127.0.0.1/Kotuha-Matuha/blog
Demanding result: http://127.0.0.1/kotuha-matuha/blog
Any idea? ;)
Comments
Why rules? Could you not do
Why rules?
Could you not do this with pathauto?
+1
There are settings in Path Auto that allows transforming URLs to lower-case.
Doing it with Rules is probably very possible, but I wouldn't recommend it when there is a tailored solution for this feature.
//Johan Falk, NodeOne, Sweden
pathauto blog bug
I'm familiar with all your suggestions, guys, but there was bug in pathauto during creating user blog alias https://drupal.org/node/447698. Possible solution was to use rules to generate path alias. But I installed pathauto 2.0 and advanced blog and It was working.
Definitely I thing, that creating lowercases alias using path auto, should be built in feature in rules.
completely agree with Jasom
I am trying to use rules for making URL aliases for my users and I have run into this problem as well. Basically I am giving my users the ability to make a custom URL, sitename.com/THEIRNAME by filling in a field in the node edit page. Rules then checks to see when this field changes and does three things:
1.) deletes all aliases currently pointing to the node id
2.) Creates the standard URL path for that node (same that path auto does)
3.) creates an additional URL path based on the users value they enter in the field for that node.
The reason for step 1and 2 is if the user changes this value it will clear all existing and recreate the standard and then their path.
To my disappointment I realized that the RULE module creates the path from the token fields I use with their actual case intact. The problem I have is that I use path alias with convert to lowercase, so now I have a problem as the links don't match as the original (or standard) should be all lowercase, but the path that rules generate is NOT. This is unacceptable and I'm a bit stuck on what to do at this point.
Any ideas?