skeezicks

The workaround works fine! I appreciate the help! All is wonderful in blogland again!

Well, it works for me. Today anyway ??

BTW, the workaround holds up also if one uses TinyMCEAdvanced.

Thanks for the clarification!

To Otto42:

First of all, thanks for your help. Please forgive my frustration. It just seems that I constantly have to fuss and fidget around with my blog to get it to work right.

It’s like MSWord’s multi-level list functionality. No matter how much care one puts into formatting a multi-level list, it seems it is always boogered the next time the file is opened.

A few months back, and in another forum (bluehost, I believe) I got the idea that the inclusion of absolute urls in blogs opened doors to spambots, and that keeping urls relative would help. That’s my big hangup with absolute vs. relative urls. Maybe whoever wrote that advice was incorrect, I dunno.

Sometimes it seems that I spend much more time trying to prevent problems than I would spend just fixing the problems if and when they occur.

Circumambulent’s workaround about using the HTML editor worked for me (IIRC). Thanks for the help!!

Then I began using TinyMCEAdvanced (supposedly fixed for WP2.5).

Problem came back.

I went through Schamane’s workaround for TinyMCE and will see how that works out for me (Thanks, Schamane!)

I also checked whatever Tinymceadvanced files I could find for a similar callout but was not able to find any, so I guess it’s back to TinyMCE for awhile.

This is for Otto42:

You said:

Relative links are not recommended. They break whenever you change to using non-default permalink settings.

This is not a decision that WP or TinyMCE should make, and it telling folks “Don’t do that” doesn’t help with their frustration.

Well, I suppose this functionality can be considered either a feature or a bug, depending of course upon who is doing the considering.

It would be nice to get some kind of definitive feedback. If it is a feature and it its purpose were explained, people could utilize it or work around it – if it is a bug, people could still work around it but at least look forward to the possibility it will be fixed.

Looks like TinyMCEAdvanced has been updated to version 3.0 for compatibility with WP 2.5. Seems to work fine for some users while others are experiencing problems of various kinds.

For what it’s worth, I just checked with the tinymceadvanced site and version 3.0 is out. Feedback is mixed – some folks report no problems using 3.0 with WP2.5 and others report various problems. (April 5, 2008)

I wouldn’t say that it sucks until I understood why WP2.5 insists on using absolute urls. And I don’t.

I would say that like you, I prefer relative links over absolute, and that something that changes my typed input (i.e. the relative link text) to what it thinks is better (i.e. the absolute version) is not well-behaved.

I’m sure a large percent of WP users prefer relative links and they will eventually see this “problem” (feature??!) Maybe then the editor will be changed.

At least I hope so.

Let me restate the problem:

Relative linking as explained in

https://codex.www.ads-software.com/Linking_Posts_Pages_and_Categories

no longer works for me after upgrading to WP 2.5.

If my target document is <mysite>/uploads/mydoc.pdf

and I place this link to it on another page in mysite:

uploads/mydoc.pdf or <mysite>/uploads/mydoc.pdf

and then browse to it, I get a 404 Not Found error.

Furthermore, the link I just made is changed to:

<mysite>wp-admin/uploads/mydoc.pdf

and that is the reason for the 404 error.

Again, this behavior began after my upgrade to WP 2.5.

Is this a bug that should be reported or is there something on my system that is causing this behavior?

Otto42,

Yes, but I sure like TMCE Advanced. WP2.5’s new GUI is pretty nice too.

When I had this problem, I resolved it through my host’s email capabilities. It wasn’t a WP problem… (I use BlueHost, BTW).

Are you saying that TinyMCE works fine with WP2.5?

Have you tried TinyMCE Advanced with WP2.5 yet? I can’t get mine to work (version 2.2, that is) with WP2.5….

It needs to be updated to be fully compatible with WP2.5.