Well, I have upgraded both my 2.0.5 site, which did not have this problem and my 2.0.6 site, which did have this problem, to 2.0.7 and now both sites have this problem.
Argh.
For the one that was working, I have changed nothing except run the upgrade installer.
Does anyone have any advice?
I have experimented with various path configurations such
/assets/
assets/
assets
for the file manager directory
This would be a perfect time to use Git bisect if anyone is up for it.
I suspect this change in the MODx class:
1417 - /* create scriptProperties array from HTTP GPC vars */
1418 - if (!isset($_POST)) $_POST = array();
1419 - if (!isset($_GET)) $_GET = array();
1420 - $scriptProperties = array_merge($scriptProperties,$_GET,$_POST);
1421 - if (isset($_FILES) && !empty($_FILES)) {
1422 - $scriptProperties = array_merge($scriptProperties,$_FILES);
TinyMCE may be using $_GET or $_POST variables for the path and they’re no longer going into the $scriptProperties array.
Another user suggested completely uninstalling and removing (force removal) the TinyMCE package, then downloading and reinstalling it.
I am experiencing something similar on 2.0.7. I have File manager Path set to assets/content/
When I go to add an image in the content using the add image icon it finds the correct folder from the file manager path but removes /assets/content/ from the src address. So in the code is shows images/imagename.jpg instead of assets/content/images/imagename.jpg.
So I’m thinking there must be a setting somewhere that’s telling Tiny to strip that off.
Can anyone point me to where it is? I’ve attached my core file system settings.
Crawford
Crawford Paul
Bridgecourt Web Design - Proudly using ModX CMS
Serving Welland, Niagara, Ontario, Canada and the world!
http://www.bridgecourt.com
Ok this was solved by adding the same path to both File Manager Path and File Manager Url. Thanks to @rtripault for the help!!
Crawford Paul
Bridgecourt Web Design - Proudly using ModX CMS
Serving Welland, Niagara, Ontario, Canada and the world!
http://www.bridgecourt.com
Has anyone figured out a non-hairpulling fix for this.
I just did a new install of a Revo 2.0.8 site and I’m running into the same issue. All I want is for TinyMCE to ensure that I have rootrelative paths to images (/assets/images, not assets/images). I don’t want to mess with a <base> tag.
If I tell tinymce to be rootrelative, I get this /assets/components/tinymce prepender.
Argh.
Any hope anyone?
