CMSContent - FCKEditor Plugin Allows you to insert links to MODX Pages :)

Just as a side note- Joomla does have this option. There is a TinyMCE port called JCE. JCE is a really nice system with lots of plugins. One of them is an advanced link manager- where you can choose the article. It’s a nice feature- thanks for this..

If you want to see the JCE port of TinyMCE, it is here: http://www.cellardoor.za.net/. A very nice port- the only WYSIWYG I used for Joomla.

Chuck

Nice add-on.

One small issue. If you your page title has an apostrophe in it, this will cause a javascript error, resulting in no docs being available to link to. I solved this by inserting a backslash before the apostrophe using the str_replace() function on lines 195 and 202 in the "fck_cmscontent.php" file.

Not sure if this is the most elegant way to solve the problem but it worked for me

I must admit that I’ve hardly ever come across links with apostrophes in their titles so don’t know how useful this really is. But someone might appreciate it.

Another problem which has been reported to me is that it doesnt build a menu if none of your site documents have a parent folder / document which is 0.

As the plugin I created creates a default root node

d.add(0,-1,’Modx Pages’);

To be honest I didn’t think it would be possible not to have a parent node of 0? Does anyone else have a NOT have a parent folder / document of 0 on their site and could this be a common occurrence?

Thanks

I suppose it could seem that way if you are working on a bunch of documents under an unpublished folder? All sites have a 0, it’s the "root", and has your site_name. I don’t believe that there actually is a document with an ID of 0, though.

I have installed modx in a folder on my website not in root. When I try to use the create link title feature. It will link to the root of my site and not where I have my actual modx installation. The usual llinking feature works ok.

Cool, was thinking about this one earlier I reckon i should check the modx database for the site url and pre add it to the link.

Will do this when I get home this evening and upload an updated version

Thanks for the input everyone.

Just to let you all know I have uploaded a new zip file to the start of this thread which fixes the following:

Fixes:

1. Added rb_base_url to start of the link as some users don’t have modx installed off the root of thier site
2. Removed the path setting at the top so just change your path in the include line.
3. Removed the unused include.php while code.

I’ve just been thinking about the latest change which pre adds the site url before the link, this might lead to problems for example if a dev modx site got moved from production to a live environment for example lets say my production is: http://dev.spcs.eu I think create internal site links which resulted in this

<a href="http://dev.spcs.eu/pagename.html">test link</a>

Now when I move out of the dev environment I;m going to be stuck with loads of pages with bad links as my live site is http://www.spcs.eu/

Any suggestions on the best way to tackle this problem?>

Thanks

This issue has been hit before at other points in MODx. The main solution appears to be to give the user the choice of whether to do this or not and to warn them that if they do use absolute paths they would need changing if they ever moved the site.

If you look at Administration > System Configuration > Miscellaneous Settings in the Manager, you’ll see
"Rewrite image paths?" I’m not absolutely sure what this actually does.

More importantly, if you have TinyMCE installed, then in the section Interface & editor settings you’ll see that has a setting for Path Options. There are three options, Document Relative, Root Relative and Full Path. The help text says:

This setting tells TinyMCE how to handle the paths for internal links. Note: Document relative links may not work right with friendly alias paths. Also, links might need to be changed if you move your site to a different domain or subdirectory if links are root relative or full path.

It would thus make sense to have the same option available to FCKEditor.

I believe that you should change your files so that there is a config option in the include file (that defaults to the previous relative method as it is safest). Then if Bravado integrates this into the FCKEditor plugin/core he can add the option there so that it matches TinyMCE.

Or, you could simply append [(site_url)] to the beginning of links as this changes with the location of the install.