Using Pathologic with TinyMCE, FCK, YUIEditor - The url "relative to root" , "/" problem

But having relative path is always preferable compared to absolute one.

No, not always. As you're seeing, when it comes to feeds, relative paths are useless since they're separated from your site - there's no way for a feed reader to know what a relative path is relative to. Pathologic always outputs absolute paths.

However Pathologic treats my img link as absolute urls due to "/" in effect of TinyMCE.

Arg. So many people are having this problem. I guess I underestimated the number of serious Drupal users who use it.

It looks like what I might have to do is make treatment of paths that start with / as absolute an optional feature, but enabled by default. That way TinyMCE users aren't tripped up by it so much.

Has anyone tried Pathologic with FCKEditor? Does it have the same problem?

Okay, so I started work on adding a check box to handle paths that began with a slash, and got pretty far along before I realized -- it's probably not even necessary…

TinyMCE users of the world, could you try this and let me know if it works? In the "Additional paths to be considered local" field, enter just a single slash. Or, if your Drupal installation is in a subdirectory like http://example.com/drupal/, enter "/drupal/" (with both the beginning and ending slashes). I bet that will be enough to kick Pathologic into action on paths that TinyMCE is creating.

I don't really support the D5 version, but if you download the dev release (in red on the module page), its features are somewhat comparable to the D6 version.

BINGO!!!

That works perfectly, and I'm using FCKeditor... converted the link perfectly...

Thanks for the solution Garrett, I stumbled upon it by chance just before installing Pathologic !

Could it be set as default ?

It would avoid new user of Pathologic to have that kind of trouble

(And I suppose that if you use Pathologic anyway, it's because you want all your links to be fully absolute one, so...)

I'll take it into consideration.

I personally always use "site relative absolute" paths so I don't have to worry about:

where the link ends up being in the path structure (as I would with true relative paths)

nor

the server.domain name of the server currently hosting the page

This preference has come from static html/css development experience, and I've only just started researching this issue in relation to Drupal. This research led me to this module and of course this issue - sorry if there's a more appropriate place I should post this.

Any relevant advice (not only regarding this module) would be appreciated.

From what I understand, your remote site is at something like domain.com/drupal/, right? If so, why do you have to remove the /drupal/ from your links?

Okay, I see. The web path doesn't have /drupal but the filepath does.

You're using Drupal 6, right? I'm not sure if the version 5 version of this module works correctly for this feature…

So for the paths that don't work, do they include the http://domain.com/ part at the beginning? If so, try entering http://domain.com/drupal/ in the "Additional paths to be considered local" field.

Yes, sorry for the slow reply, but you've found a way to feed Pathologic paths it can work with. Thanks for trying Pathologic!

Pathologic is solving the issue of development sites being in subdirectories (hacking your hosts file is a very difficult for many themers), and seems to be addressing the above issues quite nicely. Would a documentation update for these scenarios make sense?

Documentation update… You mean like this? I've actually had that in the documentation for a while.

When I initially set up the module, I skipped over that section as I wasn't dealing with WYSIWYG editors specifically. I've added a subsection explaining how the same configuration can be used when the site is moved into a subdirectory.