Extension talk:Widgets

Zip method Fatal error: Uncaught Error: Class 'Smarty' not found in WidgetRenderer.php:24

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Followed the directions for installing via Zip method, after activating receive:

Fatal error: Uncaught Error: Class 'Smarty' not found in /home/username/sitename.com/extensions/Widgets/WidgetRenderer.php:24

Is there a chance these instructions need to be updated/changed?

No composer access on the host this is installed on

MediaWiki	1.35.0
PHP	7.4.12 (cgi-fcgi)
MySQL	5.7.28-log
ICU	57.1
Lua	5.1.5

TiltedCerebellum (talk) 06:03, 1 March 2021 (UTC)

Is this discussion for how to install smarty helpful? ☠MarkAHershberger☢(talk)☣ 16:09, 1 March 2021 (UTC)

Thanks, I tried a few different methods for smarty, and those didn't work with provided zip. Ended up doing the composer install for the friend's host account this was on and installing from git. With that we ended up with two other errors that suggest Widgets is not fully compatible with 1.35, ended up abandoning Widgets.

Project:Support desk/Flow/2020/09#h-Resolving_"ComposerInstalled.php"_error-2020-09-26T10:51:00.000Z

https://phabricator.wikimedia.org/T276023

https://phabricator.wikimedia.org/T276021

We weren't using it for that much, so we're just removing the stuff we did use it for until it's updated and whatever conflicts are sorted. TiltedCerebellum (talk) 20:40, 1 March 2021 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Update documentation?

After failing to get this extension to work using manual installation, I managed to do it using composer. I wondered why the former approach didn't work for me.

Previously we had to put the libs folder inside the smarty folder, but I now see, after using composer, that the contents of the libs folder are inside the smarty folder. Did something change? Should the docs for manual installation be updated? Cavila 11:16, 8 March 2021 (UTC)

Probably yes. I have not installed this extension manually in many years so I do not really know how this is done properly. I will add a note saying that the instructions may be out of date. [[kgh]] (talk) 19:22, 8 March 2021 (UTC)

Manual installation also failed for me and composer installation succeeded.

I had to update Composer to v2, though. MediaWiki-specific instructions here: Composer. 2601:18D:4981:5BF0:250A:1C13:AFB6:9DEB (talk) 23:40, 21 April 2021 (UTC)

Write error

I cannot figure out this write error. It randomly started doing this recently, and the widget I'm using was working as of last week.

I'm receiving the following error:

Error in widget iframe unable to write file

Widgets slash compiled_templates slash wrt609346e2956705_70999129 (since I was getting a damn spam error)

The directory is currently 775 permissions. I even reinstalled it from the base git and did the instructions needed for my version, 1.32. Any help would be appreicated. 192.69.180.130 (talk) 02:00, 6 May 2021 (UTC)

I'm receiving a similar error:

Unable to write file D:\home\site\wwwroot\extensions\Widgets\compiled_templates\d3288ecdd0052c9fea052081eede316e4be8e7d1_0.wiki.LearningPathMMD.php

How do I restore this page? MMDUser (talk) 20:26, 3 June 2021 (UTC)

Error: Class 'Smarty' not found

I got this error after updating my wiki recently. I tried to follow the steps under Installation from a .zip file, but I got a little confused by the wording.

So I installed the newest Widgest extension and then created a folder named 'smarty" (extensions/Widgets/smarty). Then I downloaded the newest Version of Smarty, unzipped it, and put the 'libs' folder in extensions/Widgets/smarty/libs.

But it didn't change anything, I still got the error message. What did I do wrong? 94.223.127.19 (talk) 15:47, 7 June 2021 (UTC)

Please try installing the extension via Git, since the method via unzipping Smarty manually is outdated.

If you can not use git or composer directly on your server, you can run the respective command locally and afterwards upload the whole folder. MGChecker (talk) 00:55, 8 June 2021 (UTC)

I am having the same error, but when I attempt to import from another wiki.

installed via git from github wikimedia/mediawiki-extensions-Widgets

I get the following:

