[wp-trac] Re: [WordPress Trac] #6737: TinyMCE converts relative
links incorrectly (adds wp-admin)
WordPress Trac
wp-trac at lists.automattic.com
Fri Jun 13 14:08:43 GMT 2008
#6737: TinyMCE converts relative links incorrectly (adds wp-admin)
-----------------------------------+----------------------------------------
Reporter: Otto42 | Owner: azaozz
Type: defect | Status: new
Priority: high | Milestone: 2.5.2
Component: TinyMCE | Version: 2.5
Severity: critical | Resolution:
Keywords: 2nd-opinion has-patch |
-----------------------------------+----------------------------------------
Comment (by Otto42):
Replying to [comment:8 lloydbudd]:
> Otto42, can you provide steps to reproduce the problem y'all are
discussing?
Sure. Create a non-root relative link in a post. Like
href="bobs/yer/uncle". TinyMCE will convert it into
href="http://example.com/blog/wp-admin/bobs/yer/uncle", when you really
wanted href="http://example.com/blog/bobs/yer/uncle".
This gets a lot of confused users on the support forums, who complain that
it used to work correctly. Admittedly, they should not be using relative
links in the first place, because with pretty permalinks those are
unreliable to begin with, however if TinyMCE is going to convert those to
full links, it should at least make a better guess about it than assuming
the files are in the wp-admin directory.
> Off hand it seems like a stretch to lump this into "correct invalidly
nested XHTML automatically". What is invalid about the XHTML?
I agree that it is a stretch. The XHTML is valid, but the resulting link
itself is not. But I don't think that it's worth adding another option.
The idea behind using that option is that you're basically giving
permission to "fix up" your invalid posts, and if you turn it off, then
most likely you want it to leave your (potentially broken) relative links
alone.
--
Ticket URL: <http://trac.wordpress.org/ticket/6737#comment:9>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list