Release: Redirects

[apeisa]

benbyf, see from here: https://processwire.com/talk/topic/148-release-redirects/?p=78798

[renobird]

I have an as yet undocumented update to this module that will do that.

Here is the most current version

ProcessRedirects.zip

I've been using this version on a high traffic site for over a month, and it's solid.

You may have to use 2 rules (depending on what you want)

The * at the end is a wildcard.

[benbyf]

Thats cool, but is there a set up to send /old-page/* to /new-page/* not just the root folder. I.e. all pages under /blog/* to /news/*

[Mike Rockett]

@benbyf - I don't think Tom did it that way. I do hope to get my module (which will fully support such redirects) up soon - still got a bit to do on it...

Sorry for the delay guys... I'm sure that there are a few people who need it. Will get to it as soon as I have the time.

[renobird]

is there a set up to send /old-page/* to /new-page/*

Not currently, but it shouldn't be too difficult to add while Mike Anthony gets his version complete. I'm looking forward to his version myself—so long as I can specify my alt domain. *wink*

[Ivan Gretsky]

Finally got a chance to use this module. Thank you apeisa! I installed it on current stable (2.5.3) and tested probably every function. I can state it is compatible with PW 2.5. If someone else could confirm that, maybe it can be stated on module page, so people would not be scared off by compatibility problems.

@Mike Anthony: Patiently waiting for your new module. I was impressed by your Bolt redirect module satated functionality! When finished, your PW module should get almoast all use cases covered.

[Mike Rockett]

@Ivan: Glad you like that one. I'm going to try and work on the new module a little now. I have a feeling it needs to be re-written, but I'll decide shortly.

(Not a Christmas-person, so any form of work is not a problem - does feel good to have no obligations, however.)

[Mike Rockett]

Don't want to open up a new thread about this small issue: Why is that if I define an admin page in the module's info, it won't delete at uninstall-time?

[apeisa]

Finally got a chance to use this module. Thank you apeisa! I installed it on current stable (2.5.3) and tested probably every function. I can state it is compatible with PW 2.5. If someone else could confirm that, maybe it can be stated on module page, so people would not be scared off by compatibility problems.

I updated the module page, thanks for the heads up Ivan!

[Nico Knoll]

@mike: Not sure where you defined it but normally you have to create and delete admin pages manually in the ___install() and ___uninstall() functions (Example: https://github.com/NicoKnoll/ProcessTemplateEditor/blob/master/ProcessTemplateEditor.module#L264-L311)

Edit: maybe I missed an Ryan-update and there is an easier way now.

[Mike Rockett]

@Nico - there is an easier way. One can now define the pages in the info, which can also be in a JSON file:

"page": {
    "name": "the-name",
    "parent": "setup",
    "title": "The Title"
},

 

So I know I can manually uninstall the page - but it should do this automatically. Haven't checked out the source though...

[Mike Rockett]

Ah! My bad - didn't move parent::___uninstall() over when I started again... lol

[Nico Knoll]

This only works for Process-Modules, doesn't it?

[apeisa]

Nico, sure - no reason to work with others. Process modules are what admin pages use.

[Nico Knoll]

Just add parent::init() to the init function. Then you don't need parent::install() and parent::uninstall() (I started updating my process modules with this new technique )

[Mike Rockett]

Nico, I really like that idea. Crazy simple.

But wait, before I do that - will it interfere with a conditional install? In other words, I'm checking to see if the original redirects module is installed before installing my module...

Edit: However, I've always used parent::init()... Didn't do the [un]install automagically...

[Nico Knoll]

Well for me it works with just having parent::init() ... (I updated ProcessLogs today for example: https://github.com/NicoKnoll/ProcessLogs)

[Mike Rockett]

I'll investigate further to see what may be happening on this end... (There's a slight chance I may be deluded - but on the chance that I'm not, I'll double check what happened.)

[kongondo]

I think the feature Nico is talking about was added in the dev branch a while back? IIRC...can't find a link atm... . To be clear parent::init() has been there for a while...what I am referring to is the 'uninstall' feature Nico is talking about...if memory serves me right!

Edited December 27, 2014 by kongondo

[Mike Rockett]

I'm on the latest dev, but, for some reason, it didn't auto-[un]install. Here's the code of the init method in Process.php:

public function init() { 
	$class = $this->className();
	$info = $this->wire('modules')->getModuleInfo($this, array('verbose' => false)); 
	$version = (int) isset($info['version']) ? $info['version'] : 0;
	if(is_file($this->config->paths->$class . "$class.css")) $this->config->styles->add($this->config->urls->$class . "$class.css?v=$version"); 
	if(is_file($this->config->paths->$class . "$class.js")) $this->config->scripts->add($this->config->urls->$class . "$class.js?v=$version"); 
}

[Mike Rockett]

Quick one: I'm not fully sure how the hooks system works. Will there be conflicts with my module and the original if both are installed, and calling the same hook? I understand there's a priority attribute - does that mean they'll work comfortably together?

[Mike Rockett]

So I'm hacking away at the new module right now, and I need to ask if anyone needs the following features:

1. PassThroughs - keep the old url and serve content at a new url. I don't think anyone will need this, but I'd like to know if anyone does, and how important it is to them.

2. The ability to set HTTP Status Codes (301, 302, 307) on a per-redirect basis. I guess this is handy for temporary stuff, like for short URLs...

3. The ability to set a start and end date for the redirection

I guess that 2 and 3 go with one another. In other words, if I set a start and end date, the redirect should be 302. Am I right? If so, would number two be redundant?

Update - I'm not doing feature 1. Features 2 and 3 are being done, but the outcome of feature 2 will be determined what is set for feature 3.

[Mike Rockett]

(Removed)

Edited January 23, 2015 by Mike Anthony

[Mike Rockett]

Tom: Regarding Legacy Domains, do you think it may come in handy if we were to add per-redirect exceptions? Perhaps you want to keep a URL on your legacy domain, but if its accessed on the new site, you don't want to redirect to legacy. Yes?

[Mike Rockett]

(removed)