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.
Extension talk:Widgets
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.
Did you migrate to wfLoadExtension( 'Widgets' );? See here.
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
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?
Try e.g. 10:22. Probably you added the brackets [] which should not be done.
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.
Note that a lot of websites nowadays disallow iframing. This is probably where your "forbidden" comes from. Apart from that, I do not know.
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?
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.
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
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.
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 |
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.
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?
Hi, when I use the Google Presentation widget I only get a white plane in the place where the presentation should be. It doesn't say that the document doesn't exist (which it does when I change the docid) so apparently that is not the problem. But what is, I don't know!
I have the same problem. It appears to be something wrong with new presentations. Old presentations with short ids can be displayed.
Here is a hack: One can disable new presentation editor and make older format presentations as described here: http://support.google.com/docs/bin/answer.py?hl=en&answer=1685857
@AdSvS Hi, was there ever a solution or alternative to displaying presentations? thanks
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?
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.
Manual installation also failed for me and composer installation succeeded.
I had to update Composer to v2, though. MediaWiki-specific instructions here: Composer.