Help talk:Extension:TemplateWizard

Jump to navigation Jump to search

About this board

This board is for discussing and getting help about the TemplateWizard extension.

Issues can also be reported on Phabricator, using the #mediawiki-extensions-TemplateWizard tag.

Zoeannl (talkcontribs)

It says in the info not to use 2017 wikieditor. I don't know wht editor I am using and have been having problems. How do I find different versions of wikieditor?

Jeroen N (talkcontribs)

Hi Zoeannl, to use the 2010 WikiEditor you should tick 'Enable enhanced editing toolbar' in your preferences under the 'Editing' tab, and have 'New wikitext mode' disabled under 'Beta features'. (And to use the TemplateWizard extension, enable 'TemplateWizard' under 'Beta features'.) For a complete list of all editors, see Editor.

Reply to "Wikieditor versions"
YjM (talkcontribs)

Hi all, is there a reason why the Insert Template widget in VisualEditor looks and behaves differently than the TemplateWizard in WikiEditor? Is there a plan to update the Insert Template in the way the TemplateWizard looks like? I believe this is quite important from the UX-point of view. Anyway, great update for the WikiEditor, indeed!

NKohli (WMF) (talkcontribs)

Hi @YjM. The insert template widget you see in VisualEditor has been there since a few years. The wishlist project was to bring that functionality to the WikiEditor so when we were working on it, we decided to give it a UI update. I don't believe the VisualEditor team (known as Editing team now) has any plans to update the VisualEditor version currently but I do plan to bring this up with them in case they are interested. Thanks for the feedback!

197.218.92.212 (talkcontribs)

It is because developers reinvented the wheel. To put it simply they are different applications. One only works in Wikitext Editor and the other is part of Visualeditor and doesn't work elsewhere. For instance, Visualeditor doesn't have any date input dialog, nor a specific one for adding numbers. Both are currently added as simple text.

In principle they should be sharing code, in practice chances are that they will diverge more as time goes by.

NKohli (WMF) (talkcontribs)

That's correct. The reason we had to split it up is because the template widget you see in VisualEditor is built in such a way that the code cannot be extracted out or reused outside of VE. We had a long discussion about this possibility with the VisualEditor engineers and they advised us to build it from scratch. In an ideal world, the code would be the same (and shared from the same source) between the two applications.

YjM (talkcontribs)

Thanks for the answers. Honestly, yours, @NKohli (WMF), made me sad. It makes no sense, from the user's POV, why these two things, which serves the very same purpuse, might possibly be different. I hope you will find a common ground with the V|E team and will share as much of the code as possible. I will probably propose this in this years' wishlist survey, if it helps in pushing the things forward.

Reply to "TemplateWizard in VisualEditor"

TW do not follow parameters order in TemplateData

5
Fringio (talkcontribs)

I've noticed that TW do not follow parameters order set in TemplateData. I've made an example in it:Special:PermaLink/102712468: as you can see, the template added with VE follows the parameter order set in it:Template:RIAA/TemplateData (1→opera→accesso), but the one added using TW follows the order the parameters have been added to the TemplateData (1→accesso→opera). This template has only 4 parameters, so it can be solved quite easily editing the TemplateData like this, but for more "heavy" templates this can generate a wrong wikicode.

NKohli (WMF) (talkcontribs)

@Fringio TW tries to separate required, suggested and optional parameters. Ideally, that is the order in which they should be added to TemplateData. Is that causing the issue you mention?

Fringio (talkcontribs)

I understand that, and I find very useful that the template list them in the order Required→Suggested→Optional, but I also think that it should follow the instructions about parameter order, since most of templates structure (i.e. the wikicode required for the template) do not follow the Required→Suggested→Optional order, but the order set by TemplateData.

NKohli (WMF) (talkcontribs)

When you say "instructions about parameter order", do you mean the order that's specified in TemplateData?

Fringio (talkcontribs)

Exactly.

Reply to "TW do not follow parameters order in TemplateData"
Summary by NKohli (WMF)

Unrelated

Jaimin26783 (talkcontribs)

How to create new page about movie?

NKohli (WMF) (talkcontribs)

