Match Redirect overrides Redirect

Yes, we are experiencing the same dilemma. We would like to have 1:1 redirect rules defined in the Redirect module to process first...and then any pattern based rules defined inside Match Redirect next. Anyone have any thoughts on how to modify the priority of execution?

Set the module weight in the "system" table for match_redirect to be "1" instead of 0. This makes sure its hooks run after the "redirect" module and should preserve your 1:1 redirects before matching patterns.

@nsciacca is correct. Whichever module runs first will win.

Match redirect should have an option to decide if match redirect or redirect runs first.

Hacking the DB is not a real option.

This would be a very nice feature to have

Just in case it saves someone two minutes...

Set the weight for match_redirect to 1:

UPDATE `system` SET `weight` = '1' WHERE `system`.`name` = 'match_redirect';

Set it back to 0:

UPDATE `system` SET `weight` = '0' WHERE `system`.`name` = 'match_redirect';

I think it would be sufficient to put the weight to 1 in the installation process.

It is just logical that redirect patterns are less important than individual redirects.

Fuction for match_redirect.install would be:

<?php
/**
 * Implements hook_enable()
 */
function match_redirect_enable() {
    db_update('system')
    ->fields(array('weight' => 1))
    ->condition('type', 'module')
    ->condition('name', 'match_redirect')
    ->execute();
}
?>

New fork which adds a setting on the Match Redirects page to first defer to any redirects set up via the redirect module.