No TinyMCE site wide - front end or back end.

I upgraded a site from 7.1.6 to 7.3 and there is no TinyMCE editor anywhere on the site, front end or back end.  Nothing is being reported in the error console.  The TinyMCE JS init is not being loaded to any pages where there is a textarea that is suppose to have TinyMCE.  I have checked everything I can think of without any luck; so asking here in case someone can shed some light on this problem.

Could this be what your looking for?

https://www.boonex.com/PaymentProvider/premium_download/moxie

Don't know if that is part of the TinyMCE

Hi GG. I know you said you've checked everything you can think of, but can't assume what I'm going to suggest is what you've checked, so I would check that TinyMCE files on the filesystem are there, the filesystem permissions are correct (and the same as a default 7.3 installation).

I'd also check if you can access (from the public/remote web not localhost) direct access to the TinyMCE code or create a template block/page accessing the TinyMCE code.

From the browser perspective, I'd test it on different browsers. I use Firefox extensively but I have seen Firefox, for absolutely no reason, stop processing js and then 10 minutes later, for absolutely no reason, start again.

I try to avoid looking at code because that opens a can of worms, but the last resort would be looking at the code for the calling functions of TinyMCE. If those code is there, I'd trouble-shoot system calls or use strace (on Linux) to see what's happening.

This happened once before on a site I was working on. Somehow the 'sys_editor_default' entry in the 'sys_options' table of the database was emptied. If that's the case on your install, set the value to 'sys_tinymce'. Here's the original query for it:

INSERT INTO `sys_options` VALUES ('sys_editor_default', 'sys_tinymce', @iCatHidden, 'Default HTML editor', 'digit', '', '', 91, '');

INSERT INTO `sys_options` VALUES ('sys_editor_default', 'sys_tinymce', @iCatHidden, 'Default HTML editor', 'digit', '', '', 91, '');

Smacks head; I bet that is the answer.  When I perform the upgrade, I lost several rows from the sys_options table; and the same happened to another member on here during an upgrade.  I would ask for the upgrade scripts to be examined but I am sure Boonex would just dismiss it off-hand.  I think I should examine the sys_options table in detail.  Thanks for the info.

Update: the entire row was missing.  The upgrade really did some damage on the sys_options table.

 What else is missing?

~~~~~~~~~~~~~~~~~~~~~~
Michel ✈ Meta-Travel.com
~~~~~~~~~~~~~~~~~~~~~~

Not including the default HTML editor, it also removed the rows for the site licensing and the site version.  I think other rows are missing from the sys_options table and may be accounting for other issues on the site.  I am going to look at the backup of the sys_options table and see what other damage was caused by the upgrade.  I have upgraded Dolphin many times and this is the first time I had the upgrade to damage the database.

I've upgraded a number of sites from 7.1.0 all the way to 7.3.0 without any issues. So it seems some kind of exceptional issue occurred here. Can you check the patches you applied or try upgrading again from a backup (maybe on a copy of the site)?

If I upgrade another site, I will download fresh copies of the patches.  As for starting over, no way, it is going to be quicker to just work out the issues; the site had over 30 third party modules that had to be upgraded outside of the Dolphin upgrade.  The changes that Boonex made to Dolphin; many of which I consider insignificant or worthless really caused one of the worst upgrade I have ever done with Dolphin and it was because it caused just about every module that generated pages to have to make changes in their layout to accommodate a rather worthless addition that I implemented in Dolphin 7.1.x using the Profile Customiser; and one that I will probably have to rip out before I upgrade my site.  In fact, I have been considering abandoning Dolphin because of the stupidity I see in the 7.2-7.3 branches. 

 What would be your choice of alternative to Dolphin?

Greetings

Mayki

I would not actually abandon Dolphin, I still consider it the best platform of its kind.  I am frustrated with some of the direction that Dolphin has gone in and the whole 7.3 mess of just slapping in a column without thinking of the consequences.  Instead of upgrading to 7.3, I should just develop 7.1.6 improving it.  Boonex does allow one to fork Dolphin now although I don't know how that really works; I am guessing that the licensing of the fork would be through Boonex; they still get the licensing fees; I asked about it on the Blog that Andrew posted but got no answers.

When looking historically at other Open Source projects that have forked off the main frameworks, the licensing model hasn't existed. They were true forks to develop on the framework of the software when certain groups of people decided to fork.

There's some major projects that have done this, case in point SugarCRM / Vtiger, Bacula / Bareos, and there are many others. Some have gotten themselves into a mess of disputes (legal or otherwise) while others worked a treat.

When you have a licensing model in place you need clarity as to whether you can actually fork or not. Otherwise the the fork is more or less just so people can contribute code to the main source tree.

The other problem with forking off a main tree is if the code is not commented well, you have to figure everything out yourself. Documentation is key there and unfortunately documentation takes time.

Hell, we don't even have a user manual and sometimes features are added that are not documented.  I had such a feature to prevent the login form from working.

Yes, that's one of the things I noticed most prevalent in Dolphin. I have a (very) long history of working in IT and with Open Source software, over 22 years, before it was termed as Open Source. I've contributed to more than 20 Open Source projects over those years in varying capacities and the one thing I've found that helps the most when contributing is documentation. Without it, it's all that much harder to assist.

I can't begin to think how I would start contributing to Dolphin, if I had the inclination, as it's documentation is too sparse and too basic, add to that the various tips and tricks located in various forums, which may or may not be relevant for the version you are running.

I reviewed many different social networks before landing here and choosing Dolphin, each with it's own merits and demerits. I chose Dolphin because of its flexibility with managing blocks, knowing full well it's shortcomings with documentation, support and the number of "non-free" modules from third party developers.

Out of all that though, the documentation is the most frustrating, as it limits your ability to work with the platform, help others, contribute to the project and build your own mods.