Hi @Jaimin26783. This is the wrong venue to discuss page creation. You may contact the help desk on the wiki you need help on.

Djiboun (talkcontribs)

Could an admin tag this page to enable its translation?

NKohli (WMF) (talkcontribs)

Thanks for raising this @Djiboun. I will add more content to the page and then request an admin to enable translations.

Djiboun (talkcontribs)

Ok, thank you for your reply. I look forward to starting the french translation.

NKohli (WMF) (talkcontribs)

It is now available to translate. Thank you @Djiboun.

George Ho (talkcontribs)

I appreciate separating the "Suggested parameters" and "Optional parameters" for most templates. However, that makes using w:Template:Track listing via the wizard more awkward to use and edit. By separating its parameters into two categories, the suggested parameters would be above the optional ones when the template is inserted. titlen and lengthn are currently the suggested parameters and organized by numerals. However, optional ones, like writern and extran, would be below the supposed last/final number of titlen and lengthn, e.g. title20 and length20. The same can be said about other language versions of the template. I had to manually sort reorganize the parameters after the template insertion. Does the sorting issue matter much enough to resolve it, or what else can be done about it?

NKohli (WMF) (talkcontribs)

Hi @George Ho. This is indeed a tricky case. Do you think changing the template to make all the parameters optional is better? I don't know if TemplateWizard can be made smart enough to solve this case.

George Ho (talkcontribs)

Unless the coding is technically too complicated, I don't mind merging the "suggested" column into the "optional column". Indeed, re-sorting makes parameters easier to use, but the "optional" column would become lengthy. Nevertheless, let's test that out and see whether the change works productively.

NKohli (WMF) (talkcontribs)

To be clear, I was thinking of changing that for this specific template in its TemplateData. I don't think merging "Optional" and "Suggested" parameters into one group for all templates is a good idea. I have heard feedback that users like having those parameters be separate.

George Ho (talkcontribs)

Oh... I don't mean merging two into one for all, which I agree with you about. You can change the template's TemplateData if you want.

Reply to "Sorting parameters of "w:Template:Track listing""

Is there any way to use TemplateData alongside "subst" in TemplateWizard?

2
Hoefsldyla (talkcontribs)

Would like to substitute in the source of a Template instead of transcluding it, I am wondering if this is possible while still using TemplateData to be able to easily fill the Template.

NKohli (WMF) (talkcontribs)

@Hoefsldyla I'm not entirely sure what you are asking for here. Can you explain with an example perhaps?

Reply to "Is there any way to use TemplateData alongside "subst" in TemplateWizard?"

Disable bundled TemplateWizard or locate files

8
Summary by Hoefsldyla

Resolved

Hoefsldyla (talkcontribs)

I have a problem where I would like to edit the *.js files that make TemplateWizard work as I need some custom behaviour. The problem is that some version of TemplateWizard came "bundled" with my verison of MediaWiki. I wouldn't think this was a problem except that I have installed the Extension manually also (So that i can edit these files) but it seems to be using the bundled version and its *.js files as i can completely corrupt the ones used by the manually installed extension and the TemplateWizard still works fine. It does show up in Special:Version so i know it is installed.


To solve this problem i would ideally like to disable the bundled version of TemplateWizard unless someone can point me to where its files are located.

NKohli (WMF) (talkcontribs)

Hi @Hoefsldyla. Are you sure that TemplateWizard was bundled with MediaWiki? It's a fairly new extension. It should not be bundled with MediaWiki. A quick search on the bug tracker didn't show up any results.

Hoefsldyla (talkcontribs)

Hmm that is odd as I didn't install it, however maybe maybe it came with Visual Editor. Either way the same problem still applies.

NKohli (WMF) (talkcontribs)

@Hoefsldyla Can you share a screenshot of the wizard you are talking about? VisualEditor does not use TemplateWizard but has its own wizard to insert templates. I'll be able to help you more if you can tell me what you want to disable. :)

Hoefsldyla (talkcontribs)

@NKohli (WMF) Really? I thought they must be the same thing as they look identical and have identical functions. In that case maybe TemplateWizard isn't working at all? If I am editing a page in visual editor mode where should the button to using TemplateWizard be situated? Here are screenshots

