I noticed that instead of replacing the Term ID arguments in my views' URLs with their corresponding terms, View Alias is instead appending the terms to the end of the alias paths.
For instance, I have a view with the path "rants/%/popular" (where % is a Term ID argument). In the past, View Alias would create an alias of "rants/Music/popular", which corresponded to the URL "rants/22/popular". But now its instead creating an alias of "rants/%/popular/Music", which it assigns to the nonsensical URL "rants/%/popular/22".
Luckily my existing view aliases were not deleted, but the new views I've added all have malformed aliases like this, which is creating several broken links on my site.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | argument-validation-1.png | 189.47 KB | jstoller |
| #2 | argument-validation-2.png | 198.78 KB | jstoller |
| #2 | page-path.png | 126.7 KB | jstoller |
Comments
Comment #1
emackn commentedI can't reproduce this. Can you take some screen shots of your argument and path definitions and post them here. Maybe its a odd argument setting.
Comment #2
jstollerHere's an export of one of my affected views. Hopefully this will help.
For what it's worth, I do have a bit of an odd argument setting. First I set my argument validation to "Taxonomy term". Then I changed my argument validation to "PHP Code" and entered some code to adjust the view's title based on the argument. However, as you can see in the above code, the original taxonomy term validation settings remain in the database. This allows View Alias to pick up this view and correctly associate it with a taxonomy vocabulary. I've had these views set up this way for months now and it's worked just fine until now.
Comment #3
emackn commentedtry the 2.0 release