TinyMCE 4.0.4-rc2 fails to install under revolution

I did notice that when I uninstall tinyMCE, I get this:

Skipping modPluginEvent object (data object does not exist and cannot be removed): Array ( [pluginid] => 0 [event] => OnRichTextBrowserInit )
Skipping modPluginEvent object (data object does not exist and cannot be removed): Array ( [pluginid] => 0 [event] => OnRichTextEditorRegister )
Skipping modPluginEvent object (data object does not exist and cannot be removed): Array ( [pluginid] => 0 [event] => OnRichTextEditorInit )

Does that help?

I had to enable my error logs with my host. But then after I re-install tinyMCE, no files show up in the ’log’ directory.

I saw something in another tinyMCE thread about making sure it is registered to the right events. How do you register it to events?

Edit the plugin and select the System Events tab.

These events should be checked:

OnRichTextBrowserInit
OnRichTextEditorInit
OnRichTextEditorRegister

Thanks Bob -- I was hoping that was it but I went over there and they’re all checked already in my current non-appearing installation of tinyMCE. With: Property Set: 0 and Priority: 1.

There’s something in my apache error log now:

[Tue Feb 08 15:39:53 2011][crit] [client 173.15.79.161] (13)Permission denied: /data/9/1/18/114/1344440/user/1441327/htdocs/assets/.htaccess-ic pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://fruitflylife.com/manager/?a=30&id=19

I don’t know quite what I’m doing with Unix permissions, but I changed it to: r-- rw- rw- r--

Still no tinyMCE

That looks like a question for your host.

I’ve installed / deinstalled / installed a few times, and every time I deinstall, I get the OnRichTextBrowserInit, OnRichTextEditorInit, and OnRichTextEditorRegister errors saying that the object doesn’t exist - even though I know those are checked in the System Events. Why do you think that is? What are the implications of this?

Are the settings removed? If not, you could try removing all of them manually and reinstalling. The only thing I can think of (and I’m guessing wildly here) is that Package Manager knows them by their IDs and since they already exist, they can’t be installed. Then, when it’s time to uninstall them, the settings with the IDs PM is looking for don’t exist because they weren’t installed.

If a package isn’t successfully uninstalled, it can sometimes create a situation that’s hard to escape from.

A wild guess, but if there’s no contents that you need to save, try dropping the entire mysql database (delete it), uninstall and then reinstall.