Hoefsldyla (talkcontribs)

I have also noticed that when I have the TemplateWizard extension loaded my WikiEditor dissapears from source mode

NKohli (WMF) (talkcontribs)

Yup, what you see is VisualEditor's own Template insert wizard. TemplateWizard looks quite different, see screenshots here. The TemplateWizard we made only works with WikiEditor and does not work for VE. That's because VE had its own thing. I am not completely sure if/how to disable it (code probably somewhere here) but TemplateWizard won't work on VE, unfortunately. :(

Hoefsldyla (talkcontribs)
George Ho (talkcontribs)
197.218.92.212 (talkcontribs)

They would need to change the Extension:TemplateData specifications. It specifically requires that dates be output as the standard ISO format. This is necessary to ensure that the tools like visualeditor can change the value, if it has a weird or ambiguous format then that is downright impossible. For instance, other languages use different calendars.

Long term, they need to support different calendars as well as output formats. But that's going to be tricky, considering that even html tags like <time> don't support them, and editors wouldn't like typing a complicated <time dateformat=XXX >"YYYY-MM-DD"</time> format anyway.

George Ho (talkcontribs)

How about an option to manually type dates, similar to that of UploadWizard, i.e. the "Use" portion of UploadWizard?

197.218.82.255 (talkcontribs)

It wouldn't fix this issue. It needs a feature request to Templatedata to allow different date formats. An alternative would be changing the template to specify that parameter as plain text, that would allow adding it as plain text.

On English wikipedia it may be a slight annoyance, in non-latin based wikis it may add a completely unintelligible date if it doesn't use arabic numerals at all.

George Ho (talkcontribs)

I decided to add the "date" parameter(s) without using the TemplateWizard to fill them out. That way, I can fill them out manually.

For now, until the issue is fixed, or more date options are provided, I don't find the calendar date format feature either sustainable or reliable.

197.218.82.255 (talkcontribs)

As a temporary workaround they could add the same feature as visualeditor that always allows entering plaintext for any given parameter. That way even if someone enters the wrong templatedata for a template, it will still allow the user to enter stuff. Of course that is less of a problem for wikitext editors because they can always insert the whole template call without parameters, and manually enter everything.

This seems to be yet another disadvantage of not reusing code from VisualEditor, now they need to re-implement everything. On a positive note, if something useful is added to templatewizard that may create pressure for VE developers to add to it too.

George Ho (talkcontribs)
George Ho (talkcontribs)

I commented on the calendar (sub)feature not allowing inserting of just month and year without a day.

George Ho (talkcontribs)
Laurit301 (talkcontribs)
Reply to "Need options to change date formatting"

Doesn't seem to address specific issues

6
197.218.92.212 (talkcontribs)

Going by the screenshots and by the actual wishlist item, it seems obvious that some things were completely missed.

  1. No menu to filter types of templates (https://phabricator.wikimedia.org/T55590) - The wishlist seems to specifically ask for an infobox wizard and talks about newbies, but there is neither any way to filter only those infoboxes, quote templates, or anything else. This could be implemented by either fetching most used templates in a category or using wikidata to get them in non-english wikis, e.g. https://www.wikidata.org/wiki/Q19887878.
  2. Date type is not properly supported - It seems that the wizard either has a limited interpretation of the templatedata spec, or simply ignores it. The spec also allows the use of time in addition to dates. But this doesn't seem possible with this tool. Arguably, the templatedata spec should be improved to indicate the expected output format.
  3. Inability to select from a list of items (https://phabricator.wikimedia.org/T53375) - the wishlist item talks a lot about invalid structures. This doesn't address wrong template input, e.g choosing a country name from a dropdown.
NKohli (WMF) (talkcontribs)

Hello. Thanks for taking the time to reply! I will address your points below -

  1. When we started working on this project, we realized it could be useful for all kinds of templates and restricting it to just infoboxes seemed like a waste. You can still quite easily search for all infobox templates by using the search function. We thought about the idea for showing popular templates for new users but that is actually quite complex to compute, technically. We then settled on the idea of showing recently used templates for each user (https://phabricator.wikimedia.org/T194434) but we haven't implemented that yet.
  2. For this point, can you give me a specific example where you don't see date type supported correctly? We did test this feature but it seems like we missed some use cases.
  3. You are actually the first person to bring this to our attention as it was not mentioned in the wishlist proposal or any of the project page discussions I had with users. This seems like a very useful thing to have. I cannot commit to working on this currently as the team has several other projects to go through before the year end but we will definitely keep it on our list of things to do in the long-term.

Thank you so much.

197.218.81.214 (talkcontribs)

It is certainly useful to be able to insert all templates. But the request stressed newbies, and newbies don't often know what templates even exist. They might as well type random stuff in the search box, remember that wikis in different languages may have named them quite differently. It would only need to list some 10 most used templates within specific categories to give the user a hint. It certainly would not need to list the thousands of templates that wikis have. There's also a lot of free whitespace that could contain that.

The date parameter isn't supported properly because the widget being used only shows dates, not time. There was also a hint of it here:https://meta.wikimedia.org/wiki/Talk:Community_Tech/Template_wizard#Inserting_dates. So for example, it can only insert stuff like "2014-05-09" but never "2014-05-09T16:01:12Z". See (https://phabricator.wikimedia.org/T100206#2197740). Try pasting that longer date in the templatewizard date input and it will simply be discarded.

About point 3, maybe they thought it was obvious, but some users make mentions about template parameters being added incorrectly : "On frwiki too template editors ask bot maintainers to change parameters of infoboxes. Here it seems to want to take the problem at the root for page creations. with a tool to directly add the right syntax.".

Anyway, thanks for the explanations...

197.218.81.214 (talkcontribs)

Also, generally, it might be a good idea to pull in all templates currently on the page, and make it possible to insert them...

NKohli (WMF) (talkcontribs)

Sorry about the late reply. This got lost in my inbox. So one of the reasons it's hard to find "popular" templates is because generally the MOST transcluded templates are meta/banner templates. Which aren't meant to be used by themselves. But it's not trivial for the software to be able to recognize that. So the only workaround I see to this is for us to allow every wiki to configure what the list of popular templates would be for their wiki. This isn't exactly straightforward either and is likely to spark some wars on what templates are important enough to be shown in the list.

I do completely agree that giving a new user a completely empty screen is not a good experience.

About the dates, I will create a Phabricator to investigate this issue and see if we can find a solution for it. Thanks for raising this.

197.218.84.40 (talkcontribs)

So one of the reasons it's hard to find "popular" templates is because generally the MOST transcluded templates are meta/banner templates.

This was true. However, end-users have already solved that problem by A) categorizing such templates B) adding it to wikidata . For instance, if I wanted to know what are the most used templates that fit into neat types that are likely useful for the average user:

  1. Get list of most used templates Special:MostTranscludedPages
  2. Get specific categories of templates linked through wikidata (https://www.wikidata.org/w/index.php?search=&search=haswbstatement%3AP279%3DQ11266439&title=Special%3ASearch&go=Go)
  3. Fetch infoboxes, navigation boxes, and other lists from wikidata:
  4. Filter list #1 by lists fetched in #3 using interwiki links, and show about 10 infoboxes, and 10 navboxes, simply excluding anything that doesn't fit into selected categories.

Probably the most useful templates are utility templates, such as template:date, template:formatdate, quote, etc. Although they currently aren't classified properly in wikidata, this would be trivial for volunteers. This would also make it possible to warn users when they are attempting to insert a template that doesn't belong in a content namespace, e.g. documentation templates ( https://www.wikidata.org/wiki/Q4608595).

Alternatively, if it is deemed unfeasible, it might be possible to handle tasks https://phabricator.wikimedia.org/T165053 or https://phabricator.wikimedia.org/T166525 . Either the latter or the wikidata solution seems like it should have certainly been part of this project because it specifically asked for an infobox insert tool and it was mutated into something else (for good reasons) with an empty screen.

For the dates, it seems simple enough to use the date picker used in Special:ApiSandbox#action=query&format=json&list=recentchanges .

It might generally be a good idea to clarify the exact specifications and limitations of future wishlist requests before perusing them.

Reply to "Doesn't seem to address specific issues"
There are no older topics