[fae15bd5e378e271a99d65f5] /index.php?title=Special:Import&action=submit Error from line 24 of /frogdice/servers/com.thresholdrpg.wiki/extensions/mediawiki-extensions-Widgets/WidgetRenderer.php: Class 'Smarty' not found

@Gesslar Gesslar (talk) 05:45, 18 July 2021 (UTC)

As stated in the documentation at Extension:Widgets#Download, you need to run Composer afterwards. This can also be done at your local machine before syncing with the server. MGChecker (talk) 12:48, 18 July 2021 (UTC)

Unable to load template 'wiki:Iframe'

hi !

i want to use in lokal wiki the Widget#Iframe.

The folder ..\extensions\Widgets\compiled_templates has full permisson to IIS_IUSRS and the .htaccess file, include this folder (source: deny from all) i rename.

the template .../index.php?title=Vorlage:Wiki:Iframe is create with

<includeonly><iframe src="<!--{$url|validate:url}-->" style="border: <!--{$border|escape:html|default:0}-->" width="<!--{$width|escape:html|default:400}-->" height="<!--{$height|escape:html|default:300}-->"></iframe></includeonly>

then i copy the example into side - but now i get the misstake:

Unable to load template 'wiki:Iframe'

did someone could help?

regards Jan

os	Windows Server 2016
mediawiki	1.36.1
php	php-7.4.20-nts-Win32-vc15-x64
mysql	mysql-5.7.12-winx64

JanTappenbeck (talk) 12:36, 8 July 2021 (UTC)

Please review the widget description carefully, section 'Copy to your site' www.mediawikiwidgets.org/Widget:Iframe

To resolve the issue, you need to create Widget:Iframe page like this:

.../index.php?title=Widget:Iframe

and copy the 'full source code' to the page. Aliaksei.S (talk) 19:02, 8 February 2023 (UTC)

Forbidden?

After trying to up any widget in i get "forbidden". I changed the dir to 777 and still no dice. Specifically iframe and form code gets me the forbidden. 2604:2D80:E507:3000:A5BA:527E:A9AE:8B43 (talk) 07:49, 30 July 2021 (UTC)

Note that a lot of websites nowadays disallow iframing. This is probably where your "forbidden" comes from. Apart from that, I do not know. [[kgh]] (talk) 14:26, 30 July 2021 (UTC)

Captcha on mediawikiwidgets.org not working

Having issues creating a new account on mediawikiwidgets.org because the time calculation captcha says my answers are wrong. I have tried every combination of syntax I can think of. Any ideas how to get it to work? 206.214.228.200 (talk) 20:55, 7 September 2021 (UTC)

Try e.g. 10:22. Probably you added the brackets [] which should not be done. [[kgh]] (talk) 05:49, 8 September 2021 (UTC)

How to render mediawiki syntax before sending to a widget

