Hello and thank you. Does it mean I can add some code to my user common.js,
so that VE will work in edit window on all namespaces?
Igal (User:IKhitron)
On Jul 18, 2018 03:29, "Yaron Koren" <yaron(a)wikiworks.com> wrote:
Hi everyone,
I'm very excited to announce the release of a new MediaWiki extension:
VEForAll. Its name stands for "VisualEditor For All", and it provides
something that some people have been asking about for a long time - a way
to incorporate the VisualEditor interface into textarea inputs other than
the one in the standard VisualEditor tab.
The VEForAll extension works by providing a JavaScript function that, when
called on a textarea input, adds the VisualEditor interface to it (if the
VisualEditor extension is already installed). So the extension itself
doesn't actually do anything - instead, it provides an API for other
extensions to use. At the moment, two extensions can already make use of
VEForAll if it's there: CommentStreams and Page Forms. (You need to use the
latest version of either extension to get it working.)
You can read more about VEForAll, and download it, here:
https://www.mediawiki.org/wiki/Extension:VEForAll
This extension has five credited authors, although most of the credit goes
to the first two: Pierre Boutet and Clément Flipo of the consulting company
Dokit, and the site Wikifab. I feel like I should give both the company and
site a plug, in their honor:
http://www.dokit.io/en/about-ushttps://wikifab.org/wiki/Accueil
Please feel free to try out the extension, and let us know on the talk page
if you run into any problems.
-Yaron
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hi everyone,
I'm very excited to announce the release of a new MediaWiki extension:
VEForAll. Its name stands for "VisualEditor For All", and it provides
something that some people have been asking about for a long time - a way
to incorporate the VisualEditor interface into textarea inputs other than
the one in the standard VisualEditor tab.
The VEForAll extension works by providing a JavaScript function that, when
called on a textarea input, adds the VisualEditor interface to it (if the
VisualEditor extension is already installed). So the extension itself
doesn't actually do anything - instead, it provides an API for other
extensions to use. At the moment, two extensions can already make use of
VEForAll if it's there: CommentStreams and Page Forms. (You need to use the
latest version of either extension to get it working.)
You can read more about VEForAll, and download it, here:
https://www.mediawiki.org/wiki/Extension:VEForAll
This extension has five credited authors, although most of the credit goes
to the first two: Pierre Boutet and Clément Flipo of the consulting company
Dokit, and the site Wikifab. I feel like I should give both the company and
site a plug, in their honor:
http://www.dokit.io/en/about-ushttps://wikifab.org/wiki/Accueil
Please feel free to try out the extension, and let us know on the talk page
if you run into any problems.
-Yaron
Hello,
I am writing to you on behalf of the Leicestershire County Council regarding your software MediaWiki. We are currently in the process of moving to Office 365 Pro Plus and we would like to know if your application would still be working once these changes are made.
Please can you confirm whether Office 365 Pro Plus is compatible with your application?
Thank you,
Krishna Thanki | Assistant Technical Specialist
Information and Technology Services | Applications Management | Development Team 2
Corporate Resources | Leicestershire County Council | Tel 0116 305 4041
_______________________________________________________________________________________________________________
This e-mail and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this e-mail is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received.
Incoming and outgoing e-mail messages are routinely monitored for compliance with Leicestershire County Council's policy on the use of electronic communications. The contents of e-mails may have to be disclosed for requests under Data Protection or Freedom of Information legislation.
The views expressed by the author may not necessarily reflect the views or policies of the Leicestershire County Council.
Attachments to e-mail messages may contain viruses that may damage your system. Whilst Leicestershire County Council has taken every reasonable precaution to minimise this risk, we cannot accept any liability for any damage which you sustain as a result of these factors. You are advised to carry out your own virus checks before opening any attachment.
I have been playing with Scribunto recently and the one thing that struck me as odd was that Lua has a number of methods like table.foo or string.foo, but I did not find any factory module leveraging these methods to provide someting more intuitive like someTable:foo or someString:foo.
Is it just not worth it or did I miss anything?
Stephan
Heiya,
I configured a wiki to use`$wgEnableDnsBlacklist = true;` (also added
"$wgDnsBlacklistUrls"). So far so good.
Now I have the situation that a user (with sysop permission) cannot log
into the wiki because the respective IP-address was blocked. Is there a
permission or setting, etc. that will allow me to get the user on board
again without having to disable DNS blacklist checks? It is not the
"ipblock-exempt" or "proxyunbannable" permissions with the latter not
available any more anyways.
Thanks for your time.
Cheers Karsten
We use tooltips with the fields in the MediaWiki forms using #info
<https://www.semantic-mediawiki.org/wiki/Help:Adding_tooltips> tooltips.
Now we want to use tables in the tooltip text. Manual page says it's not
possible ("There is limited support for wikitext formatting such as bold,
italics and internal links. No paragraphs, tables, lists or any other
*block* elements are allowed"). Is there another way to do this?
Thanks for your reply.
Cheers, Jethro
I use Flow (Structured Discussions) on all of my Talk namespaces.
My understanding is that Flow discussions are not text searchable using the mediawiki search tool.
Is there a way to eliminate the talk namespaces from the list of namespaces that result when you select "Advanced" on the "Special:Search" page?
-Rich
Heiya,
I think that the docu to $wgEmailAuthentication was wrong so I changed
it [0]. I have a wiki which was switched to "false" as a setting and I
still get notifications since the respective user preference options for
email notifications are selected on special page "Preferences". I want
to make sure that the docu is correct.
Moreover all the related configuration parameters like e.g.
$wgEnotifUserTalk state that they are being ignored if the setting to
$wgEmailAuthentication is "false". I guess these need to be changed too?
Alternatively it may be the case that the selection of a user via
special page Preferences for the respective preference options override
whatever one set via the respective configuration parameters. This would
have to be noted too.
I would like to sort this out properly. Thanks for your insights.
Cheers,
Karsten
PS I believe that it makes sense to send notifications to emails if
provided even if they were not authenticated in a second step. Probably
you would not like to have this on a public wiki with high activity but
this is another story.
[0]
https://www.mediawiki.org/w/index.php?title=Manual%3A%24wgEmailAuthenticati…
A while back I imported pages from the custom namespace of another wiki to the Main namespace of my wiki (e.g. XYZ:pagenames). The pages worked fine in the Main namespace.
Recently I created that custom namespace and was hoping that the old pages would magically relocate themselves into the new namespace ... they did not. Nor are they accessible anymore by any means that I know of. They show up in a list pages from Special:AllPages looking only at the Main namespace, but when I click on them, it says the page does not exist.
Is there a maintenance script that will fix this?
-Rich
- Richard Evans, NASA GRC - Plum Brook Station
http://www.linkedin.com/in/rkevans
(c)216.973.4398
anyone know how to sync the pages of a namespace in one wiki to another wiki on the same server?
I the same server, I'd like to configure a wiki (say wiki 1) such that any page created or edited in namespace X on wiki 1 is automatically saved to namespace Y on wiki 2. I'd like this to be occur behind the scenes automatically. Has anyone done this before?
-Rich