Needs review
Project:
Path redirect
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Aug 2011 at 13:55 UTC
Updated:
3 Jan 2012 at 09:01 UTC
Jump to comment: Most recent file
Comments
Comment #1
okokokok commentedComment #2
David Hernández commentedHi!
I've updated the code provided by Kasper Souren to follow the Drupal Coding Standards and added command aliases. Also, I've added two new commands:
I've tested the part of Kasper Souren and was working fine. My part works to but I will leave it for review.
Regards,
David.
Comment #3
David Hernández commentedChanged to version 6.x-1.x-dev
Comment #4
tomotomo commentedWhat's the right way to get a .drush.inc file included?
Also, how about a "path-redirect-list" command? :)
Comment #5
David Hernández commentedHello,
#4, Drush loads the [module name].drush.inc file included in the folder of the module or inside a drush folder, so you don't have to worry about including or loading the new drush commands.
A path redirect list command will be easy to implement, but I'm not sure if it's a good idea as you may have a lot of redirects. Maybe adding some filters to the command will help, for example adding a limit to the query, filtering by redirect type... The module provides a function to load a list of redirects using different parameters (path_redirect_list_redirects), but maybe will need a bit of refactoring to work with drush.
I will try to have a better look in other moment.
Regards,
David.
Comment #6
tomotomo commentedI think that hundreds of entries is not a problem, but thousands of entries would generally need to be redirected to a file. If not listing output to stdout, then maybe "path-redirect-export" should be an option.