Is there an easy way to go back to the old Editor?

[Sarteck]

I upgraded to vB 4.1.4 just a little while ago to have some of the bug fixes that I've been waiting a while for. Unfortunately, the upgrade slapped an ugly text editor onto my site that doesn't even seem to work for many of my members.

Although I'd hate to do so, I could deal with having to re-style every single Skin we use. It would suck, since I'd have to go through and style each and every one that we created ourselves, not to mention the ones we've downloaded from here that OTHER people created which I'd either have to edit myself or wait for them to get their butts in gear. (Can't blame 'em for not wanting to bother with it, though, heh.)

Like I said, though, having to re-Style everything would be a minor inconvenience, if that was the only problem. Many of my users (on several browsers, and yes, after clearing caches) are unable to use the damned thing. The buttons are invisible for them, the editing of posts just hangs and does not complete the edit, the Reply with Quote doesn't even load. (Before you even respond with the usual, "disable your plugins and see if that fixes it," yes, this is likely due to one of my Plugins, MARCO1's advanced quick-reply/edit, but I don't want to get rid of that--at least with that enabled, I have SOME decent-looking editor that actually WORKS for those users having trouble.)

I've looked around a bit for an option to use the old Editor instead of this shiny new (ugly, broken) CKEditor, hoping that vBulletin would be thoughtful enough to give us a choice on what we wanted to use. I cannot find such an option, myself, but I'm hoping that someone here can tell me I'm an idiot, and just not looking hard enough.

[Brandon Sheley]

Update your styles or restore a backup.

The new editor isn't broken at all, your style is most likely the issue...

[Sarteck]

Brandon, thanks, but that doesn't really answer my question.

Also, yes, my styles are the issue--they worked on vB 4.1.3. So of course, yes, they'd be broken for 4.1.4. I should have realized that ahead of time, you're probably right.

It's not that the new editor is broken--it's that the new editor breaks my forum. And looks ugly, and can't easily be modified, and ignores the StyleVars we use for styling everything else... Do I need to go on?

Don't misunderstand me--if people want to use that on their own forums, it's great and all. But it takes a much longer time to load on the page than our old editor, destroys styles that previously worked without any kind of problem, and has no easy way for modification that will actually stick around for the next upgrade. I think it would be nice for vB to give us the option to continue using the old editor, which absolutely zero of my members ever had a problem with. :<

So, other than restoring from a backup to revert back to vB 4.1.3, is there an option to restore the old editor?

[Lynne]

No, there is no way to restore the old editor.

[strudinox]

Apparently the new CK editor uses a theme system. I'm not sure how to use it but that might be a good place to start since you can't go back.

[Sarteck]

From everything I've read, we have to edit the files in /clientscript/ckeditor to make our own themes. Nowhere at vB.com or vB.org can I find instructions on how to do that, so obviously I'm going to be doing a bunch of trial and error crap.



Here's something that is NOT the fault of any of my styles, and as far as I can tell, not the fault of any of my plugins.

We have several Custom BB Codes that were working fine and dandy as buttons on the previous editor. On this new editor, each of them ONLY gives the BB Code for the newest custom BB Code we created.

E.G., we have a {spoiler=TITLE}Spoiler Text{/spoiler} code, but when we click the button for it, it only returns the {rizonirc}#channel{/rizonirc} BB Code we created. The Rizon IRC BB Code is used for every custom button we have.

The IRC BB Code does not have a button itself, and I am assuming it's being used for some reason because it's the newest BB Code we created.


It acts like this even on a new default skin with no modifications what-so-ever.

Does anyone else have similar behaviour?

[Lynne]

There is a bug report for that already.

In Source mode, any custom BB code buttons always insert the last custom BB code tags

[Sarteck]

I was kind of hoping that I really was doing something wrong... :<

Well, I voted for it. Not sure if that means anything. I just wish I knew how this new editor works so I could try to put a temp fix on it. Lots of my members are going to be asking me why they keep getting an Iframe to Rizon IRC put in their posts.

[fxwoody]

Totally agree with Sarteck on this one! I have the same troubles and lost way to much time improving my board and functionallity to go back to 4.1.3 and wait for some news on how to fix it!

I have the old proverb saying "Don't fix it if it's not broken" but i our case, us the skins transformer, that we always end up with bunch of troubles after updates.

I really think there should be a standard in coding the new stuff with effect that plugins should be taken in consideration for future updates!
It's cool to have the latest version but when you have to go back and pass days in fixing things back on how they were before......starting to question the update purposes

So, i guess we should refer to your bug report and see how it will be fix, for now.

[cellarius]

You can't implement a new editor and not break plugins that plug into the old editor. There's just no way.

As far as ease of styling, I opened this in the tracker:http://tracker.vbulletin.com/browse/VBIV-12413

Vote for it