Topic on Extension talk:VisualEditor

Jump to navigation Jump to search

Behavior switch __NOVISUALEDITOR__

Jongfeli (talkcontribs)

Hello, is there or will there be a behavior switch like __NOVISUALEDITOR__ to be able to disable VisualEditor on a certain page or group of pages. We have a Semantic Wiki and on the pages that use forms it would be nice to be able to disable VisualEditor. We are not using VisualEditor on our production wiki's yet but it has great potential for those people that just "don't want to" learn the wiki syntax and want to click around like there where using Word :) Thanks.

Kghbln (talkcontribs)

+1 Nice idea, however it should come with a parameter for "LocalSettings.php" which allows to activate or deactivate this switch. Cheers

He7d3r (talkcontribs)

Will VisualEditor support this switch (i.e., auto-destruction)?

Jdforrester (WMF) (talkcontribs)

There isn't such a behaviour switch; we could add one, but it seems unnecessary. If SMW is written correctly, items like forms should just get "alienated" and not cause any issues – you have to actively write a node handler for VisualEditor to touch any unknown HTML fragments.

Jongfeli (talkcontribs)

James you are right but I am not proposing this to "protect" pages from VisualEditor because they break. In this case the "problem" is not VisualEditor, Semantic Mediawiki or Semantic Forms. As far as I can see they all behave as expected nothing gets broken. The reason is that in some cases it just makes sense that a user does not have the option to use VisualEditor at all on a specific page in a NS where VisualEditor is enabled. One of the reasons is a page on a Semantic Wiki that is maintained with a form. There are probably lots of scenarios where it would also make sense to be able to do this. Regards and have a nice weekend:)

Sj (talkcontribs)

Nice idea! I would also find this very useful.

For instance, on wikis I maintain, there are pages in every namespace that are mainly edited to leave signatures. Since that is currently impossible in VE, and a fix is not on the horizon, I would prefer to be able to disable VE on those pages. There is no reason for anyone to use VE to edit those pages; it will only confuse or frustrate them. (One or two editors might want to edit the framework context of the pages, but they are essentially set up once by the author or coordinator, and everyone else is just finding the appropriate section and signing their name or vote).


Jaideraf (talkcontribs)

+1 for __NOVISUALEDITOR__. I love VisualEditor, but I would love to be able to choose when to use or not in a page (via template transclusion).

John Vandenberg (talkcontribs)

fwiw, this was declined at T54141.

Jongfeli (talkcontribs)

I did not proposed this because of T54141 it actually has nothing to do with it. Like explained above, I think that such a switch is very useful for a lot of MediaWiki users. Some wiki's are very dynamic and use different extensions to get the desired result. Being able to control when users are able to use VisualEditor is a powerful tool but that is just my humble opinion :).

Reply to "Behavior switch __NOVISUALEDITOR__"