Hi,

I need to redirect a particular page to my front page.

I thought this module would do the job but nothing at all happens when I use it. No redirect, no error, nothing.

What information can I give you to bug-hunt? :-)

S

Comments

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

Did you add an actual redirection in the module's interface? What did you put in the from: and to: fields?

SMartin’s picture

Dave,

Thanks for the quick response... :-)

Yes, I did it through the interface. I just pasted the page url, after the domain, in the first box and "front" (in sharp brackets) in the second box.

So it reads 'my-page' in the first box and <front> in the second.

I just tried the 'Dev' version with the same result...

S

dave reid’s picture

Is your Drupal install in a sub-folder at all? Nothing happens when you go to http://example.com/my-page?

SMartin’s picture

Dave,

No sub-folders, just a vanilla install. When I go to www.mysite.co.uk/my-page I see the regular page.

The page in question is promoted to the front page. Could that be it? It's the *only* page which is promoted to the front page.

I don't want a visitor to view the page unless they are seeing it on the front page.

S

SMartin’s picture

Dave,

I just tried putting node/3 in the first box and <front> in the second and got the error:

The source path node/3 is a currently valid path. You cannot override existing paths. You can however, create URL aliases for them.

I don't really understand the error... I *want* to redirect a valid page to another page...Don't I?

This is using the dev version of the module.

S

dave reid’s picture

Ah, now we've gotten to the problem. You can't currently override existing paths.

SMartin’s picture

Dave,

Still not following...

How do I redirect /my-page to the front page? Not possible to do?

S

jguffey’s picture

:D I had the same Newb problem, we weren't using the module correctly.

In order to redirect, you have to use a path that Drupal isn't using yet. For example, 'node/1" is already a page, so use a page that doesn't exist yet like '/foo'. Make sure to test your path first to make sure it gets a 404 before attempting to redirect.

Anonymous’s picture

> In order to redirect, you have to use a path that ... doesn't exist yet like '/foo'.

Sorry, I don't get it. How can you redirect from a non-existent path?
Maybe I misunderstand what this module is meant for.
I thought it could redirect *from* some internal node to an external website (in my case) or some other internal node.
Like with meta-refresh in flat HTML.

I tried it:
/someinternalpage --> alias to http://outside.com
"You cannot add an existing alias as a redirect as it will not work. You must delete the alias first."

So I tried the raw node:
/node/3 --> http://outside.com
"The source path node/3 is a currently valid path. You cannot override existing paths. You can however, create URL aliases for them."

Please set me straight if I'm asking this module to do something it's not meant to do.

Anonymous’s picture

Subscribe #9.

Having the same problem: I want to redirect from an existing url (taxonomy term) to another existing url (child taxonomy term).

dave reid’s picture

@9/10: That's not currently supported. Aliases are for existing paths. Redirects are for non-existant paths (like when you migrate from a legacy CMS and it has funky URLs that don't map to Drupal URLs).

Anonymous’s picture

I solved my isue (#10) with module subpath_alias (and url_alter).
There is no setup needed in both modules.

In url aliases I now kan make a new alias: taxonomy/term/36 (parent term) -> taxonomy/term/42 (child term)

It need some more testing, with path redirect and path alias modules. The first impression is good.

------------

my webform edit page was not accesible caused by the two modules. I removed them.
It dit not solved my search for a solution described in #10.

Anonymous’s picture

I solved the ridirect with the modules rules en pathrule:

Event: User is going to see a page
If: check path
Do: Page redirect

dave reid’s picture

Status: Postponed (maintainer needs more info) » Fixed

Marking as fixed as per #11.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.