I installed TinyMCE 3 and corrected the extra , indicated in the previous post.
Now the editor shows up just fine. However when I open up my resource browser (which works as well) it still shows an error in my statusbar.
Furthermore when you use TV’s with an option to insert an image it seems to use the browser that is included in the manager folder instead of the resource browser included with the TinyMCE 3 package. This results in not showing the files in the assets/images folder.
P.s. The package on Modx’s frontpage is still not upgraded...
Could we have an option for "inlinepopups" plugin?
MY editors are always confused when those pesky insert picture dialogs drop under browser window...
There seems to be an error in Firefox when choosing a file upload (not an image) -- the error is in this code in /mcpuk/browser.html:
if (win.ImageDialog.getImageData) {
win.ImageDialog.getImageData();
}
win.ImageDialog.showPreviewImage(url);
which needs surrounding in a check to see if we are browsing for an image:
if (typeof(win.ImageDialog) != 'undefined') {
if (win.ImageDialog.getImageData) {
win.ImageDialog.getImageData();
}
win.ImageDialog.showPreviewImage(url);
}
Unless there is a better way of doing this?
Author:
ManagerManager plugin - customise your ModX manager interface
Rckt - web development, Sheffield, UK
Good call, ncrossland! I’ll look into this today. Your solution may just be the ticket! Thx!
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Quote from: Eol at Feb 28, 2008, 02:21 PM
Could we have an option for "inlinepopups" plugin?
MY editors are always confused when those pesky insert picture dialogs drop under browser window...
You could easily add the inlinepopups plugin to the custom settings. However, Moxiecode says that it’s experimental and may not work right. My experimentation with it shows that it doesn’t work all that well right now due to the fact that the content area is within a frame. I think once we get 0.9.7 out, using stuff like this is going to be a whole lot easier.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
Quote from: bertcatsburg at Jan 27, 2008, 03:50 PM
Hello,
To come back on my previous problem reported by me and others.
It seems that I rely on the MODX Search too much and therefore could not
find the links mentioned below. The standard Google search engine pointed to the right direction.
http://wiki.modxcms.com/index.php/How_to_prevent_TinyMCE_from_prefixing_relative_URLs_with_/manager/
http://wiki.modxcms.com/index.php/Fixing_Relative_URLs_in_MODx_and_TinyMCE
I implemented these solutions and problem seems to be solved.
Tomorrow I will let my team test if other new problems occur due to implementing this solution.
The first problem manifests itself also in MODX 0.9.6.1. and TinyMCE 2.1.3.
Regards,
Bert Catsburg
Bert, I think I might have found a solution. The problem is that TinyMCE will try to convert a URL if it’s set to do root relative links. As such, it tries to do it based on the current URL...which is inside the manager. It’s a limitation within TinyMCE itself. To get around this, I’m adding in a convert_urls parameter and setting it to false any time the configuration is set for root relative links. That should do the trick.
Jeff Whitfield
"I like my coffee hot and strong, like I like my women, hot and strong... with a spoon in them."
There doesn’t seem to be a way to give users a specific CSS file ("Path to CSS file") for TinyMCE. You can do just about everything else with TinyMCE, but not that. It would be a useful feature to have because I have several users who are allowed to edit only a section of the site, and that section has a different style sheet and different template than the default style sheet/template. Is there a way to get around this limitation, so that I can specify a different CSS file for a specific user?
Greetings folks,
I’m noticing a possible problem in v3.0 where when editing a chunk the editor will not load. Anyone else seeing this behavior? (Note: After quick testing, it seems this only affects Firefox and Safari, Mac and PC--IE and Opera display the editor fine.)
Jim
------
Server: *nix, ModX Evo 1.0.4, Apache 2.x, PHP 5.x, Mysql 5.x.
Does an upgrade from 3.0 to 3.0.3 require running the install script, or can the files just be overwritten?
Author:
ManagerManager plugin - customise your ModX manager interface
Rckt - web development, Sheffield, UK
ncrossland - not totally sure, but I would do the standard install routine, that way if you find an issue you can rule out any installation differences. It also allows you to switch back to an earlier version very easily by disabling and enabling the different plugin versions.
That being said I do have a problem with 3.0.3. I’m not sure if anyone else has this issue yet, early days I guess.
When browsing for an image (or file to link to) from within 3.0.3 I get a javascript error on the FCKeditor page.
Line: 172
Char: 3
Error: Unspecified error
Code: 0
The files or images are then not displayed for selection. I had version 3.0 working ok. I’ve tried it on a couple of different MODx installations and using Firefox and IE7, all give the same problem. I’ve also tried changing the "Path Options" to see if it made a difference, but no.
