make urls in content work within link syntax
Ticket
+issues
Right now you can't label a URL that's stored in a card (without using an HTML card).
- it's not prepending base_url, just "/wagn/", but the effect is the same.
- at the time the link is processed, the chunk processor has no idea what the value of the card is (it would cause a thousand problems to change that), so it's treating it as an "unknown card"
- i think we can change it so it just uses whatever value it gets back as the href, which is probably the most obvious route forward, but getting any smarter than that would be hard.
Worked around this with an html card on http://democracyinnovations.wagn.org/
--John Abbe.....Mon Feb 21 23:17:31 -0800 2011
fwiw, you don't have to use an html card -- you can write links directly into Basic through the HTML editor.
--Ethan McCutchen.....Tue Feb 22 10:19:50 -0800 2011
In this context, it causes problems:
http://democracyinnovations.wagn.org/wagn/By_Popular_Demand+summary_layout_broken (hover over "external website")
http://democracyinnovations.wagn.org/wagn/summary_layout_broken+*right+*content
vs.
http://democracyinnovations.wagn.org/wagn/By_Popular_Demand+summary_layout
http://democracyinnovations.wagn.org/wagn/summary_layout+*right+*content
--John Abbe.....Tue Feb 22 11:32:30 -0800 2011
oooh, interesting. ok, I see what's happening. TinyMCE is fucking with us. We keep making it so that it says something like href="
". Since the inclusion stuff means nothing to TinyMCE, it assumes we're putting in a relative url and it absolutizes it for us based on where we are. It makes some sense. If I were to link to "boots" from the current card, the absolute url would be "/wagn/boots". With the inclusions (processed server side), that was leading to "/wagn/http://blah...", which is a busted url.
I guess we could hunt around on tinyMCE to try to shut it off, but since we want to fix this in eight other ways, I'd probably just go with the HTML card for now.
--Ethan McCutchen.....Wed Feb 23 12:21:23 -0800 2011
Can you see any ways this could mess things up that we're not going to fix? (If so, want to ticket it now while the example is present and fresh in my mind.)
--John Abbe.....Wed Feb 23 13:23:07 -0800 2011
no. once we've built the link and inclusion editors we'll probably disallow a tags in tinymce altogether.
--Ethan McCutchen.....Wed Feb 23 14:01:52 -0800 2011
build link and inclusion editors
--John Abbe.....Wed Feb 23 21:50:21 -0800 2011
Is there more than one card for this issue? I thought it had the idea for a 'link' type in the comments. In any case, the issue is addresses with the new URI cardtype.
yeah, I'd say this is a duplicate of inclusions to define link targets. closing.