To me, this sounds more like a Firewall on the server is blocking the request (to save the resource) and not like a problem with TinyMCE RTE.
So if you open the developer tools in the browser (and go to the “Network” tab) and then try to save the resource (with “from” in the content), what is the actual response (and the HTTP response status code) for the request that gets generated?
No. But it could be that something went wrong during the installation.
Maybe try to completely uninstall/remove the TinyMCE RTE plugin and then reinstall it.
What exact file isn’t found? Maybe it’s the one from a previous version?
If there is a problem with the JS file, then you shouldn’t be able to see the TinyMCE interface at all in the content area.
So these 3 TinyMCE plugins (“hr”, “download” and “spellchecker”) don’t exist on my system as well (with TinyMCE RTE 3.1.6-pl installed). But the code doesn’t try to load them, when I test it.
Maybe these plugins got added to the tinymcerte.plugins system setting (or to the external config file, if you use one → system setting tinymcerte.external_config). So maybe you have to remove these plugins from the setting or manually install them, to get rid of the errors.
All in all, I don’t think the reason for the problem (with the resource not saving) are these missing TinyMCE plugins.
When MODX “hangs” (after saving a resource), it’s usually that the request (with the resource form data to store) doesn’t return the expected JSON data. So either a PHP error occurs on the server, or a firewall just blocks the request. As the problem is quite random (the word “from” triggering it), it suspect a firewall interfering.
It’s unlikely, but possible, that this is a mod_security issue, though it would be a weird one. Maybe the mod_security rules got updated around the time you updated TinyMCE and someone mistyped one of them. I once saw a case where mod_security wouldn’t let a user save anything with the word “casino” in the text.
If you disable rich text or the plugin and the problem goes away, it’s definitely a TinyMCE problem and not mod_security.