Hello,
I am working on Drupal 6.6 and tried both Globalredirect 6.x 1.0 and the dev version and it is not seems to work.
I created a new node - mysite.com/node/1 and set an alias url for it - mysite.com/alias
i ran the update.php after downloading the module but when i manually enter the url - /node/1 i get the the page and the url is not redirecting to my aliased url.
I've been working with the global redirect a lot with my drupal 5 websites and this is not the way im familiar with, is it a bug or is it anything im doing wrong ?
Thanks,
Evyatar
Comments
Comment #1
Anonymous (not verified) commentedI thought i had this issue before but placed the blame elsewhere - I could have been wrong
For the node I created, I assigned an alias.
If the link to the node was from a menu I got the alias.
If I go to the view tab of the node it displays the alias.
If I link to the node from within another node, or my own block I get the nid
So effectively it appears that some links are not intercepted
Comment #2
nicholasthompsonTo address evyawebsites' issue... Have you tried the dev release? I cannot replicate this on 6.x-1.0. I'm going to be releasing 1.1 soon, so hopefully that might help.
@midkemia... Globalredirect doesn't 'intercept' any hyperlinks and re-render them correctly... It *should* notice any attempted access on a URL with an alias but isn't being accessed on the alias. So, in your later situation, if you wrote a hyperlink HTML code pointing at "/node/1" then the link should still point at /node/1, but when you click it you should be 301 redirected to the alias page. You may be experiencing the same problem as evyawebsites' issue with the no redirecting though. Please try 1.1 when it comes out.
Comment #3
Anonymous (not verified) commentedJust about to give 1.1 a try. But just noticed that the links appear to be OK. I have just moved my website from
old.mysite.com
to
www.mysite.com
so effectively it was in a sub-domain. I wonder if that was part of the issue ?
Comment #4
nicholasthompsonGlobalRedirect doesn't care what domain it's on...
Comment #5
nicholasthompsonSo are you saying its fixed now?
Comment #6
Anonymous (not verified) commentedBeen running the latest with no issues. So would say yes
Comment #7
nicholasthompsonAwesome. Thanks
Comment #8
evyawebsites commentedLooks Great!
Comment #10
chris.mccreery commentedI have the same issue. I have tried 1.1 and 1.2 and am running the site on a sub domain as well.