Last modified: 2012-12-19 11:33:24 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 7590 - CategoryTree does not work properly when used in [[MediaWiki:Sitenotice]]
CategoryTree does not work properly when used in [[MediaWiki:Sitenotice]]
Product: MediaWiki extensions
Classification: Unclassified
CategoryTree (Other open bugs)
PC Linux
: Lowest enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-10-15 19:50 UTC by Manuel Schneider
Modified: 2012-12-19 11:33 UTC (History)
1 user (show)

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


Description Manuel Schneider 2006-10-15 19:50:34 UTC
* MediaWiki v1.8.2
* CategoryTree SVN version from 2006-10-15

When using this extension in MediaWiki:Sitenotice the box does show up, but is not usable. Clicking on [+] does 

When including the <category> tag additionally into another page it works - also in the box shown from 

Steps to reproduce:
1. Put <category>/some category/</category> into [[MediaWiki:Sitenotice]].
2. Box should be shown on all pages, but is infunctional.
3. Put the <category>/some category/</category> on any other page or visit [[MediaWiki:Sitenotice]] - two boxes 
should be shown.
4. Both boxes will work.
5. Go to another page with box only included from [[MediaWiki:Sitenotice]] - box doesn't work.
Comment 1 Daniel Kinzler 2006-11-22 13:19:08 UTC
Please look for any JavaScript errors you are getting and report them here (some
browsers do not report them per default, you have to look for them in some log
and/or enable reporting).

I expect that the probelm is that the tag does not cause the required JavaScript
code to be included, when it is in a system message. System messages are
special, using extensions in system messages is generally problematic.

I can't think of a good reason to use CategoryTree in the site notice... please
describe why you want that, perhaps I can find a better way to accomplish that goal.
Comment 2 Javier Valcarce 2007-04-01 15:23:40 UTC
Hi. I have the same problem. I solved it putting by hand the javascript code
into my skin. Ugly, but is the only way I think. 

<script type="text/javascript"
<script type="text/javascript"> 
   var categoryTreeCollapseMsg = "collapse"; 
   var categoryTreeExpandMsg = "expand"; 
   var categoryTreeLoadMsg = "load"; 
   var categoryTreeLoadingMsg = "loading"; 
   var categoryTreeNothingFoundMsg = "Lo sentimos, no se ha encontrado nada"; 
   var categoryTreeNoSubcategoriesMsg = "sin subcategorías."; 
   var categoryTreeNoPagesMsg = "sin artículos ni subcategorías."; 

Comment 3 Javier Valcarce 2007-04-01 15:32:41 UTC
>I can't think of a good reason to use CategoryTree in the site notice... please
>describe why you want that, perhaps I can find a better way to accomplish that

I want a CategoryTree menu into a div container in my own skin so I used
$this->html('sitenotice') variable to achieve this goal. Does you know better
way to accomplish that goal? Thanks.
Comment 4 Daniel Kinzler 2007-09-13 11:33:57 UTC
You can get this to work using a relatively simple hack: [[Extension:CategoryTree#Using_CategoryTree_in_the_Sidebar]]

This should probably be come a propert configuration option in the future, so closing this as "LATER".
Comment 5 Andre Klapper 2012-12-19 11:28:11 UTC
[Removing RESOLVED LATER as discussed in . Reopening and setting priority to "Lowest". For future reference, please use either RESOLVED WONTFIX (for issues that will not be fixed), or simply set lowest priority. Thanks a lot!]

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