File manager upgrade/install past Revo 2.0.4

Can anyone tell me:

Were there changes in 2.0.5+ that alter the file system settings - specifically how TinyMCE behaves?

I had a 2.0.5 install that was working perfectly with Tiny MCE.

I did a separate 2.0.6 install and was having trouble with tinymce prepending image insertions from the file manager with /assets/components/tinymce as documented over yonder: http://modxcms.com/forums/index.php/topic,7806.0/prev_next,next.html#new

I upgraded both to 2.0.7 and now I have the problem in both places. In both cases, the TinyMCE plugin is the same version and so I assume it’s a core change.

I’m really struggling with this because now my clients need to be instructed on how to use the HTML view to do something simple like insert an image and it’s making me nuts.

It’s probably not a bug, (yes I did read the note about reporting bugs) but it’s a change that I don’t know how to track down.

Both of these sites are on the same infrastructure at a shared host, so there are no differences in the two from that standpoint

The first thing to check would be the rb_base_url and rb_base_dir System Settings.

Then, check the TinyMCE Default Properties and the System Events that TinyMCE is attached to (edit the plugin and look at the System Events and Properties tabs) in the old and new site (assuming that you still have the old, pre-upgrade site available somewhere) to see if any were changed or deleted in the upgrade.

[UPDATE]. It looks like someone has already checked and that’s a dead end.

http://modxcms.com/forums/index.php/topic,55391.msg342063.html#msg342063

I think some change in MODx requires an update to the TinyMCE code.

If I remember correctly, that was one of the issues I had on one of my sites a few months ago. Go into Package Manager and right click on TinyMCE. Select Remove Package and click "Force Package Removal." Then download and reinstall TinyMCE.

Thanks for the suggestions. I tried the force removal of TinyMCE, redownload, reinstall route.

My image insertions in tinymce did not have /assets in the path at all, so then I tried the ’rootrelative’ path option for tinymce, which produced the /assets/components/tinymce/assets problem. I then tried ’docrelative’ path option, which gives me assets/ (no forward slash), which is closer to what I want, though I really want all of my links to be root relative, just for safety’s sake.

I did have moderate success with setting filemanager_path to the full path /home/username/public_html/assets and then filemanager_path_relative to no, but it returned my paths with assets// instead of assets/

This particular configuration adventure has caused me headaches with every version of ModX I’ve used .. from evo 0.9.x on up. <sigh>

I will keep trying different combinations in the file management piece. I know there’s a bug filed regarding the documentation for that section of settings, and I have to agree that there are too many variables at play that seem (to the novice like me) to be either closely related or the same.

The way I see it, you need to support two scenarios: 1 - your assets are all in the web root, whether that’s declared relatively or absolutely, OR 2 - your assets are outside of the web root. There must be a way to optimize for one or the other.

Thanks again for the help. I will post results of experimentation when I have them.

This could be related: http://modxcms.com/forums/index.php/topic,59827.msg342106.html#msg342106