Nedjo has done a great job cleaning up CVS and writing 2 feature enabling patches (form based custom TinyMCE configuration and JQuery support). It's been all I could do to keep the back log of issues and feature requests to a minimum while deadlines at my "real" job were my priority.
We've just launched the beta of OurTahoe.org, so I have more "free" time to dedicate to TinyMCE. I'd really like to get the custom version of TinyMCE we're using at UNR updated so that I'm running a release version. To do that I need form based custom TinyMCE configuration to work with module that add textareas to the node add form like Node Teaser. Currently using the patch with multiple textareas causes duplicate TinyMCE calls. Nedjo believes that using JQuery instead of tinyMCE.init() will solve that problem. Currently the JQuery patch causes other issues.
I've set up 3 semi-public new test sites to work through the issues...
http://tinymce-roles.sidewalktheory.com
http://tinymce-jquery.sidewalktheory.com
http://tinymce-jqueryroles.sidewalktheory.com (not working yet)
I'll email everyone in the group the admin username/password individually. The reason I've set these up is the third big issue that I've been working... the state of the .install. There are definitely some issues with Nedjo's patches depending on what version on TinyMCE you are coming from. The old 5.1 users don't even have the settings and roles files this patch tried to update. In addition, the install needs to address the fact that Moxie actually renamed the TinyMCE tables. Users who had TinyMCE installed that went to Moxie and are now trying to come back to TinyMCE are missing these tables as well.
In the next release, I'd like the .install to work for all the versions we know are out there.
If you have some time to offer feedback on the state of these updates, I'd appreciate it. If you'd like to test them with a specific module, let me know and I'll install it.
Comments
I don't think we need to
I don't think we need to cover all cases. The way TinyMCE works, the table stuff is really not THAT critical. It's unfortunate, but you CAN just blow away all tables and then do a clean install and be set on the new system.
I would suggest minimal work on older use cases...esp. any of the moxie stuff.
Volunteering?
Is this your way of volunteering to respond to the support issues about this from the queue :) Nedjo added a nice warning for users that informs them they are missing the TinyMCE itself. The next most common issue in the queue has been from users who have problems with the install because of the version of TinyMCE they used before. The code that is there only works as upgrade for 4.7 users. The install fails for everyone else. Users who installed the previous 5.1 won't be able to install the fix without clearing the tinymce record from their system table. It is hard to focus on real issues when there are several of those each week.
I expect Allie and Steve to be as outraged about asking someone to manually delete a row from the system table as they were about requiring users to edit a comma separated list. Users shouldn't have to deal with that to install an "upgrade" to the module.
For the record, I was also
For the record, I was also "outraged" -- it's not about editing the list, it's about multiple configurations in a multi-site environment.
And yep, the varying source --> upgrade paths really suck....and yes, I do volunteer to do that: we need to set all of those to "support" and then have a place where we can point people to super clear documentation.
First support feedback is: remove previous versions of TinyMCE from your system, do X (where X is likely either a PHPMYAdmin command), and then follow install instructions.