This is thread follows the discussion on http://drupal.org/node/115970. I've submitting this as a new node as this 'feature request' is now changing direction and form.

I followed up on Tobias' comment about how this feature could be implemented. I took into consideration others' concerns about the direction of Global Direct, it's footprint on server resources and their suggestions. I've done research into path_redirect.module and taken into consideration many details of how Tobias' suggestion could work and possibly cause more problems.

I think that the 'tobias method' is the best solution to this. I suggest it would probably be best implemented as a new module; an alternative to Global Direct. I'm currently referring to it as as Global Redirect 2, GR2 or gr2.module.

I've documented how I think it would work best in Google Docs (http://docs.google.com/View?docID=dgj63cr3_32dnb492&revision=_latest) and in a workflow diagram (attached in PDF format).

I'd like to hear everyone's thoughts, opinions, advice, etc.. Is there a better way to do it? Have I missed anything? Where are it's weak points? How can they be strengthened?

Does anyone want to code it? I am keen to code it, although I'm learning php, programming, and drupal APIs, and might find this too challenging. Would someone mentor me if I code it?

CommentFileSizeAuthor
#1 GR2 workflow.odg_.txt12.37 KBBevan
GR2 workflow.pdf48.39 KBBevan

Comments

Bevan’s picture

Bevan commented
StatusFileSize
new GR2 workflow.odg_.txt12.37 KB

I've attached the OpenOffice.org draw file I made the workflow diagram with. Remove the .txt extension.

Questions I have and points about my planning and research so far (Some of these are marked in yellow in the document on google docs);

  • GR2 is run manually from config, or by cron. (Ideally it would run every time a row in url_aliases is added/updated/deleted -- is there a hook from path module to do this?)

    I couldn't find one

  • Would path_redirect table need changes to path (make unique) and redirect (make index) columns? If so, would this require changes to path_redirect.module? Would those changes be advantageous or disadvantageous to path_redirect.module?

    I think the answers are yes, yes and advantageous

  • The functions inside 'SetRedirect() would best be implemented as part of path_redirect module.

    Are they already implemented? (I found a comment on line 236 in path_redirect.admin.inc //check that there there are no redirect loops ), but no relating code. Is this an indication of plans for checks such as those in SetRedirect() on page two of GR2 workflow.pdf?

Bevan’s picture

Bevan commented
Status: Active » Closed (fixed)

I´m closing this as chx has got it covered for drupal 6: http://drupal.org/node/106094

nicholasthompson’s picture

nicholasthompson
Primary language English
commented
Status: Closed (fixed) » Closed (won't fix)

I understand that you're meant to leave issues as their status and then let the site close them automatically... I've seen someone got told off somewhere for setting one to closed ;-)

Bevan’s picture

Bevan commented

tks for the tip! :)