I renamed my module to pathfilter and just ported all your code over. http://drupal.org/project/pathfilter Thanks! Rob Roy Barreca Founder and COO Electronic Insight Corporation http://www.electronicinsight.com rob@electronicinsight.com Ray Zimmerman wrote:
On Aug 2, 2006, at 1:56 PM, Rob Barreca wrote:
I like this idea better than my urlaliasfilter.module, so maybe we could use this module instead of the one I have there (which just replaces any link to "node/5" or "admin/settings" with it's appropriate alias).
Ray, let me know when you get a CVS account and if you'd like to post a patch/combine efforts to urlaliasfilter.
I agree that we don't really need both modules. However, the reason I created it actually has nothing to do with URL aliasing, that was just a free bonus, so I'd prefer to use a name like "Drupal Path Filter" or "Internal Link Filter" or something. What I really needed was a way to enter internal links in content in a way that doesn't break when you move the site to a different path.
Other than that, I'm not really attached to being the owner of it. Would it make sense to set up a new project for my module and then put a note on the project page for URL Alias Filter saying that it's no longer supported and has been superceded by ... ?
IMO internal://node/5 is better so if someone wants to create a white label installation for a client who doesn't want anything labeled "Drupal"-specific.
I have no strong preference, but I had to pick one. Switching it to internal:// is obviously a trivial change. Any other opinions on this?
Ray