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 (http://tracker.vbulletin.com/browse/VBIV-12351)

[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 :)

[fxwoody]

great idea cellarius! Did voted yes ;)
Now, where do we stand as far as our troubles with "hide & code" or other extras???

Don't really care for my other options but my "hide" is the main focus here :)

Tks guys! Good work ;)

[Sarteck]

@cellarius, I understand what you're saying... I just don't get why we even started using the new editor. Was something broken with the old one? (It worked perfectly fine for me, tbh.) Was there some feature that vBulletin didn't know how to implement into their own editor?

Not that it matters, now, I guess. I doubt they'll be giving us any option (other than downgrading) to go back to the old editor.

I also voted for that issue on the tracker, because I very much would like to have some kind of control over the editor styling without having to edit files that are just going to be over-written with the next update anyways.

In the meantime, since we really have no other option available, if any of you guys happen to run into tutorials on editing this Editor, I'd appreciate if you could post a link here.

On the subject of the editor, several of my members (but not all) are experiencing some weird phenomenon with the editor that I just can't recreate. They are not able to insert line breaks by pressing Enter. This is pretty horrible for a lot of them that write multi-paragraph posts.

Furthermore, at the end of a line they write, the words are not moved to the next line if they spill over the edge--the word just breaks in the middle. For example, if the line they were writing was ending with the word "example," then "exa" would appear on the first line, and then "mple" would appear on the line underneath.

Does anyone know what could be causing this behaviour?

[cellarius]

@cellarius, I understand what you're saying... I just don't get why we even started using the new editor. Was something broken with the old one? (It worked perfectly fine for me, tbh.) Was there some feature that vBulletin didn't know how to implement into their own editor?
Yes. WYSIWYG did not work in Webkit (Chrome/Safari) browsers or Opera, especially the first a growing marketshare. It did not work well for the CMS at all, and it was a mess regarding the different implementations for forum posts, blog, groups, visitor messages, and so on. In my opinion, it was high time. And it makes sense to implement a well coded third party editor instead of making one's own. It was different 10 years or so back when you basically had to cater for two browsers only. The browser market is in constant shifting with many players, and dev time is better spent on other things, leaving the editor to people who concentrate on that. CKE is actually much more expandable than the old one. What we have now is the very first iteration, and I'm sure we'll see it improved and the issues it still has ironed out. Overall, it works pretty well is my impression.

Not that it matters, now, I guess. I doubt they'll be giving us any option (other than downgrading) to go back to the old editor.No, there indeed is no way back, and maintaining the old editor as option would be a bloody mess (and render all the positive impact to zero). There will be no optional old editor, and that's actually a good thing. I have addons pluging into the editor, and I would cry if I had to do them for two editors that work completely different.

I also voted for that issue on the tracker, because I very much would like to have some kind of control over the editor styling without having to edit files that are just going to be over-written with the next update anyways.In the meantime, since we really have no other option available, if any of you guys happen to run into tutorials on editing this Editor, I'd appreciate if you could post a link here.Well, as I wrote in my tracker entry, you can use additional.css with !important on each style definition. What classes to use can be seen in the styles folder in CKEs directory in clientscript.

For support with the editor you really should go to vbulletin.com.

[masterross]

You can downgrade your forum:
https://www.vbulletin.com/forum/showthread.php/381783-How-to-disable-this-full-of-bugs-CKE-Editor?p=2171360#post2171360

The only problem I saw is the "what's new" shows only 1 page even I clicked on 2,3 etc... but it's not big deal for me as the old editor works and my plugins too.

Regards!

[cellarius]

Of course you can downgrade, but that's not a way back to the old editor - unless you want to stay on 4.1.3 forever. But of course it can be a solve for the time being.

[Sarteck]

@cellarius, that's funny, because my Chrome/Safari and Opera users right now are the ones having the most issues with the new editor. Previously they had no problems whatsoever.... Are you sure you haven't got that reversed? O.o

@masterross, I'm going to talk with my Staff and see what they think about doing that. I'd prefer the downgrade right about now, because this new editor renders my forum VERY hard to use for many of my members. Kudos for the link and method!

EDIT, as for going to vB.com, everytime someone posts there about wanting to change something, they're told to come here. XP Thought I would save the trouble.

[cellarius]

@cellarius, that's funny, because my Chrome/Safari and Opera users right now are the ones having the most issues with the new editor. Previously they had no problems whatsoever.... Are you sure you haven't got that reversed?
Yes, I am sure. Ask them whether they had a WYSIWYG editor before.

[masterross]

Agree mate ;)
But I hope IB will fix the mess with this CKEeditor and custom BB codes (CSS) in next release.

[fxwoody]

I found the perfect solution! Went back to my 4.1.3 ;)

Clean and working like a charm!

Will not update anymore unless totally necessary! For sure :)

[Post Reader]

yeah its a problem for me too.. i have just disabled the WYSIWIG editor mode and using the standard editor for my new threads and replies.... its not a good thing that we cant restore to the old editor as many members are complaining about the new Ck Editor

--------------- Added 1308215545 at 1308215545 ---------------

well in my personal opinion vBulletin should have given the option to disable or enable the new Ck Editor

[Sarteck]

Yes, I am sure. Ask them whether they had a WYSIWYG editor before.

They didn't have one forced on them, no. They had the option to use the basic editor plus formatting tools, or the WYSIWYG.

Now, they have the same thing--basic editor plus formatting tools or WYSIWYG. Except THIS one causes errors.

For many of them, words don't get wrapped properly, line breaks are not inserted in posts, etc. With the Quick Edit, all the time, my line breaks disappear--same goes for everyone else on my forum, even on a clean test style.



