vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Is there an easy way to go back to the old Editor? (https://vborg.vbsupport.ru/showthread.php?t=265244)

fxwoody 06-15-2011 10:55 PM

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 06-16-2011 04:20 AM

@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 06-16-2011 05:22 AM

Quote:

Originally Posted by Sarteck (Post 2208351)
@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.
Quote:

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.

Quote:

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.
Quote:

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 06-16-2011 05:54 AM

You can downgrade your forum:
https://www.vbulletin.com/forum/show...60#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 06-16-2011 06:15 AM

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 06-16-2011 06:22 AM

@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 06-16-2011 06:28 AM

Quote:

Originally Posted by Sarteck (Post 2208377)
@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 06-16-2011 06:55 AM

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

fxwoody 06-16-2011 07:09 AM

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 06-16-2011 08:11 AM

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 [DATE]1308215545[/DATE] at [TIME]1308215545[/TIME] ---------------

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


All times are GMT. The time now is 11:24 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01002 seconds
  • Memory Usage 1,747KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (3)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete