Reply to comment

not really

The distinction is that a single prefix l: will handle two types of substitutions - those starting with / are treated as web site paths, and without / are treated as Drupal paths. This is a distinction that is useful for those who install Drupal in a sub-directory.

Of course, that may be handled in InterWiki by creating two keywords, and mapping them differently, assuming it handles special characters correctly.

The key difference with many other link filter modules already available for Drupal and this linkfilter module is in that both Drupal and non-Drupal paths are handled appropriately. Non-Drupal paths with special characters, query strings, and local web non-drupal paths when Drupal is installed in a sub-directory cause other filters to run into problems, resulting in mangled URL links, which was the main reason for creating this filter. The Drupal l() and url() functions are the key issue - while they claim to handle non-Drupal links, they really don't. Comments in the Drupal forum suggest that it is best to stick to processing Drupal paths with l() and url() Drupal APIs.

Reply

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <b> <span> <pre> <hr>
  • Lines and paragraphs break automatically.
  • You may use [acidfree:xx] tags to display acidfree videos or images inline.
  • [l:URL text] input tags replaced with HTML links. URL may be Drupal internal path. [ Link Filter Tips ]

More information about formatting options