Hi, making a flashcard system on my wiki using SMW (flashcards are defined in pages and available in portals), the display is made with tabs with the input-radio trick (see for example : https://www.youtube.com/watch?v=oLqdy95LZSw ). So the html structure and css are in Widget:Flashcard.

But questions and answers may have links to pages (definitions...), images... in wikicode. And they are not rendered after being sent to the widget witch displays raw code.

Is it a way to render them ? Thanks FrViPofm (talk) 00:52, 14 March 2022 (UTC)

I would also like to know if it is possible to send wikicode through the extension to be rendered. It would open up much more flexibility in my use case. Chaeidras (talk) 23:03, 24 January 2024 (UTC)

Widgets.php was not found!

I upgraded from 1.34 to 1.38 and got Widgets error, so I used your manual for "mediawiki version 1.31 and later', it seems everything is done fine and I get no error, but Widgets.php is not under /Widgets folder. Why this file is missing from your git? I copied Widgets.php from my older 1.34 version to this new folder, but it seems there are still problems. Farvardyn (talk) 11:28, 2 July 2022 (UTC)

Did you migrate to wfLoadExtension( 'Widgets' );? See here. [[kgh]] (talk) 19:58, 2 July 2022 (UTC)

What triggers widgets to get cached/compiled?

Our wikis have a lot of widgets, some of which I'm seeing get recompiled into the compiled_templates directories many times per minute, even sometimes multiple times in a second. In that particular example, the only thing changing in the compiled code is the JS function name that is randomly generated by the call to PHP uniqid('', true). Is this probably something with how our Widgets are written, or perhaps about how they are used within templates and themselves use templates (it gets messy)? FWIW a while back I opened a Phabricator task on this. Justin C Lloyd (talk) 15:45, 19 July 2022 (UTC)

Any thoughts on my question? Justin C Lloyd (talk) 15:23, 25 August 2022 (UTC)

I would like to understand this better too for similar reasons. Revansx (talk) 13:28, 8 November 2023 (UTC)

Some links I found to be very helpful:

• Extension:Widgets/et#Troubleshooting
• https://www.semantic-mediawiki.org/wiki/How_to_write_a_JavaScript_to_display_data_in_a_Semantic_MediaWiki#How_to_clear_precompiled_templates_from_database.2Fcache Revansx (talk) 13:51, 8 November 2023 (UTC)

it looks like the extension is currently using ParserAfterTidy hook to decide this, which is probably not the most correct option. Something LinksUpdate related would be better (although have to be careful about asyncness of linksupdate) Bawolff (talk) 18:29, 8 November 2023 (UTC)

Widgets loaded before mw.hook is available

I ported some functional widgets from a different wiki running MW 1.31 and Widgets v1.3.1 to mine, which is running MW 1.38 and Widgets v1.4.1. However, some of these ported widgets are not working. In particular, I see errors about mw.hook and mw.loader.using not being a function.

I tried to log them in the console as the widget loads, mw shows up as an object with all the expected properties, but mw.hook and mw.loader.using are both undefined.

A simple script to reproduce the issue is as follows:

window.RLQ.push(async () => {
    console.log(mw); // this shows up as a regular object
    console.log(mw.loader.using); // this shows up as undefined
    console.log(mw.hook); // this shows up as undefined
});

I typed the names of all these packages in the console after the web page loaded. Everything shows up normally, implying that the widget is perhaps loaded before core mw packages are available.

I feel like I'm missing something very obvious, but I don't know much about javascript and cannot find any migration guides/tutorials that may explain this phenomenon. Everything I saw suggested that mw.hook and mw.loader.using are loaded before everything else and that I don't need to do anything special to use them. Any help is appreciated. Thank you! PetraMagna (talk) 02:14, 22 October 2022 (UTC)

Hi, I honestly don't know but you're relying on a number of ResourceLoader's core modules (mw.loader.using, etc.). As far as I know, the Widgets extension has no support for them out of the box, so I wonder how that issue was solved on the older wiki.

One hack you could try, though it really is a stab in the dark, is to edit extension.json and load the required modules as dependencies, which may or may not also include jQuery.

Another route you might consider is move your JavaScript to MediaWiki:Common.js instead, which comes with built-in support for ResourceLoader although you will probably have to rewrite some of your code (or have it rewritten). Cavila 08:57, 22 October 2022 (UTC)

@Cavila Thanks for the reply! I saw in another thread called "JQuery access" that upgrading from MW 1.31 to 1.34 breaks jquery, so the issues with mw.hook and mw.loader.using might have a similar cause.

I thought extension.json configures the dependencies of an extension, so it shouldn't affect the order in which js scripts are loaded? PetraMagna (talk) 20:54, 22 October 2022 (UTC)

relative URL for a widget

I am using the widget video given in the list of already designed widgets

but this one use an absolute url

and i want something like src= instead of URL=

because videos are locales to my wiki and not external

Could you please give me the syntax to change this

best regards

Because in my old version of mediawiki i used HTML5Video extension and now with version 1.39 of mediawiki it doesn't work Chantoune (talk) 21:35, 8 February 2023 (UTC)

I would think that the Video widget already makes use of src internally. I'm not sure what you by mean "videos are locales to my wiki", but there's a couple of things you could do.

• You could rewrite the widget to make use of $_SERVER['SERVER_NAME' ]
• You could rewrite the widget to include a hard-coded reference to the domain.

Or before passing stuff to the widget:

• You could use prefix your relative urls with Help:Magic words: e.g. https:{{SERVER}}/
• If a video is uploaded to the wiki, you can retrieve its url by using filepath

Hope that helps. Cavila 13:29, 9 February 2023 (UTC)

502 Bad Gateway

I'm getting the 502 Bad Gateway error when I save a page in my wiki that has the Widget template called, how do I solve this problem? 2804:14C:6584:4F38:EC78:D90E:A50A:85DE (talk) 17:10, 22 May 2023 (UTC)

Class "FlaggedArticle" not found

I use a Windows laptop with XAMPP. After I installed this extension, I enabled FlaggedRevs. However, when I then tried to save a page that transcluded a widget, I got this Internal error:

[67a635e5d3c566814dbcfeab] /wiki/Main_Page Error: Class "FlaggedArticle" not found

Backtrace:
from C:\xampp\htdocs\w\extensions\Widgets\SmartyResourceWiki.php(34)
#0 C:\xampp\htdocs\w\extensions\Widgets\vendor\smarty\smarty\libs\sysplugins\smarty_resource_custom.php(75): SmartyResourceWiki->fetch(string, NULL, NULL)
#1 C:\xampp\htdocs\w\extensions\Widgets\vendor\smarty\smarty\libs\sysplugins\smarty_template_source.php(211): Smarty_Resource_Custom->getContent(Smarty_Template_Source)
(...)

I don't think I have to post the entire log, but you get the idea. 😉

I can edit the Widget: page just fine. Approving and rejecting revisions also works. But when I try to transclude the widget, it crashes. The problem disappears when I turn FlaggedRevs off. Manifestation (talk) 14:19, 31 July 2023 (UTC)

Sorry about that - this turned out to be a bug from 2012! I guess Widgets and FlaggedRevs don't get used much together. Anyway, I just checked in what I believe is a fix. Yaron Koren (talk) 17:00, 31 July 2023 (UTC)

You did? That's great! Manifestation (talk) 19:14, 31 July 2023 (UTC)

@Yaron Koren: And? Did you find the bug? Manifestation (talk) 13:18, 31 August 2023 (UTC)

I think so... Yaron Koren (talk) 13:26, 31 August 2023 (UTC)

This is really weird. I updated your extension using Composer. But apparently something went wrong. Composer only updated certain files, but not all. 😕

I then tried downloading the entire extension manually from the ExtensionDistributor. When I went there, it said "1.40 (latest stable MediaWiki)".

I was still on 1.39, so I upgraded to 1.40. As a result, my entire wiki collapsed. 1.40 doesn't appear to support Flagged Revisions at all! I posted about it here and here. Manifestation (talk) 20:12, 31 August 2023 (UTC)

@Yaron Koren: Sorry for the confusion. I fixed the above issue.

I now have the latest stable MW version. I have the latest version of FlaggedRevs. I downloaded the latest version of Widgets (for MW 1.40) via Special:ExtensionDistributor. But it still gives me the exact same error. Manifestation (talk) 07:56, 1 September 2023 (UTC)

@Yaron Koren: Ok, scratch that. I now downloaded the alpha version, i.e. the master version, i.e. the development version. Now it does work. Why is everything so complicated! 😩 Manifestation (talk) 08:17, 1 September 2023 (UTC)

It's not quite as complicated as you may have thought - you only had to switch to the latest version of the Widgets extension, not upgrade MediaWiki or FlaggedRevs. But I'm glad everything works now. Yaron Koren (talk) 20:33, 1 September 2023 (UTC)

@Yaron Koren: Yeah I know, and I apologize for my convoluted response.

Do you know when the alpha/development/master version will become the stable version? Manifestation (talk) 16:31, 2 September 2023 (UTC)

Is this extension compatible with PHP 8.2?

I am running MediaWiki 1.39.5 and recently switched to PHP 8.2.x (8.2.12 currently).

We have a Widget test page that loads sample Google presentation, Google document and Google Spreadsheet widgets.

All appear okay. However in the error_log we get:

[07-Nov-2023 23:12:33 UTC] PHP Warning: Undefined array key "width" in w/extensions/Widgets/compiled_templates/ba811dbfd89414d874993a209b5e2eb71ad14d2d_0.wiki.GooglePresentation.php on line 24 [07-Nov-2023 23:12:33 UTC] PHP Warning: Attempt to read property "value" on null in w/extensions/Widgets/compiled_templates/ba811dbfd89414d874993a209b5e2eb71ad14d2d_0.wiki.GooglePresentation.php on line 24 [07-Nov-2023 23:12:33 UTC] PHP Warning: Undefined array key "height" in w/extensions/Widgets/compiled_templates/ba811dbfd89414d874993a209b5e2eb71ad14d2d_0.wiki.GooglePresentation.php on line 25 [07-Nov-2023 23:12:33 UTC] PHP Warning: Attempt to read property "value" on null in w/extensions/Widgets/compiled_templates/ba811dbfd89414d874993a209b5e2eb71ad14d2d_0.wiki.GooglePresentation.php on line 25

I have gone through the individual Widget pages and purged the page so that the compiled templates are refreshed.

These seem to be indicative of something not compatible with PHP 8.2 changes or is some step required to recompile the template(s)? Peculiar Investor (talk) 13:10, 8 November 2023 (UTC)

I doubt it. Anyhow, MediaWiki is not compatible with PHP 8.2 either. Did the widget work with earlier versions of PHP, MediaWiki, and Widgets? [[kgh]] (talk) 16:53, 8 November 2023 (UTC)

According to Compatibility#PHP MediaWiki support for PHP 8.0 and above started with 1.39.0. The recent 1.39.5 release announcement makes mention that "Various patches aimed at PHP 8.0, 8.1, and 8.2 support have been back-ported."

The Widget's work as far as the end-user knows. The PHP Warnings in the error_log are something I would expect the Extension:Widgets developers to address. Peculiar Investor (talk) 18:00, 8 November 2023 (UTC)

I don't know what your widget looks like and how it is used, so this is a wild guess, but the error messages read like the values for those parameters have not been specified. If those values were omitted, did you at least provide defaults or provided an 'if' condition to prevent such errors from occurring? Cavila 08:20, 9 November 2023 (UTC)

Returning to this... I had the same issue, recently. At some point, the Widget extension has become less forgiving when you do not set a value for a parameter defined in the widget, which will trigger the warning you encountered. Like I mentioned at the time, you can use an 'if' condition to get around this[1], but what I didn't know is that defaults (https://www.smarty.net/docs/en/language.modifier.default.tpl) no longer seem to work and will emit same error message. I used the REL1.39 branch of the extension, which installed version 1.4.2, and I am using PHP 8.0.

This no longer works:

<!--{$myparam|escape:'quotes'|default:'Nothing to see here'}

It looks like the issue began with the inclusion of modifier.allowedvalues.php, which does not check for defaults.

[1] For anyone looking for am example, this solution checks if the param is set at all and if it is, if the value is not 'empty', similar to how you would wiki templates

<!--{if ( isset($myparam) && $myparam!="" )}-->
<!--{$myparam|escape:'quotes'}-->
<!--{else}-->
Nothing to see here [optional default]
<!--{/if}-->

Cavila 10:10, 28 February 2024 (UTC)

MediaWiki Search does not work on Widgets!

I am running MediaWiki 1.39.5. We have a Widget that loads projects information from OpenAIRE and make it available to all pages within our mediawiki setup. Widgets work perfectly fine. What we want is to do search over these loaded project information via MediaWiki search. However, The search provided by MediaWiki does not find these loaded information. We have tried advanced search but nothing happened. How can i search this data inside mediawiki? Do i need separate search function for this kind of data? 2A02:8388:15BF:C180:E8AB:38E6:17F1:733B (talk) 14:49, 21 March 2024 (UTC)

MediaWiki search only has the data available in the wiki code of each page. Widgets load content from external sources on the browser, not on the server, and that's why MediaWiki search can't find it Ciencia Al Poder (talk) 10:29, 22 March 2024 (UTC)

Ahaan! so, what is the best way to perform search on this kind of data in mediawiki? 2A02:8388:15BF:C180:E8AB:38E6:17F1:733B (talk) 21:02, 22 March 2024 (UTC)

There's no way to do that. A bot or some other automatic process would need to fetch the data and store it on the wiki page directly instead of relying on external requests (widgets) Ciencia Al Poder (talk) 16:59, 24 March 2024 (UTC)

How to pass an array into widget

Hi there,

I noticed in the doc it says:

"If you use the same parameter multiple times, the widget will get an array of values. You can use foreach to go through the array."

That's nice for manually specifying values. But actually passing a list of values into a widget gets more complicated and i have not yet been successful at transforming

one,two,three

into

|arrayValue=one|arrayValue=two|arrayValue=three

In order to then feed into the widget and indeed get a working array that you can iterate through.

I've tried arraymap[template] without luck. The pipe gets parsed too late.

Any thoughts, ideas? Thanks! Jeremi Plazas (talk) 12:56, 29 April 2024 (UTC)

Twitter/X Widget ?

Hi,

For example https://publish.twitter.com/?query=https%3A%2F%2Ftwitter.com%2FMichael86084836%2Fstatus%2F1798253963143528714&widget=Tweet

However the embed code includes the tweet text an is not drawing it from an api. Is there a way to make a widget using this code ? Michael Z Freeman (talk) 12:11, 5 June 2024 (UTC)

Amazingly, it looks like there's no standard widget yet for displaying a tweet, er, X post. (I think that text is there just to display something before the tweet finishes loading, by the way - the API is being accessed.) You could create the widget yourself, potentially... Yaron Koren (talk) 14:09, 5 June 2024 (UTC)

"I think that text is there just to display something before the tweet finishes loading, by the way - the API is being accessed."

Ah, really ? Right. I’ll go back to trying this again.

So actually consulting the X API using https://publish.twitter.com/oembed?url=https://twitter.com/Michael86084836/status/1798253963143528714 gives ...

{"url":"https:\/\/twitter.com\/Michael86084836\/status\/1798253963143528714","author_name":"Michael Freeman","author_url":"https:\/\/twitter.com\/Michael86084836","html":"\u003Cblockquote class=\"twitter-tweet\"\u003E\u003Cp lang=\"en\" dir=\"ltr\"\u003E“We are awake to their woke"\u003Ca href=\"https:\/\/t.co\/5dRMkPd32a\"\u003Ehttps:\/\/t.co\/5dRMkPd32a\u003C\/a\u003E\u003C\/p\u003E— Michael Freeman (@Michael86084836) \u003Ca href=\"https:\/\/twitter.com\/Michael86084836\/status\/1798253963143528714?ref_src=twsrc%5Etfw\"\u003EJune 5, 2024\u003C\/a\u003E\u003C\/blockquote\u003E\n\u003Cscript async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"\u003E\u003C\/script\u003E\n\n","width":550,"height":null,"type":"rich","cache_age":"3153600000","provider_name":"Twitter","provider_url":"https:\/\/twitter.com","version":"1.0"}

Can I parse this, I think it’s JSON ? Does anyone know a widget example ? Michael Z Freeman (talk) 16:36, 5 June 2024 (UTC)

Why parse it - why not just create a widget that displays the necessary HTML? Yaron Koren (talk) 17:16, 5 June 2024 (UTC)

Sorry, having real problems getting started here. Can you give me a few clues as to what I need to look at ? Michael Z Freeman (talk) 09:36, 14 June 2024 (UTC)

Could I filter that X response with something live "regex_replace:"#^(?!(https?:)?//).*#I":’'” ? That’s taken from the iFrame widget. Michael Z Freeman (talk) 17:35, 27 June 2024 (UTC)

Sorry for the delay. Actually, there is a Tweet widget - and it seems to still work fine, even though it was pre-name change. Have you tried it? Yaron Koren (talk) 19:33, 28 June 2024 (UTC)

實驗失敗中

• 傳入參數使用wiki的語法時，無法正確轉換，會變成文字直接輸出？無解？
• widget:Infobox

<includeonly>
<table class="infobox" cellspacing="5" style="width: 450px; font-size: 90%; text-align: left;"><tbody>

<tr><td colspan="2" style="text-align: center; font-size: 130%; font-weight: bold;"><!--{$name|default:""}--></td></tr>
<tr><td colspan="2" style="text-align: center;"><!--{$logo|default:""}--></td></tr>

<!--{if $screenshot neq ""}-->
<tr><td colspan="2" style="text-align: center;"><!--{$screenshot|default:""}--><br /><!--{$caption|default:""}--></td></tr>
<!--{/if}-->

<!--{assign var="i" value=1}-->
<!--{while $i<=30}-->
<!--{assign var="label" value=$<!--{"label$i"}-->}-->
<!--{assign var="data" value=$<!--{"data$i"}-->}-->
<!--{if ($data|default:"") neq ""}-->
<tr><td><!--{$label|default:""}--></td><td><!--{$data|default:""}--></td></tr>
<!--{/if}-->
<!--{assign var="i" value=$i+1}-->
<!--{/while}-->

</tbody></table>
</includeonly>

• Template:Infobox software2

{{#widget:Infobox
|name = {{{name}}}
|logo = {{{logo|}}}
|screenshot = {{{screenshot|}}}
|caption = {{{caption|}}}
| label1 = 其他名稱
| data1 = {{{other_names|}}}
| label2 = 原作者
| data2 = {{{author|}}}
| label3 = 開發者
| data3 = {{{developer|}}}
| label4 = 首次發佈
| data4 = {{{released|}}}
| label5 = {{#if:{{{discontinued|}}}|最終版本|當前版本}}
| data5 = {{{latest release|}}}
| label6 = 原始程式
| data6 = {{{repo|}}}
| label7 = 程式語言
| data7 = {{{programming language|}}}
| label8 = 中間件
| data8 = {{{middleware|}}}
| label9 = 引擎
| data9 = {{{engines|}}}
| label10 = 作業系統
| data10 = {{{operating system|{{{operating_system|}}}}}}
| label11 = 系统平台
| data11 = {{{platform|}}}
| label12 = 内置於
| data12 = {{{included with|{{{included_with|}}}}}}
| label13 = 取代
| data13 = {{{replaces|}}}
| label14 = 由…取代
| data14 = {{{replaced_by|}}}
| label15 = 服務名稱
| data15 = {{{service_name|}}}
| label16 = 文件大小
| data16 = {{{size|}}}
| label17 = 標準
| data17 = {{{standard|}}}
| label18 = 語言
| data18 = {{#if:{{{language count|}}}|{{{language count}}}種語言|{{{language|}}}}}{{{language footnote|}}}
| data19 = {{#if:{{{language count|}}}|{{#if:{{{language|}}}|{{hidden begin|toggle=left|title=语言列表|titlestyle=background-color: transparent;}}{{{language|}}}{{hidden end}}}}}}
| label20 = 類型
| data20 = {{{genre|}}}
| label21 = 授權方式
| data21 = {{{license|}}}
| label22 = 網站
| data22 = {{{website|}}}
| data23    = {{{嵌入插座|{{{embedded|{{{module|}}}}}}}}}
| label24 = 數據截至
| data24 = {{{AsOf|}}}
}}

• Test

{{Infobox Software2
| name = 7-Zip
| developer = Igor Pavlov
| released = {{Start date and age|1999|7|19|df=yes}}
| latest release version = 24.07
| latest release date    = {{start date and age|2024|06|19}}
| programming language = [[組合語言]]、[[C]]、[[C++]]
| operating system = [[Windows]]/[[ReactOS]], [[BSD]], [[macOS]], [[Linux]]
| language count = 89
| genre = 檔案壓縮
| license = https://7-zip.org/license.txt
| website = https://7-zip.org
}}

-2001:B011:300D:10F3:42D5:9A1:DC5F:86BA 12:34, 11 August 2024 (UTC)

Extension update since Miraheze "2020-12-23 Security Disclosure"?

I guess that the extension has been updated since https://meta.miraheze.org/wiki/2020-12-23_Security_Disclosure - has it, and which version should be used on a MW1.39 wiki? Thanks. Jonathan3 (talk) 20:16, 24 April 2025 (UTC)

It's had many updates since then, yes. You should use the latest version of Widgets, which still works with MW 1.39. Yaron Koren (talk) 20:58, 24 April 2025 (UTC)