For this WYSIWYG that supposedly works better for Chrome/Safari and Opera users, it's NOT working better. Again--the old editor was worked just great for them. Not sure if they were using the WYSIWYG or the Basic plus Formatting tools, but does that matter? Now, whichever way they go (WYSIWYG or otherwise), they're screwed. At least if we stick with this editor.



Which we most likely are not--we'll probably be giving masterross' "downgrade" a try, to see if it works out for us. (For those of you wondering how it'll work out, I'll post back a few times with status updates on it.)

[cellarius]

They didn't have one forced on them, no. They had the option to use the basic editor plus formatting tools, or the WYSIWYG.
Sorry, but that's nonsense. There never was a WYSIWYG option for Webkit and Opera browsers in the old editor, so where would that optionhave come from? WYSIWYG did only work in IE and Firefox, ever.

[Sarteck]

Sorry, but that's nonsense. There never was a WYSIWYG option for Webkit and Opera browsers in the old editor, so where would that optionhave come from? WYSIWYG did only work in IE and Firefox, ever.

For all I know, you might be correct. I don't use Opera, I've not used Chrome much, and I don't have a Mac.

And... your point is?

I mean, how many times do I have to repeat it--the old editor did not have problems for those users. Now, great, they have a WYSIWYG, if they didn't have it before. A WYSIWYG that doesn't work for the majority of them, and causes a crapload of problems, and isn't easily styled, so on and so forth.

What part of that is so hard to understand?



If it's between forcing Opera/Chrome/Safari users to not have a WYSIWYG, or forcing EVERYONE to have an editor that causes all these problems, I think I'll say unto the Chrome/Opera/Safari users, "sorry, guys, but you'll have to 'put up with' just doing things as you always have."



I mean, seriously, is it really hard to see that?

[cellarius]

I don't know what you hope to gain by barking at me like that. If you want to rant, look for more suiteable targets, and if you have issues, open a ticket at vb.com and report them in the bugtracker.

[Sarteck]

You are telling me, "oh, this is so great for Opera, Safari, and Chrome users!"

I'm simply telling you that's a bunch of BS. At least for my forum members, it seems to be the polar opposite.

This ain't a rant directed towards you, so sorry if you feel that way, heh. I was confused about something you'd mentioned (that this new editor is awesome for Chrome/Opera/Safari users, since my forum members have been experiencing the exact opposite).

Unless you had a hand in putting this new Editor in vB 4.1.4, that is... If that's the case, then this IS a rant against you! XP

[clubplanet]

I cant even SEE the wysiwyg editor on my forum after going to 4.1.4. It's totally gone. I'm basically looking at the basic editor with no insert or formatting options. Definitely not happy about this. It also has nothing to do with my style as it's happening on the vbulletin4 default style. This occurs in ALL browsers on ALL OS'

[Lynne]

Disable your plugins. I'll bet you have one that is causing the issue. I know at least one of my modifications here had to be fixed for the new editor, and Paul M said he had to fix one of his also.

[clubplanet]

Turns out it was an issue with Cloudflare.com, the caching service we use. When we turned it off, it started working. Now we have to figure out what setting is causing it.

[adbox]

*sobs* It's ugly and I can't go back :(.

Any advice on how style it to make it look like the old one?
The light grey is terrible. The bubbly buttons are ugly, too spaced, and too big.

How can we theme this?

[Sarteck]

<a href="http://docs.cksource.com/CKEditor_3.x/Developers_Guide/Styles" target="_blank">http://docs.cksource.com/CKEditor_3....s_Guide/Styles</a>

(NOTE: I'm having trouble making heads or tails of it, myself. XD)

[Boofo]

I don't know what you hope to gain by barking at me like that. If you want to rant, look for more suiteable targets, and if you have issues, open a ticket at vb.com and report them in the bugtracker.

Woof! Woof! ;)

[cellarius]

Woof! Woof! ;)
Would be interesting to find out who's the bigger dog among the two of us :p

[Boofo]

That would be quite the contest I think. We might be better off just sharing the title. ;)

[cellarius]

OK, for now, but should I ever come to Iowa, beware! :D (<- showing teeth)

[Boofo]

You'll just get lost in a cornfield and I will have to sniff you out. ;)

We could always tag-team, too, you know.

[cellarius]

True. And a pack we would be. But hell, are we off topic...

[TheLastSuperman]

I always wait one to two weeks before upgrading myself, I recommend waiting to view the initial bug reports from a new version all the time to clients and friends yet it goes virtually unheard :p.

You'll just get lost in a cornfield and I will have to sniff you out. ;)

We could always tag-team, too, you know.

True. And a pack we would be. But hell, are we off topic...

And when you two make it to Wrestlemania I'll be there!

[Boofo]

True. And a pack we would be. But hell, are we off topic...

Probably... but, what the hey. ;)

I always wait one to two weeks before upgrading myself, I recommend waiting to view the initial bug reports from a new version all the time to clients and friends yet it goes virtually unheard :p.

Same here. I always watch to see what problems occur and if they can be solved easily before I do any upgrades. I'm usually glad I waited. ;)

And when you two make it to Wrestlemania I'll be there!

Wrestlemania probably couldn't handle both of us together.

[KissOfDeath]

I completely agree, i hate this new editor, members are complaining that it's slow and theirs a delay before they can actually post anything, and theirs a difference between a plugin and custom bb code, i'm also having the same problem when trying to use multiple custom bb codes which are essential to running my forum reverting would cost me to much

[Lostboyfan]

I like the new editor. It saves your stuff when you are typing. Meaning if your vbulletin logs you out and you where in the middle of typing it will auto-save it.

It works fine for me on my forum and none of my members have complained about it.