Internal WYSIWYG Link Manger

Hi there,

I’ve noticed in Revo that there is no way to insert a link to an internal page by selecting from the context tree within TinyMCE - this seems to be available in Evo. Is this likely to be added shortly? If not, any tips on how it was integrated with Evo so that I may duplicate the method myself?

Cheers,

DM

EDIT: Typo

You should be able to just drag the node from the tree straight into the TinyMCE content pane.

I’m having real trouble trying to get this to work consistently however, particularly in Firefox - ironically IE is the most consistent but this just inserts [[~id]] - rather than creating an editable link. Is this intentional? I love that its using dynamic linking but would like to have greater control over the <a> tag attributes, is this possible?

I’m assuming you’re drag/dropping it straight into RTE-mode (not HTML-editing mode).

I’ll take a look at it for RC1; maybe we can get it to insert an <a> tag rather than just the HTML; TinyMCE is particularly difficult to work with when inserting HTML from JS.

That said, you can always use the "Toggle Richtext" button below the editor, and edit the tag directly.

P.S. My bad about editing the post - clicked Modify instead of Quote. Doh!

Yep straight in to RTE - if I hit the HTML button TinyMCE loads a new window and I can’t drag and drop from there. Incidently, if you turn off RTE mode then drag and drop works perfectly.

Just to clarrify - [[~1]] etc will drop a URI in at the moment when the content is parsed?

Whilst JS drag and drop is cool, maybe a simpler solution would be to create a "resource tree browser" for pages in the same way that there is one for files/images? Just an idea.

DM

Quote from: DangerMouse1981 at Jan 06, 2010, 10:32 AM

Just to clarrify - [[~1]] etc will drop a URI in at the moment when the content is parsed?

Yes.

Whilst JS drag and drop is cool, maybe a simpler solution would be to create a "resource tree browser" for pages in the same way that there is one for files/images? Just an idea.

That would have to be done in the TinyMCE Extra, not in MODx core - since the core supports any number of RTEs.

Quote from: splittingred at Jan 06, 2010, 11:32 AM

That would have to be done in the TinyMCE Extra, not in MODx core - since the core supports any number of RTEs.

Whilst I think its great that MODx will support multiple RTEs, I’m not sure I see the distinction between the way files and images are currently catered for i.e. with a "file manager" style hook and having something similar for internal links. If other RTEs can make use of the file manager dialogue thats been developed, are they not able to do the same with a resource tree?

I’m quite happy to try and mock something like this up, but I’m not familiar enough with MODx - where would you suggest I start looking to find the code for the Resource Tree widget that currently lives on the left handside of the manager?

DM

Quote from: DangerMouse1981 at Jan 06, 2010, 02:46 PM

Whilst I think its great that MODx will support multiple RTEs, I’m not sure I see the distinction between the way files and images are currently catered for i.e. with a "file manager" style hook and having something similar for internal links. If other RTEs can make use of the file manager dialogue thats been developed, are they not able to do the same with a resource tree?

In theory, yes, but different RTEs handle how those are loaded; some require anything to be in a popup window; others let you just specify a JS function. So, you have to provide a solution that would work in both scenarios (and not to mention fires in ExtJS). It gets pretty complex.

I’m quite happy to try and mock something like this up, but I’m not familiar enough with MODx - where would you suggest I start looking to find the code for the Resource Tree widget that currently lives on the left handside of the manager?

manager/assets/modext/widgets/resource/modx.tree.resource.simple.js

is the tree widget. (The non-simple one is specifically for the left-hand tree.) It has an xtype of ’modx-tree-resource-simple’.