Last modified: 2010-05-15 15:50:57 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10904 - addHtml in Templates
addHtml in Templates
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-08-13 09:25 UTC by GBenemy
Modified: 2010-05-15 15:50 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description GBenemy 2007-08-13 09:25:50 UTC
Article X has fully-functional html implemented into it through the <addhtml> </addhtml> tag. 
This html wants to be used on multiple pages, without having to type out the html each time. On Template:X The html (along with the <addhtml> tags) have been put into it. Giving the result of:

"unauthorized usage of addHtml extension."
Comment 1 Rob Church 2007-08-13 16:21:11 UTC
Please contact the author of the broken extension.
Comment 2 GBenemy 2007-08-13 23:17:27 UTC
(In reply to comment #1)
> Please contact the author of the broken extension.

>>I have no idea what you're talking about. I added the template. I copied and pasted the html EXACTLY as it appeared in the article, where it works fine. It says the usage of the tag was unauthorised. Maybe I have to add something to LocalSettings.php enabling usage of the tag within templates?
Comment 3 Rob Church 2007-08-13 23:43:44 UTC
<addhtml> is not a core tag. It therefore follows that it comes from an extension. Since this is not an extension we maintain, I don't know about it, and therefore, I suggested contacting the author for support.

Note You need to log in before you can comment on or make changes to this bug.