Forum:Request disabling automatic use of VisualEditor: Difference between revisions
imported>K6ka |
imported>LostInRiverview mNo edit summary |
||
| Line 4: | Line 4: | ||
When VisualEditor was announced, I was optimistic that it would fix many of the nagging problems present in the Rich Text Editor (aka the WYSIWYG editor), such as the addition of blank lines, breaking of complicated templates, etc. Before VisualEditor, we could force people to edit in source mode by adding <nowiki>__NOWYSIWYG__</nowiki> to especially sensitive pages, but VisualEditor simply ignores those tags. |
When VisualEditor was announced, I was optimistic that it would fix many of the nagging problems present in the Rich Text Editor (aka the WYSIWYG editor), such as the addition of blank lines, breaking of complicated templates, etc. Before VisualEditor, we could force people to edit in source mode by adding <nowiki>__NOWYSIWYG__</nowiki> to especially sensitive pages, but VisualEditor simply ignores those tags. |
||
Right now, the Visual Editor is disabled by default for registered users, but it can be enabled in each person's preferences. However, it is ''enabled'' by default for all unregistered users. This means that any page that an unregistered user can edit which has complex code can be broken by that user, ''even if they don't directly edit the "complex" feature'' |
Right now, the Visual Editor is disabled by default for registered users, but it can be enabled in each person's preferences. However, it is ''enabled'' by default for all unregistered users. This means that any page that an unregistered user can edit which has complex code can be broken by that user, ''even if they don't directly edit the "complex" feature''; this is apparent on our [[The Sims Wiki:Battles|Battles page]], as well as many others. On top of that, we have no way to prevent use of the VisualEditor on these pages, as the software ignores the <nowiki>__NOWYSIWYG__</nowiki> tags. The only way to prevent VisualEditor being used on these pages extensively is to limit access to the page. It would be highly detrimental to semi-protect that page and other pages simply because they contain complex text. So, our only options left are to appeal to Wikia Staff to disable default VisualEditor use for unregistered editors on the wiki, to semi-protect all "breakable" pages on the wiki, or get used to having to constantly clean up after the collateral damage of this latest experiment. |
||
Therefore, I am requesting that we contact Wikia Staff and respectfully ask them to disable VisualEditor for anonymous users on the wiki. -- '''[[User:LostInRiverview|<font color="navy">LostInRiverview</font>]]<sup> [[User_talk:LostInRiverview|<font color="green">talk</font>]] ~ [[User_blog:LostInRiverview|<font color="green">blog</font>]]</sup>''' 22:48, July 5, 2014 (UTC) |
Therefore, I am requesting that we contact Wikia Staff and respectfully ask them to disable VisualEditor for anonymous users on the wiki. -- '''[[User:LostInRiverview|<font color="navy">LostInRiverview</font>]]<sup> [[User_talk:LostInRiverview|<font color="green">talk</font>]] ~ [[User_blog:LostInRiverview|<font color="green">blog</font>]]</sup>''' 22:48, July 5, 2014 (UTC) |
||
Revision as of 22:51, 5 July 2014
Although we are presently discussing a policy to prevent forced features, I feel we should also draft a separate request for Wikia Staff to disable use of the VisualEditor on this wiki by all people.
When VisualEditor was announced, I was optimistic that it would fix many of the nagging problems present in the Rich Text Editor (aka the WYSIWYG editor), such as the addition of blank lines, breaking of complicated templates, etc. Before VisualEditor, we could force people to edit in source mode by adding __NOWYSIWYG__ to especially sensitive pages, but VisualEditor simply ignores those tags.
Right now, the Visual Editor is disabled by default for registered users, but it can be enabled in each person's preferences. However, it is enabled by default for all unregistered users. This means that any page that an unregistered user can edit which has complex code can be broken by that user, even if they don't directly edit the "complex" feature; this is apparent on our Battles page, as well as many others. On top of that, we have no way to prevent use of the VisualEditor on these pages, as the software ignores the __NOWYSIWYG__ tags. The only way to prevent VisualEditor being used on these pages extensively is to limit access to the page. It would be highly detrimental to semi-protect that page and other pages simply because they contain complex text. So, our only options left are to appeal to Wikia Staff to disable default VisualEditor use for unregistered editors on the wiki, to semi-protect all "breakable" pages on the wiki, or get used to having to constantly clean up after the collateral damage of this latest experiment.
Therefore, I am requesting that we contact Wikia Staff and respectfully ask them to disable VisualEditor for anonymous users on the wiki. -- LostInRiverview talk ~ blog 22:48, July 5, 2014 (UTC)
Discussion
Or at least not make it the "default" editor. Anonymous editors can go back to the old editor by clicking on the drop-down menu and selecting "Classic Editor", but who's honestly going to do that every single time? Therefore I support this proposal. VisualEditor, at least until 100% of its kinks are ironed out, should be completely optional. --k6ka (talk | contribs) 22:50, July 5, 2014 (UTC)