Is it possible to use InputBox with VisualEditor ?
Is it possible to use InputBox with VisualEditor ?
I guess you are asking about the create article "problem"?
I'm a newbie, so probably what I'm suggesing might be very bad, but worked for me
so I search in the source files and found that if you change the file /extensions/Inputbox/Inputbox.classes.php and change action to veaction (see below) the magic happens. This doesn't work When you are using the parameter prefix, it won't create an article with prefix in the name.
$htmlOut .= Xml::openElement( 'input', array( 'type' => 'hidden', 'name' => 'veaction', 'value' => 'edit', )
An easier way (now) to do this is add the parameter 'useve' for InputBox. I'm not sure when this was added, but I'm running MediaWiki 1.26.2.
Thanks for that ;-)
Do you know if using a preload is possible with VisualEditor?
@Mattho69 Did you manage to get preload working with VisualEditor?
I'm not sure what you mean by preload. I'm pretty new to administering an instance of MediaWiki. Still figuring a lot out. Sorry I can't be of more help.
This is currently a bug in VisualEditor. See bug tracking at https://phabricator.wikimedia.org/T51622
Is there a way to add the ajax search suggestion to an inputbox? Thanks
I would like to know this too.
In my eyes the search is no fun if there's no autocompletion / suggestions...
I have found a hack to add ajax suggestions to any inputbox. You must add the following code to your MediaWiki:Common.js, and refresh browser cache.
document.getElementById('searchform').action = '/w/index.php'; document.getElementsByName('search').id = 'searchInput';
When using useve=true and type=create, the url doesn't contain the correct parameter "&vecreate=inputboxcontents"
type = create
buttonlabel = Create pre-print
placeholder = Pre-print title
break = no
As part of the solution, the current syntax calls the url:
Whereas it should call:
If you can remove the empty parameters (preload=&editintro=&summary=&nosummary=&prefix=&minor=) the function should call properly.
As my works in Manchu test of Wikipedia, I found the width parameter is not enough in an element uses top-to-bottom direction, if you use it, the box would be very long, and it would out of page even if you add the height in this element (see this page, tested on the latest version of Firefox). So I think this parameter should be added in this extension, but defaulting to nothing (i.e. this parameter should be activated only when you input it).
What's the use case of having a "vertical" inputbox?
I'd like to propose two new functions to this extension. The first is a button color/class option. E.g. green button could be managed by "buttoncolor=green" or by 'buttonclass=mw-ui-progressive". The second is the level of the new section heading. E.g. 3rd heading could be managed by "headinglevel=3" What do you think? Could they be added?
@Dvorapa: Re: button colors - One goal of the ongoing design work, is to make a User Interface that is consistent, as in, once people are familiar with a button's action/outcome, they can expect consistent results. Hence, the button to submit a form (as in this extension, and others) should always be a single color (blue in our case). There's some related information at this (slightly outdated) page: Wikimedia Foundation Design/Color usage#Functional Colors.
Re: heading levels - I almost filed a feature-request for this in phabricator, but then I couldn't find any examples (I checked a few dozen pages linked from en:WP:Requests). Here's what I had drafted; please add your use-case, and any pre-existing examples you can find, and post it in phab.
Note: I'm not sure if this is technically feasible though. The current system just hooks into the standard "New topic" tab on all talkpages. Adding new code to allow changing the H-level might be more complex than is desired.
This would be super helpful - it is difficult to design a page around the light grey color of the 'create' button.
I wondering there is no option for this as old templates support this on Wikimedia like Template:Clickable_button, I see this because someone used some unicode signs which are not really supported by many systems: 🔍
I believe this would be covered by phab:T106948 ("Convert InputBox to use OOJs UI where possible"), but I'll ask some folks...
I believe that task would cover the issue of extensions/tools which desire to have consistent/pre-determined icons within buttons, see examples in OOjs_UI/Widgets/Buttons_and_Switches. So, after that work was done, additional work could be done on the InputBox extension to include a magnifying-glass icon on the
type=fulltext/search/search2 form input buttons by default. However, changing the image manually for each usage of the InputBox, would run counter to the desire for standardization (for a more intuitive/learn-able interface). HTH.
Hi, I have a header search box but I can't find a way to edit it and use InputBox, more precisely i wanted to do something like this:
<inputbox>type=search namespaces=Main**,Help </inputbox>
So users could selected categories to search. How can I change this?
That should work, assuming you mean "namespace" and not "categories". (See functional example at W:en:Help:Contents)
If you mean "categories", I don't believe it is possible to use the checkboxes for those. However, defaults could be entered in, per Help:CirrusSearch#Filters (intitle:, incategory: and linksto:). e.g.
<inputbox> type=search default=incategory:"Freeware games" incategory:"Art games" </inputbox>
Can anyone provide an example to show how the "summary" parameter works? The example provided does not seem to have an edit summary.
It doesn't seem to work with type "comment", only with "create" and "move". I'll update the docs.
Can someone remove Flow? I would like to use this talkpage, and Flow is a buggy mess.
You apparently just managed to use this talk page using Flow.