-
☆ A M B ☆
- 24,524 Posts
No, TinyMCE cannot parse MODx tags. Images in .css files can be linked relative to the .css file. For example, if your images folder is in the same place as the .css file, image paths would look like
#something {background:url(images/someimage.png)top center no-repeat;}
If the .css file is in a "css" folder and the images are in an "images" folder in the same place, then it would look like
#something {background:url(../images/someimage.png)top center no-repeat;}
-
☆ A M B ☆
- 24,524 Posts
Ah, sorry. I misunderstood. I have done much the same, only using a chunk to provide the common part of the URL.
http://domain.com/where/images/are/
then my image link just looks like [[$imageURL]]image.jpg
That's a good idea! But the image would still show up as broken in TinyMCE.
Still, it'd be nice to get Tiny to render MODX tags (at least the assets_url system setting). But then again, that opens a can of worms with output modifiers. Those tags could just be ignored, though, seeing as parsing MODX tags is outside the scope of TinyMCE. I'll look into TinyMCE's callback functions and see if I can come up with something.
Hm, this is interesting subject. I'll think about this feature... I'm going to make CKEditor transport package...
-
☆ A M B ☆
- 24,524 Posts
I still much prefer the
elRTE editor and the related
elFinder file manager. A package for elRTE was made some time ago, but it was rather rudimentary and didn't take into account most of the relevant MODx settings. I've often thought it a pity that elFinder wasn't made into a package. Its image editing features are excellent, among other almost excessive features. Hook it up with Media Sources and it would be fantastic. Written with JQuery.
Consider how easy it would be to connect it to Media Sources:
https://github.com/Studio-42/elFinder/wiki/Multiple-Roots
[ed. note: sottwell last edited this post 13 years, 10 months ago.]