MediaWiki - User contributions [en]

Project:Sandbox

2019-01-28T16:31:08Z

213.61.254.68: ölöl

{{Please leave this line alone and write below (this is the coloured heading)}}

=== '''Testing MediaWiki, dont mind me!''' ===

This is easy, kinda.
test

<br />

Topic:Usxxwg6xqqxfdp2q

2019-01-28T08:57:49Z

213.61.254.68 (talk) commented on "Which Version of Semantic with which Version of MediaWiki" (My problem was in the file composer.local.json the line: "extra": { "merge-plugin": { "inclu...)

Extension talk:Semantic MediaWiki/Archive 2/Flow export

2019-01-28T08:57:49Z

213.61.254.68: /* Which Version of Semantic with which Version of MediaWiki */ Added reply

{{flow imported revision}}
'''<big><span style="color: orange">The best way for getting support for Semantic MediaWiki is to post to its user mailing list.</span></big>''' Comments made below are not very well monitored by the developers. There are various options for making yourself heard:

* If you have a usage question, please post them to the [https://sourceforge.net/projects/semediawiki/lists/semediawiki-user SMW support mailing lists] ([https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/ archives]).
* If you found a bug or want to propose a new feature, please file it at [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues GitHub]. Bugs and requests are regularly considered by core developers and have a great impact on the future development of SMW.
* If you want to contribute to the development, please contact the development community at the [https://sourceforge.net/projects/semediawiki/lists/semediawiki-devel SMW developers' mailing list] ([https://sourceforge.net/p/semediawiki/mailman/semediawiki-devel/ archives]).

When asking for help or describing bugs, '''do not forget''' to provide necessary details about your configuration, version details for all relevant components, information about other extensions that are used, and, if possible, a URL where the problem can be seen. See the help page on '''[[semantic-mw:Help:Reporting bugs|reporting bugs]]''' for detailed information.

The below talk page is most useful for comments regarding the wiki page, but of course you may do as you like (it's a wiki, after all).

→ [[Extension talk:Semantic MediaWiki/Archive|previous talk on this page]]

== PHP Fatal error: Class 'SiteConfiguration' not found in updateArticleCount.php on line 59 ==

Moved to wiki support instead of SMW support. Sorry. [[Special:Contributions/85.80.205.112|85.80.205.112]] 11:42, 2 March 2013 (UTC)

== Syntax highlight lang for documenting Semantic MediaWiki code ==

This seems to work quite well:
<nowiki><syntaxhighlight lang="bibtex"></nowiki>
[[Extension_talk:SyntaxHighlight_GeSHi#lang_for_Mediwiki_Code_.3F|Thanks]] to [[User:Technical_13|Technical 13]] [[User:Daniel K. Schneider|Daniel K. Schneider]] ([[User talk:Daniel K. Schneider|talk]]) 11:15, 28 June 2013 (UTC)

== SMW "future-safe"? ==

Hello,

your extension SMW is great! I would like to integrate it into our private wiki.

Is the use "future-safe"?
What are your future plans? Will developing go further when new releases of mediawiki appear ... e.g. the next 10 years?
Or would you recommend to use the extension Dynamic Pagelist instead?

Regards
Janis --[[Special:Contributions/87.186.50.77|87.186.50.77]] 07:46, 2 October 2013 (UTC)
:Hi Janis,
:SMW is probably one of my main reasons for sticking with MediaWiki. If you look at the website (http://semantic-mediawiki.org) and the mailing list (https://lists.sourceforge.net/lists/listinfo/semediawiki-user), you'll find that the extension as well as related extensions like SF are actively supported and enjoy a lively user community - quite contrary I'd say to the bulk of MW extensions that you'll find here, so I know where your question is coming from. No one can tell where we will be ten years from now, but I don't think you'll regret it. If you have any questions regarding the future direction of SMW, the mailing list would be the place to ask. [[User:Cavila|Cavila]] <span style="font-size:65%;">(MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2}</span> 08:37, 2 October 2013 (UTC)

== Upgrading SMW old version ==

Hi,
My production wiki is on ver 1.15.1 and it has smw 1.0.1 installed. I am trying to test an upgrade in the dev environment which is mw 1.19.9 with smw 1.8. The extension has installed successfully and is showing up properly in special:version. But the pages using it are breaking. I was wondering about how i should go about upgrading smw to 1.8. Are the old SMW_settings and SMW_Globalsettings compatible with the latest install? Should the upgrade be done in steps? I was reading and I found that there have been several schema changes. Any help is greatly appreciated

Thanks in advance.

Arnab [[Special:Contributions/81.245.110.27|81.245.110.27]] 17:54, 22 December 2013 (UTC)
:Oh, this is quite an archaic installation. Hmm, did you completely [[semantic-mw:Help:Repairing_SMW's_data|rebuild your store and data]] (or [[semantic-mw:Help:Installation 1.8.0#Upgrading existing installations|upgrading to 1.8.x]])? Perhaps you are still using the "<code>:=</code>" syntax for annotating properties. I think this does not longer work in recent versions. The best way to ask questions about SMW is to use the [[semantic-mw:Semantic MediaWiki mailing lists]]. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:19, 31 December 2013 (UTC)
::Hi,
::<code> This is how I worked it out. I went with upgrading from 1.0.1 to 1.1 to 1.2 to 1.3 to 1.4 to 1.5 to 1.6 to 1.7.1.</code>
::So i did the upgrade in steps. I couldn't figure out a way of going directly from 1.0.1 to 1.8. It was lengthy but it worked out properly.
::Arnab [[Special:Contributions/81.247.85.62|81.247.85.62]] 14:22, 5 January 2014 (UTC)
:::Glad it worked out. :) [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:49, 5 January 2014 (UTC)

== What are the "issues" that break a wiki when you remove the extension? ==

Extension has been installed but never used and trying to reduce overhead by removing several unused extensions. If the extension wasn't used, is SMW_setup.php --delete enough? [[User:Skunark|Skunark]] ([[User talk:Skunark|talk]]) 02:40, 30 December 2013 (UTC)
:This should be enough. You can verify in your database if the SMW related tables are still there. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:11, 31 December 2013 (UTC)

== Logo ==

Hi,
Is there a way to control the enabling and disabling of the SMW logo at the right bottom of the page.

Arnab [[Special:Contributions/81.247.85.62|81.247.85.62]] 14:40, 5 January 2014 (UTC)
:The best way to ask questions about SMW is to use the [[semantic-mw:Semantic MediaWiki mailing lists]]. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:48, 5 January 2014 (UTC)

== Updated Semantic Mediawiki but cant run update.php, Err. SEMANTIC MEDIAWIKI MUST BE INSTALLED TO RUN SEMANTIC FORMS ==

I used composer to update my semantic mediawiki version. The installation ran successfully but I cant update.php. My current SMW version in 1.8.05. Running update gives me an error that says SEMANTIC MEDIAWIKI MUST BE INSTALLED TO RUN SEMANTIC FORMS. I did try placing the enableSemantics() call at the end of LocalSettings.php file. Please help. Thanks in advance [[User:Cmm9888|Cmm9888]] ([[User talk:Cmm9888|talk]]) 08:23, 25 August 2014 (UTC)
:Try uninstalling Semantic Forms (and any other SMW-requiring extensions) before doing the update. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:56, 28 August 2014 (UTC)

== Reunion instead of intersection ==

Hey guys,
Really would appreciate any help!
If I write <nowiki>{{#ask: [[Category:Cat1]] [[Category:Cat2]]</nowiki> it will give me an intersection between Cat1 and Cat2.
Is it possible to get a reunion (basically OR instead of AND)
Thanks so much! [[Special:Contributions/86.122.98.27|86.122.98.27]] 09:42, 12 September 2014 (UTC)
:The documentation for this is at https://semantic-mediawiki.org/wiki/Help:Selecting_pages (see "Unions of query results..."), where you'll find that you can do so in two possible ways.
:FWIW, there's also [[Extension:Semantic Compound Queries]], which does something similar although it is in some ways inferior to using #ask. [[User:Cavila|Cavila]] <span style="font-size:65%;">(MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)</span> 18:30, 12 September 2014 (UTC)
::thanks so much! really appreciate it! [[Special:Contributions/86.122.98.27|86.122.98.27]] 22:15, 12 September 2014 (UTC)

== Cannot install core SMW2.0 extension on MW1.23 ==

Hello, I'm trying to install just SMW by itself on MW1.23.5 but when I use either composer or the ExtensionDistributor I get the same result when trying to run the maintenance/update.php script which is about 15 warnings about classes such as "SMW\Store" not found and finally a fatal error as follows:
:'''Fatal error: Class 'SMW\SimpleDependencyBuilder' not found in /home/translat/public_html/w/123/mediawiki-1.23.5/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 112'''
Anyone have any ideas what might be wrong here? [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 15:28, 14 October 2014 (UTC)
:I've tried dropping back to SMW1.9 with Semantic Bundle so that I can be sure the versions of Validator etc match, but unbelievably I'm still getting the same result!!! [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 20:15, 14 October 2014 (UTC)
::You can not use Semantic Bundle with any other version of SMW of which it has been released because it registers the vendor/autoloader manually and doesn't use Composer to manage its package dependencies which caused issues in the past [0, 1] and will so in future because of the different class map.
::If you install SMW via Semantic Bundle then you have to wait until a new version is released otherwise trying to upgrade to another version of SMW will ultimately fail.
::I would suggest you deleted the vendor folder and re-install SB.
::For example, if on the other hand you install SMW via Composer, each time an update or removal occurs the autoloader (which is where the "Fatal error: Class" message comes from in case classes are not registered) is being re-generated to ensure it matches with the expected class map.
::[0] https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/229
::[1] http://wikimedia.7.x6.nabble.com/Installing-SMW-without-composer-tp5023207p5023218.html [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 15:04, 15 October 2014 (UTC)
:::I'm not installing a different version or upgrading, I've just tried to install SMW and some of the other related extensions in the SemanticBundle and I'm getting the errors shown above. When I sadi "I've tried dropping SMW back to 1.9" what I meant is that I've tried the entire installation operation from scratch using Semantic Bundle that comes with version 1.9 of SMW. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 12:19, 17 October 2014 (UTC)
:Installing SMW 2.* via Composer works as expected (being constantly monitored and tested via Travis-CI [0]).
:[0] https://s3.amazonaws.com/archive.travis-ci.org/jobs/38009543/log.txt [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 15:09, 15 October 2014 (UTC)
::In my case it's not working as expected, it's giving the errors shown above. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 12:26, 17 October 2014 (UTC)
:::I've got it working with composer. What I was doing wrong was installing composer and the SMW extensions within the extensions directory which didn't work. When I did it within the mw root dir it installed the extensions properly. Next I had includes for SMW extensions in the LocalSettings.php file which were raising errors as they're not needed anymore when installing with composer. Thanks for your help. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 16:02, 20 October 2014 (UTC)

== loops and images ==

Hi, I am new to Semantic. I have been trying to build a basic query that will list all items in a category and their properties :
<pre>{{#ask:[[Category:items]] [[name::+]] [[size::+]]
| ?name
| ?size#-
| ?stacklimit#-

| ?location
| ?description#-
| mainlabel=-
| headers=plain
}}
</pre>
And I keep getting several repeated over and over again, receiving some 500 items for what should have been 20. Can you point me in the right way to solve this?

Also what is the right way to list all image files in a category. I have tried using this:
<pre>{{#ask:[[Category:items images]]
| format=ul
}}</pre>
But I get a list of thumbnails and change it plain, result in a plain list of names. How can I get a list of name + links? [[Special:Contributions/87.68.255.133|87.68.255.133]] 00:28, 9 November 2014 (UTC)

== Installation. MW 1.25 ==

I installed Mediawiki 1.25.1 (new empty DB, no extensions). I run the installation script for SMW (https://www.semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.22%2B)

#> composer.phar require mediawiki/semantic-media-wiki "~2.1"

The composer reports:

[RuntimeException]
The lock file does not contain require-dev information, run install with the --no-dev option or run update to install those packages.

What am I doing wrong? [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 19:32, 31 May 2015 (UTC)
:See [0].
:[0] https://semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.22%2B#MW_1.25.2B [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 17:46, 1 June 2015 (UTC)
::Thanks a ton, I just wanted to start investigating about this.
::Edit: I have just created a [[semantic-mw:Help:Installation/Using_Composer_with_MediaWiki_1.25%2B|dedicated page for MW 1.25+]] based on your info. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:49, 1 June 2015 (UTC)
:::Thanks! ) [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 19:43, 1 June 2015 (UTC)
::::The problem was not solved. The script <code>composer.phar install</code> still reports ''run install with the --no-dev''. The script <code>composer.phar install --no-dev</code> reports ''ok'' but the script <code>composer.phar require mediawiki/semantic-media-wiki "~2.2"</code> again reports the same error.
::::What I need to do? [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 20:39, 1 June 2015 (UTC)
:::::Apparently it is not <code>composer.phar install</code> but <code>composer.phar update</code> that would ensure that all packages for MW 1.25 are installed (because 1.25 comes with a pre-deployed composer .json) before SMW can be added. [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 22:43, 1 June 2015 (UTC)
::::::Thanks, it's work! [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 23:13, 1 June 2015 (UTC)

== SMW and MW 1.25.1 not showing property names correctly ==

:'''MW: 1.25.1'''
:'''SMW: (latest from composer, "~2.1")'''
:Working tirelessly to get this to work and understand it. I'm using the "Berlin" example from the "Demo::", vis-a-vis this:
:<code> Berlin is home to [[Population::3,520,061]] souls. It is located in [[located in::Germany]].</code>
:Basically, the problem is I have is, in the fact box, the incorrect output following:
:<code> Facts about "Sandbox:Berlin"</code>
:<code> RDF feed</code>
:<code> Population|3,520,061|Population 3,520,061 +</code>
:<code> located in|Germany|located in Germany +</code>
:and - just this morning - I see the correct output briefly IF I write LocalSettings.php after commenting out enableSemantics()
:<code> Facts about "Sandbox:Berlin"</code>
:<code> RDF feed</code>
:<code> Located in Germany +</code>
:<code> Population 3,520,061 +</code>
:Upon refresh of the correctly-displaying page, without touching LocalSettings.php again, it reverts to the old, incorrect output.
:Bottom line: I cannot get consistent, correct behavior.
:What I have the 'enableSemantics" is of this form:
:enableSemantics( 'web.mysite.com/wiki' );
:I read somewhere that "enableSemantics" is no longer necessary, but there is no consistent idempotency: hitting refresh even on a correctly-displayed page with Factbox always reverts back to the wrong one.
:Everything else in the MW install works correctly. I see tremendous potential in Semantic-MediaWiki and would very much like to become an advocate of its power.
:Additional details:
:If, on the correct page, I click on Population (for which I've entered a page definining it as a number, ergo "This is a property of type [[Has type::Number]]"), the "Number" links (correctly) to Special:Types/Number.
:On the incorrectly-displayed page, clicking on Populate tries to create a page called "Property:3,520,061".
:Any help appreciated.
:-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 16:23, 11 June 2015 (UTC)
::It appears that commenting in/out the
::<code> enableSemantics( 'web.mysite.com/wiki' );</code>
::is a red herring (will leave commented out since it's no longer necessary according to SMW documentation).
::Appparently I am up against some kind of caching issue. As much caching as possible has been turned OFF for debugging.
::Again, any help deeply appreciated.
::-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 16:45, 11 June 2015 (UTC)
:::It appears that setting this (in LocalSettings.php) thus
:::<code> $smwgEnableUpdateJobs = false;</code>
:::has helped ENORMOUSLY.
:::-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 19:47, 11 June 2015 (UTC)
::If you follow the video [0] you should get an idea how it supposed to work on a vanilla installation.
::> On the incorrectly-displayed page, clicking on Populate tries to create a page called "Property:3,520,061".
::This is a clear indication that your Property NS isn't setup correctly otherwise "3,520,061" would be just a plain text (under the assumption that Has number is of type number) and not be red linked.
::> enableSemantics( 'web.mysite.com/wiki' );
::> is a red herring (will leave commented out since it's no longer necessary according to SMW documentation).
::I don't think the installation [1, 2] is mentioning that "enableSemantics" is no longer required.
::> It appears that setting this (in LocalSettings.php) thus
::> $smwgEnableUpdateJobs = false;
::$smwgEnableUpdateJobs [3] has nothing to do with the Property namespace and should only be temporary set to false in order to disable inserting UpdateJob's into the job queue (due to high load).
::In the matter of the Property NS, please have a look at [4].
::[0] https://vimeo.com/82255034 (https://semantic-mediawiki.org/wiki/Help:Getting_started)
::[1] https://semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.25%2B
::[2] https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/INSTALL.md#step-5
::[3] https://semantic-mediawiki.org/wiki/Help:$smwgEnableUpdateJobs
::[4] https://semantic-mediawiki.org/wiki/Help:Namespaces [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 13:20, 17 June 2015 (UTC)
:It turns out that other extensions loaded via MW's extension.json can in fact nullify the SMW NS setting. For more information and a solution, see [0].
:[0] <nowiki>http://wikimedia.7.x6.nabble.com/MW1-25-1-SMW-2-2-breaks-when-installed-with-DynamicSidebar-tp5049862.html</nowiki> [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 14:53, 30 July 2015 (UTC)

== . ==
{{Archive top|result=.|status=resolved}}

[[User:Tenbergen|Tenbergen]] ([[User talk:Tenbergen|talk]]) 15:46, 22 July 2015 (UTC)
{{Archive bottom}}

== Can't see the Special:SMWAdmin to finish installation ==

Hi, I have an issue when try to initialise tables for semantic,

The wiki show me the special page Special:SMWAdmin does't exist, I can see the extension listed in the Special:Version page.

My wiki are on subfolder domain.

I try this:

enableSemantics('<nowiki>http://mydomain'</nowiki>);

and

enableSemantics('<nowiki>http://mydomain/subfolder'</nowiki>);

without any favorable result, what can be? [[Special:Contributions/187.189.160.180|187.189.160.180]] ([[User talk:187.189.160.180|talk]]) 20:08, 14 August 2015 (UTC)
:Please have a look at [0].
:[0] https://semantic-mediawiki.org/w/index.php?title=Help:Special:SMWAdmin#Access%20restrictions [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 12:38, 21 August 2015 (UTC)
:That doesn't help. The Special page SMWAdmin does not appear if the read permissions are set to "false" for every group :
:<code> $wgGroupPermissions['*']['read'] = false;</code>
:You have to set it to '"true to see the Special page SMWAdmin. That's an issue ! [[Special:Contributions/31.39.114.223|31.39.114.223]] ([[User talk:31.39.114.223|talk]]) 18:02, 26 February 2016 (UTC)
:The cause of this problem seems to be the incompatibility with the ConfirmEdit Extension : [[Thread:Talk:Semantic Bundle/Property namespace disappears with SB]] [[Special:Contributions/31.39.114.223|31.39.114.223]] ([[User talk:31.39.114.223|talk]]) 20:25, 28 February 2016 (UTC)

== Please add this page to translate ==

Please add this page to translate [[User:Перевод15|Перевод15]] ([[User talk:Перевод15|talk]]) 19:47, 11 March 2016 (UTC)

== Resources fail to load with non-default extensions setup (e.g. symlinks) ==
{{Archive top|result=SMW 2.4.0 brought a [https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/1476 solution]|status=resolved}}

I configured a shared wiki setup with different extension features per wiki. In SMW 2.3.1 when debug=true in the URL some resources issue an error not to be loaded. With MW 1.25+ it is considered to set up a different extension directory ([[Manual:$wgExtensionDirectory]]) but it is not taken into account for SMW resources. I checked out and see why: SemanticMediaWiki/res/Resources.php assumes folder extensions to be there but allowing a different <code>$wgExtensionDirectory</code> this assumption is proven wrong. So if I add <code>debug=true</code> to the URL I get <nowiki>http://offene-naturfuehrer.de/w/extensions//usr/share/mediawiki26/extensions-rich-features/SemanticMediaWiki/res/smw/util/ext.smw.util.tooltip.js</nowiki> it becomes 404 and does not get loaded. Is there any fix I can do, LocalSettings or so? See also https://phabricator.wikimedia.org/T130520 [[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 11:01, 21 March 2016 (UTC)
:There is an [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/1466 issue at GitHub] for this now. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 13:22, 21 March 2016 (UTC)
{{Archive bottom}}

== Semantic queries aren't showing all the results ==
{{Archive top|result=SMW 2.5.0 brought [https://www.semantic-mediawiki.org/wiki/Help:Full-text_search full-text search]|status=resolved}}

Hi,

For some reasons, semantic queries aren't showing all the results on my wiki.

On Wikifab.org, the property "Material" of the page "[http://en.wikifab.org/index.php/ZipStich_Chair_with_plywood_pieces_and_zip_ties ZipStick Chair...]" contains the terms "Plywood" and "strong". However:
* this [http://en.wikifab.org/index.php?title=Special%3AAsk&q=%5B%5BMaterial%3A%3A~*Plywood*%5D%5D&po=&eq=yes&p%5Bformat%5D=broadtable&sort_num=&order_num=ASC&p%5Blimit%5D=&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=...+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&p%5Bsep%5D=&eq=yes query] correctly have "ZipStich Chair..." in the results
* But this [http://en.wikifab.org/index.php?title=Special%3AAsk&q=%5B%5BMaterial%3A%3A~*strong*%5D%5D&po=&eq=yes&p%5Bformat%5D=broadtable&sort_num=&order_num=ASC&p%5Blimit%5D=&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=...+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&p%5Bsep%5D=&eq=yes query] dont...
Do you know why? Is it a known issue?

Thanks in advance for your help. [[Special:Contributions/85.54.29.115|85.54.29.115]] ([[User talk:85.54.29.115|talk]]) 05:55, 5 July 2016 (UTC)
:This is currently not supported. See [[semantic-mw:Help:Type_Text#Searching_within_values|for why]]. This may however change [https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/1481 very well with SMW 2.5] later this year. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 15:40, 5 July 2016 (UTC)
:Thanks for your reply. I have subscribe to the notifications and asked a developer of our team to see if he can help. [[Special:Contributions/83.47.139.142|83.47.139.142]] ([[User talk:83.47.139.142|talk]]) 09:38, 6 July 2016 (UTC)
{{Archive bottom}}

== Semantic Mediawiki website offline ==
{{Archive top|result=The website is back on-line.|status=resolved}}

https://www.semantic-mediawiki.org/ has been offline for some time. What is going on?
[[User:Henryfunk|Henryfunk]] ([[User talk:Henryfunk|talk]]) 11:47, 11 January 2017 (UTC)
:Thanks for reporting. I guess this is a DOS attack. The VM should be rebooted and see if this makes them back off. Currently I do not have access to the interface enabling me to do this but I am working on it. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 15:47, 11 January 2017 (UTC)
:Thanks. I hope you succeed. In the meantime, people who need access to the site can do as follows:
:# Navigate to: https://archive.org/
:# In the WaybackMachine input area at the top of the page, type in: https://www.semantic-mediawiki.org/ and press Enter
:# After a few seconds a calendar will appear. Click the blue circle on the last item (so far): 31 December 2016, and wait five or 10 seconds
:# You should now see a copy of semantic-mediawiki.org's frontpage. You can use the menus etc., just be a little patient, it takes a while before pages are shown, and be aware that this is a static copy of the site. [[User:Henryfunk|Henryfunk]] ([[User talk:Henryfunk|talk]]) 10:26, 12 January 2017 (UTC)
{{Archive bottom}}

== Help for Wikia users ==
{{Archive top|result=see http://smwtest.wikia.com|status=resolved}}

Wikia provides a "Semantic MediaWiki Test Wiki " to help users of the relatively few Wikia sites that use semantic extensions: <nowiki>http://smwtest.wikia.com</nowiki>. Some material is copied from this MW site, augmented by the occasional note about the current Wikia version of each extension. [[User:Robin Patterson|Robin Patterson]] ([[User talk:Robin Patterson|talk]]) 06:59, 16 February 2017 (UTC)
{{Archive bottom}}

== mediawiki/semantic-media-wiki: 2.5.0 installed, ~2.5 required. ==
{{Archive top|result=use "update.php --skip-external-dependencies"|status=resolved}}

I'm not sure is it a bug or I'm doing something wrong but after the command <code>composer require mediawiki/semantic-media-wiki "~2.5" --update-no-dev</code> when I'm running <code>php $IP/maintenance/updae.php</code> this message appears:

<pre>
mediawiki/semantic-media-wiki: 2.5.0 installed, ~2.5 required.
Error: your composer.lock file is not up to date. Run "composer update" to install newer dependencies
</pre>

This problem was solved when I changed 'semantic-media-wiki' directive in <code>composer.json</code> from:

<pre>"mediawiki/semantic-media-wiki": "~2.5"</pre>

to:

<pre>"mediawiki/semantic-media-wiki": "2.5.0"</pre>

'''It it the right solution?''' [[User:Spas.Z.Spasov|Spas.Z.Spasov]] ([[User talk:Spas.Z.Spasov|talk]]) 13:47, 4 April 2017 (UTC)
:This way you will have to update your file every time a new version is released. See [https://www.semantic-mediawiki.org/wiki/Help:Installation/Troubleshooting#Error:_your_composer.lock_file_is_not_up_to_date. here] for another way around this. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 20:35, 4 April 2017 (UTC)
{{Archive bottom}}

== How to rebuild semantic mediawiki information? ==
{{Archive top|result=The script is located at "<code>/../extensions/SemanticMediaWiki/maintenance/</code>"|status=resolved}}

I have a page A and page B. Both page does not have properties which link each page. But page A show me B have a property which linked to A. I can not find a property of page B which link to page A.

Maybe something wrong on database. I'd like to clear this. I run /maintenance/rebuildall.php but not fixed.

Would you recommend me how to fix this? Thanks.

my private wiki have mediawiki 1.28.2, SMW 1.25.1, Apache PHP MySql on debian linux. [[User:Naramoksu|Naramoksu]] ([[User talk:Naramoksu|talk]]) 00:13, 2 May 2017 (UTC)
:I am not sure if I understand the issue correctly. However if you would like to rebuild semantic data you will have to use the [https://www.semantic-mediawiki.org/wiki/Help:Maintenance_script_%22rebuildData.php%22 "rebuildData.php"] script which is located in "/extensions/SemanticMediaWiki/maintenance". The "rebuildall.php" script has a different scope and is provided by MediaWiki core. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 08:34, 2 May 2017 (UTC)
:Thanks for your information. I just looked at the maintenance directory. [[User:Naramoksu|Naramoksu]] ([[User talk:Naramoksu|talk]]) 13:29, 2 May 2017 (UTC)
{{Archive bottom}}

== MyISAM support is blocking use of Azure Database for MySql ==
{{Archive top|result=See [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/2661 this issue and the linked documentation].|status=resolved}}

I just attempted to move my mediawiki DB into Azure Database for MySql (their new hosted MySql offering). Got blocked on the use of MyISAM fulltext search on smw_ft_search.

Can this be migrated to InnoDB soon? Latest MySQLs have support for fulltext in InnoDB. [[User:Lsilverman|Lsilverman]] ([[User talk:Lsilverman|talk]]) 18:41, 11 July 2017 (UTC)
:Sorry, I did not see this. See [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/2661 this issue and the linked documentation] on how to switch to InnoDB. It is just a configuration parameter setting. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 12:07, 9 September 2017 (UTC)
{{Archive bottom}}

== Mediawiki 1.29.1 and Semantic ==
{{Archive top|status=resolved}}

I have update from MW 1.26.4 to
{| class="wikitable"
!Software
!Version
|-
|[https://www.mediawiki.org/ MediaWiki]
|1.29.1
|-
|[https://php.net/ PHP]
|5.6.30-nmm1 (fpm-fcgi)
|-
|[https://www.mysql.com/ MySQL]
|5.7.15-nmm5-log
|-
|[http://site.icu-project.org/ ICU]
|55.1
|}
I have install the last version of all Semantic extensions. Now i get this Semantic Errors:

http://kubb290.kubbwiki.de/

'''Warning''': Class 'SMW\Updater\DeferredCallableUpdate' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''8'''

'''Warning''': Class 'SMW\Parser\InTextAnnotationParser' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''9'''

'''Warning''': Class 'SMW\Encoder' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''10'''

'''Warning''': Class 'SMW\Query\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''11'''

'''Warning''': Class 'SMW\Query\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''12'''

'''Warning''': Class 'SMW\Query\ExportPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''13'''

'''Warning''': Class 'SMW\Query\ResultPrinters\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''14'''

'''Warning''': Class 'SMW\Query\ResultPrinters\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''15'''

'''Warning''': Class 'SMW\Query\ResultPrinters\FileExportPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''16'''

'''Warning''': Class 'SMW\Query\Parser' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''17'''

'''Fatal error''': Interface 'SMW\QueryEngine' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/includes/storage/SMW_Store.php''' on line '''34'''

All Pathe are correct and all Files are exist.

Idea what is wrong?

thank's

Bastor [[User:Bastor de|Bastor de]] ([[User talk:Bastor de|talk]]) 22:59, 28 October 2017 (UTC)
:I the files are not loaded than it does not matter if they are existing or not. I guess you did not install and upgrade via command line. You used [https://github.com/SemanticMediaWiki/SemanticMediaWiki/releases/tag/2.5.5 one of the tarballs with dependencies]? If yes there may be some issue mashing this up with MediaWiki. In this case I recommend to install MW on a machine with command line add SMW to it and after this is done move the files all over. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 16:06, 30 October 2017 (UTC)
:MMh, thanks for tip.
:After my first test i get the same error :-(
:Think you my database have a error or the file structur a wrong? [[User:Bastor de|Bastor de]] ([[User talk:Bastor de|talk]]) 17:04, 31 October 2017 (UTC)
:I think the issue is that the files are not being loaded properly. So installing MW on a machine with command line adding SMW to it and after this moving the files all over did not work? This has nothing to do with the database. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 21:11, 31 October 2017 (UTC)
:Thanks for help, You were right [[Special:Contributions/77.180.154.2|77.180.154.2]] ([[User talk:77.180.154.2|talk]]) 00:43, 4 November 2017 (UTC)
:Glad it worked out! [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:07, 4 November 2017 (UTC)
{{Archive bottom}}

== mediawiki smw-editpage-annotation-enabled editform to large ==
{{Archive top|status=resolved}}

Hello,

my EditForm is to large and the save button is out of my screen. I must scroll down, to press the button.

After installing SmenaticMediaWiki there is a smw-editpage-annotation-enabled-section in the Firefox DebugConsole, that push the EditForm a little bit down.

I need a option to reduce the size of the editform, OR i need the option to collapsible the smw-editpage-annotation-enabled-section.

Can anyone help me? [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 08:21, 4 April 2018 (UTC)
:There is a configuration parameter called [[semantic-mw:Help:$smwgEnabledEditPageHelp|$smwgEnabledEditPageHelp]] to disable the info alltogether. Perhaps there is also a way to make it collapsible via CSS [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 09:11, 4 April 2018 (UTC)
{{Archive bottom}}

== How to get all future ''end'' dates of a recurring event? ==
{{Archive top|result=See [[semantic-mw:Thread:Help_talk:Recurring_events/How_to_get_all_future_end_dates_of_a_recurring_event%3F|this thread]].|status=resolved}}

I know how to get the beginning date time of a recurring event (a usual #ask will do so) but I did not figure out how to get the end of date times of future recurring events. How can I #ask for recurring end dates that come in the future? Is it possible? Or do I have to program a work around by let’s say using Unix timestamps, and add it to the #ask result to get the corresponding end time of the future event? [[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 13:04, 12 November 2018 (UTC)
:Sorry for replying late. See my answer to [[semantic-mw:Thread:Help_talk:Recurring_events/How_to_get_all_future_end_dates_of_a_recurring_event%3F|this thread]]. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:57, 2 January 2019 (UTC)
{{Archive bottom}}

== Which version to install for MW 1.31? ==
{{Archive top|status=resolved}}

Hello there, I have recently upgraded our wiki to MW 1.31. Now I want to install SMW and therefore I downloaded the extension from github. I chose branch 3.0.x. Now I receive the following message via Apache error log:
<pre>
[Mon Dec 10 13:44:09.696457 2018] [php7:error] [pid 26447] [client 79.226.0.171:53406] PHP Fatal error: Uncaught UnexpectedValueException: callback 'SemanticMediaWiki::initExtension' is not callable in /var/www/test/mediawiki/includes/registration/ExtensionRegistry.php:360\nStack trace:
#0 /var/www/test/mediawiki/includes/registration/ExtensionRegistry.php(159): ExtensionRegistry->exportExtractedData(Array)
#1 /var/www/test/mediawiki/includes/Setup.php(116): ExtensionRegistry->loadFromQueue()\n#2 /var/www/test/mediawiki/includes/WebStart.php(88): require_once('/var/www/test/m...')
#3 /var/www/test/mediawiki/index.php(39): require('/var/www/test/m...')
#4 {main}\n thrown in /var/www/test/mediawiki/includes/registration/ExtensionRegistry.php on line 360, referer: https://test.perrypedia.proc.org/wiki/Spezial:Spezialseiten
</pre>
So the question is, which version (branch) should I use? [[User:AnonymusGdpr|AnonymusGdpr]] ([[User talk:AnonymusGdpr|talk]]) 12:51, 10 December 2018 (UTC)
:Note that SMW gets invoked like this only, e.g.:
:<syntaxhighlight lang='text'>
enableSemantics( test.perrypedia.proc.org );
</syntaxhighlight>
:No requrire_once, no wfLoadExtension etc. Also note that you cannot install it using some tarball etc. To use Composer is imperative.
:You may use 2.5.x or 3.0.x (preferred) [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 13:23, 10 December 2018 (UTC)
:Not very easy and not very user-friendly, but finally I got it.
:Now the setupStore script is running and I am a little bit worried. The current step is "Checking smw_hash field ... missing 232626 rows". Running for more than one hour now it shows "updating document no. 3045 (1%)"
:Does it mean I will have to watch that job for more than four days? [[User:AnonymusGdpr|AnonymusGdpr]] ([[User talk:AnonymusGdpr|talk]]) 17:04, 10 December 2018 (UTC)
:I cancelled the job now. 3 hrs, 3 %, sorry: unbearable. [[User:AnonymusGdpr|AnonymusGdpr]] ([[User talk:AnonymusGdpr|talk]]) 18:45, 10 December 2018 (UTC)
:Much better, the database is corrupted now. I can no longer run the regular update.php, nor is it possible to uninstall SMW and/or the composer. Luckily it is just the test wiki. I now am considering of never trying it again. [[User:AnonymusGdpr|AnonymusGdpr]] ([[User talk:AnonymusGdpr|talk]]) 18:55, 10 December 2018 (UTC)
:Sorry that it does not work out for you. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 23:34, 10 December 2018 (UTC)
{{Archive bottom}}

== Trouble installing SMW 3.0 ==
{{Archive top|result=See the respective [https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/thread/e7e76638-4255-f592-cd26-ca90fbfc2c27%40kghoffmeyer.de/#msg36507174 mailing list] thread.|status=resolved}}

Hello,

I have installed SMW 3.0 on top of MW 1.27.5 (PHP 5.6.38, MySQL 5.6.39-log, ICU 52.1)

Installation went fine. I ran PHP update in the local directory, and got in return "Your composer.lock file is up to date with current dependencies! Set $wgShowExceptionDetails = true; in LocalSettings.php to show detailed debugging information."

... from which I infer that no updates were made. The Mediawiki stuff is in the subdirectory '/mw'

When I add the instruction enableSemantics( 'www.railwayobjects.eu/mw' ) at the end of LocalSettings.php in the file on the server, and try to reload my wiki, all I get is a blank page. The Firefox console only says:

______________________________

Promise rejected after context unloaded: Promised response from onMessage listener went out of scope

page_performance.js:18

Unchecked lastError value: Error: Promised response from onMessage listener went out of scope page_performance.js:18

______________________________

I'm sorry to say, I am stuck... any help is more than welcome. [[User:Amagnien2|Amagnien2]] ([[User talk:Amagnien2|talk]]) 15:13, 2 January 2019 (UTC)
:See the [https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/thread/e7e76638-4255-f592-cd26-ca90fbfc2c27%40kghoffmeyer.de/#msg36507174 mailing list] [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:11, 2 January 2019 (UTC)
{{Archive bottom}}

== Which Version of Semantic with which Version of MediaWiki ==

I don't understand, which version are compatible.

I use Composer, composer.local.json:

"require": {"mediawiki/semantic-media-wiki": "~2.5", ....

I have checked out MediaWiki REL1_31 and composer install --no-dev --> Result: remove mediawiki/core dev-REL1_31|remove mediawiki/semantic-media-wiki 2.5.8

I have checked out MediaWiki REL1_32 and composer install --no-dev --> Result: remove mediawiki/core dev-REL1_31|remove mediawiki/semantic-media-wiki 2.5.8 [[Special:Contributions/213.61.254.67|213.61.254.67]] ([[User talk:213.61.254.67|talk]]) 08:17, 25 January 2019 (UTC)
:I have the same problem with Semantic Version 3:
:remove mediawiki/core dev-REL1_31|remove mediawiki/semantic-media-wiki 3.0.1 [[Special:Contributions/213.61.254.67|213.61.254.67]] ([[User talk:213.61.254.67|talk]]) 09:12, 25 January 2019 (UTC)
:Have a look at the [https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/COMPATIBILITY.md compatibility document], e.g. SMW 3.0.1 is compatible with MW 1.31. See here for [https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/INSTALL.md how to install], i.e. use "composer.local.json" instead. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 11:57, 25 January 2019 (UTC)
:My problem was in the file composer.local.json the line:
:    "extra": {
:    "merge-plugin": {
:    "include": [
:    "extensions/*/composer.json"
:composer are not understand this recursively... I don't know why. [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 08:57, 28 January 2019 (UTC)

Topic:Uamo79kdvbn00hbq

2018-04-06T07:44:50Z

213.61.254.68 (talk) commented on "disable "editpage-copy-warn" for edit ?" (I have my own use css, but the changes doesn't affect. After set this setting, it works)

Project:Support desk/Flow/2018/04

2018-04-06T07:44:50Z

213.61.254.68: /* disable "editpage-copy-warn" for edit ? */ Added reply

{{flow imported revision}}
{{Project:Support desk/Header}}

== How to get "Add topic", "Start a new topic", or "Add Section" on Content Page (not Talk), Without VisualEditor? ==

How to get "Add topic", "Start a new topic", or "Add Section" on Content Page (not Talk), Without VisualEditor?

thx [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 00:05, 1 April 2018 (UTC)
:Use <nowiki>__NEWSECTIONLINK__</nowiki> ([[Help:Magic words]]) [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:21, 3 April 2018 (UTC)
:Great! How to get that into all page headers?
:i'm using [[Extension:Header Footer]], but that just puts the "Add topic" button to the top of the header-page, instead of all pages.
:is there a way? Put into skin? [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 16:20, 4 April 2018 (UTC)
:You may add it with the [[Manual:Hooks/SkinTemplateNavigation]] hook [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 19:23, 4 April 2018 (UTC)

== TinyMCE infinite loop error and freeze ==

I have tried several Mediawiki versions, from 1.26.4 to 1.31-alpha and in every version i get infinite loop error when i go to "Show preview" and it freezes when i go to "Save page".... Is there anything i can do about that? [[User:Darkwarrior92|Darkwarrior92]] ([[User talk:Darkwarrior92|talk]]) 15:20, 1 April 2018 (UTC)

== What is {{Draft}} Tag? ==
{{Archive top|result=<pre>
{{Draft}}
</pre>by itself is not an extension. It is transcluding/rendering the page Template:Draft. The Template contains the "under-construction" image, the "This page is a draft" message, and other behind-the-scenes things, such as the use of Template:Mbox.

Normally, it has to be manually added and removed, but can be automatically added with a bot, a create-page button, or a boiler plate extension.|status=resolved}}

[[Annoying little bugs|This page]] says "This page is currently a draft." It's source contains <pre>
{{Draft}}
</pre>How is this done? [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 19:39, 1 April 2018 (UTC)
:It is transcluding/rendering the page [[Template:Draft]]. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 20:05, 1 April 2018 (UTC)
:It appears the Template contains nothing except the "under-construction" image, and the "This page is a draft" message, correct?
:[[Template:Draft]]
:And the transclude has to be manually added and removed, right? It's not automatically displayed based on namespace, correct? [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 22:03, 1 April 2018 (UTC)
:That is what the template appears to the reader, but there are other behind-the-scenes things, such as the use of [[Template:Mbox]], too.
:To automatically add the template a bot will have to be used, or a create page button which pre-fills some of the content on the page, or one of those boiler plate extensions, which based on some rules pre-fill content on the page. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 04:31, 2 April 2018 (UTC)
{{Archive bottom}}

== Preventing articles from appearing in maintenance pages ==

Is there a way to have certain pages not displayed in maintenance special pages? For example, to prevent an uncategorized page from appearing in Special:UncategorizedPages. Or a page with some broken files to not appear in Category:Pages with broken files links. Thanks! [[Special:Contributions/2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B|2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B]] ([[User talk:2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B|talk]]) 21:11, 1 April 2018 (UTC)

== Bug? New Page is Visible Before Approval by ApprovedRevs ==

To replicate problem:
# Login as user '''without''' `approverevisions` permission
# Create a new page. Enter some random text. Save the new page.
# Log out.
# Return to new page.
# View page history: the ApprovedRevs link says "approve", indicating the page has not yet been approved.
# Switch to `Read` mode on the page.

'''Expected result:''' The page contents should not be visible, because it has not be approved yet.

'''Actual result:''' The page contents are visible.

{{FlowMention|Yaron Koren}} [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 22:38, 1 April 2018 (UTC)
:[[Extension:Approved_Revs#Displaying_unapproved_pages_as_blank]] [[User:Wargo|wargo]] ([[User talk:Wargo|talk]]) 09:37, 2 April 2018 (UTC)
:you're right, i forgot about that config.
:i'm exploring if a mod involving Draft namespace could be done simply:
:- User manually creates new page in Draft namespace.
:- On first rev approval, auto-move page to "Main" namespace. [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 15:59, 2 April 2018 (UTC)

== bad CSS cuts off descenders ==

I'm a routine user of ArchLinux's and openSUSE's wikis. For many web sites I routinely use, I create user styles to override common idiotic site styles, e.g. non-default space-wasting leading. Font designers know how to design their fonts for optimal use. Extra leading is entirely unnecessary when appropriate line lengths, font size and contrast are declared.

Mediawiki's load.php includes the following:

.diff-addedline .diffchange, .diff-deletedline .diffchange {padding: 0.25em 0;}

The result of this rule causes descenders on diff pages where it is applied to be cut off in all Gecko versions tested, among which RV17, RV52 and RV59, on desktops using 108 DPI and 120 DPI, and browser default font settings of 18px and 20px. Thus with my line-height override to use *normal* leading, I found that an override to the above declaration that reduces the padding to 0 enables seeing all descenders. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 08:10, 2 April 2018 (UTC)

== Get wiki's default timezone in JS? ==

I need to get the wiki's default timezone offset in order to correct the timestamp which the API returns, which for some reason ignores the wiki's timezone and is always in UTC, unlike magic words like <code>CURRENTTIMESTAMP</code> which use the wiki's timezone.

I know the offset is included in the <code>user.defaults</code> module, but there seems to be no way to access it. I can only retrieve the user's options, which does not include the default value if the user has changed the offset from the default. So far the only way seems to make another API request to the siteinfo API, which is annoying when the information is already included in the page. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 11:47, 2 April 2018 (UTC)
:Note, you can combine the two api requests into one if your initial api request is using action=query, as action=query allows you to specifiy both the meta=siteinfo and prop=whatever at the same time.
:I don't think there's any other way to fetch this data. FWIW, CURRENTTIMESTAMP is supposed to be always UTC (vs LOCALTIMESTAMP which is server timezone) [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:28, 3 April 2018 (UTC)
:Ah sorry I got mixed up with the magic words, it is <code>REVISIONTIMESTAMP</code> that uses the server timezone. Good tip about combining the requests, always forget about that, thanks. Still would be nice not to have to download all that extra data. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 03:55, 4 April 2018 (UTC)
:You could place something like the following in LocalSettings.php (untested):
:<source lang="php">
$wgHooks['ResourceLoaderGetConfigVars'][] = function ( &$vars ) {
global $wgLocalTZoffset;
$vars['wgLocalTZoffset'] = $wgLocalTZoffset;
};
</source>
:And then it will be available as <code>mw.config.get( 'wgLocalTZoffset' );</code>. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 17:08, 4 April 2018 (UTC)

== [SOLVED] images 404 ==
{{Archive top|status=resolved}}

Hi, I moved MW from root (<code>/</code>) to (<code>/w</code>) directory and upgrade from 1.20 to 1.30
Html pages are normally opened http://montibus.org/wiki/ old wiki url: http://wiki.mountainclub.ru/

My <code>/.htaccess</code> config

<pre>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^wiki/(.*)$ w/index.php?title=$1 [PT,L,QSA]
RewriteRule ^wiki/*$ w/index.php [L,QSA]
RewriteRule ^wiki$ w/index.php [L,QSA]
</pre>

My <code>/w/images/.htaccess</code> config
<pre>
# Protect against bug T30235
<IfModule rewrite_module>
RewriteEngine On
RewriteOptions inherit
RewriteCond %{QUERY_STRING} \.[^\\/:*?\x22<>|%]+(#|\?|$) [nocase]
RewriteRule . - [forbidden]
# Fix for bug T64289
Options +FollowSymLinks

</IfModule>
</pre>

Part of my <code>/w/LocalSettings.php</code>

<pre>
$wgScriptPath = "/w";
$wgArticlePath = "/wiki/$1";
</pre>

What's wrong? [[Special:Contributions/2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62|2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62]] ([[User talk:2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62|talk]]) 13:24, 2 April 2018 (UTC)
:There problem, that images not opened,
:200 Normal: http://wiki.mountainclub.ru/images/8/89/Андрей_Антонов.jpg
:404 Not Found: http://montibus.org/w/images/8/89/Андрей_Антонов.jpg [[User:EAndreyF|EAndreyF]] ([[User talk:EAndreyF|talk]]) 14:24, 2 April 2018 (UTC)
:SOLVED. There were file permissions error. 620 change to 644 [[User:EAndreyF|EAndreyF]] ([[User talk:EAndreyF|talk]]) 04:51, 3 April 2018 (UTC)
{{Archive bottom}}

== Quickly Share CSS to Community? ==

What's best simple way share with the community, my preferred CSS tweak for this site?<pre>
#p-personal{
position:fixed;
background: rgb(255,255,255);
}
</pre>i assume would work on any MW site.

Keeps notification bar on top when scrolling.

[https://image.ibb.co/bQLJWc/fix_mw_bar.jpg https://preview.ibb.co/jOG8S7/fix_mw_bar.png]

(how to embed images here?) [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 13:28, 2 April 2018 (UTC)
:https://userstyles.org/ ? [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:16, 3 April 2018 (UTC)
:thx, but no luck posting css there. userstyles.org says my "Style code looks unintentionally global. Please read <nowiki>https://github.com/JasonBarnabe/stylish/wiki/Preventing-global-styles</nowiki>"
:They say to "export" from chrome to get domain-specific code, but i don't see how to do that in chrome.
:They also say i can <syntaxhighlight lang='text'>
include the following code anywhere in your style:
/* i really want this to be global */
</syntaxhighlight>I tried that, but that fails for me. Too much trouble.
:i was hoping there might be a place to share css on mediawiki.org, where mediawikians are most likely to find it.
:thx [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 17:16, 4 April 2018 (UTC)

== How to change meta keywords ==

Is it possible to add, or change HTML meta keywords on pages? [[User:NeedAGoodUsername|NeedAGoodUsername]] ([[User talk:NeedAGoodUsername|talk]]) 15:56, 2 April 2018 (UTC)
:See [[Topic:Sudxknl51f1fp3ie]] or [[Extension:Add HTML Meta and Title]] [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 09:09, 4 April 2018 (UTC)

== Can I update a wiki as a bureaucrat, or do I need access to the actual server installation? ==

As I understand it, to update a wiki I need access to the actual server installation (not physically, I can connect to its cPanel or FTP in or whatever), right? I can't just update it as a bureaucrat? [[User:Banaticus|Banaticus]] ([[User talk:Banaticus|talk]]) 19:35, 2 April 2018 (UTC)
:Yes. At the very minimum you need ftp access (To replace the files). Having ssh access is even better. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:15, 3 April 2018 (UTC)

== How to Hardcode a Namespace in Inputbox Create Function? ==
{{Archive top|result=Use prefix=

Eg:<pre>
<inputbox>
type=create
width=100
break=no
buttonlabel=Create new page
default=
prefix=Draft:
</inputbox>

</pre>|status=resolved}}

Extension:InputBox provides a GUI to create new pages, but pages are created in the default namespace.

[[Topic:T2l8bu51332l0tzy]] offers a mod for a namespace dropdown-picker. (not sure this mod is compatible with current releases of MW and InputBox).

But, how to hardcode the target namespace?

thx [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 21:21, 2 April 2018 (UTC)
:Use prefix= [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:15, 3 April 2018 (UTC)
{{Archive bottom}}

== Necessity to install install Visual C++ Redistributable for the Visual Studio 2015 ==

Hello.

We currently have on our server the Wiki version 1.26.0 and PHP version 5.6.26 been installed.

Based on your instruction available on [[Manual:Upgrading]] it looks like we will do an upgrade to Wiki 1.30.0 and PHP v.7.1.15 or more recent.

I know that that our current PHP 5.6.26 uses '''''Visual C++ Redistributable for the Visual Studio 2011, and new PHP 7.1.x requires to install Visual C++ Redistributable for the Visual Studio 2015.'''''

QUESTION: Should I install on our wiki server the '''''Visual C++ Redistributable for the Visual Studio 2015''''' first before downloading MediaWiki tarball or will it re required on the step by running the command php update.php, or will it not be required at all?

Please let us know. Thank you! Alex [[Special:Contributions/198.232.184.254|198.232.184.254]] ([[User talk:198.232.184.254|talk]]) 23:33, 2 April 2018 (UTC)
:So first of all, MediaWiki 1.30 only requires PHP 5.5.9. Thus 5.6.26 is new enough for MediaWiki 1.30, so you do not have to upgrade PHP
:Second, You would only need visual studio if you were compiling PHP by hand. Which would be unusual. Most people get precompiled php packages via your operating system's package manager (e.g. apt, yum, etc) or they download a precompiled binary from the PHP website. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:14, 3 April 2018 (UTC)
:Hello!
:Thank you so much, Bawolff for your comment.
:So, am I correct that if we have PHP 5.6.26 and will upgrade our Wiki from 1.26.0 to 1.30.0 then the command php update.php will not upgrade PHP to the newer version, right?
:Thank you! [[Special:Contributions/198.232.187.14|198.232.187.14]] ([[User talk:198.232.187.14|talk]]) 17:58, 3 April 2018 (UTC)
:<code>php update.php</code> doesn't update PHP (or MySQL etc.), only the MediaWiki installation. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 20:38, 3 April 2018 (UTC)

== "Thank" fails on this mobile site ==
{{Flow summary|Bug-report filed:

https://phabricator.wikimedia.org/T191442}}

I get:

<pre>Send thanks
Do you want to publicly send thanks for this comment?

The postid parameter must be set.</pre> [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 12:31, 3 April 2018 (UTC)
:If that problem is reproducible feel free to file a bug report with sufficient information to reproduce: [[How to report a bug]] [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 12:44, 4 April 2018 (UTC)
:https://phabricator.wikimedia.org/T191442 [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 16:39, 4 April 2018 (UTC)

== How to limit who can add a category? ==

I would like only bureaucrats and administrators the ability to add a category. Is this possible. i would assume so [[User:Jamesghansen|Jamesghansen]] ([[User talk:Jamesghansen|talk]]) 22:11, 3 April 2018 (UTC)
:You could probably use abuse filters to prevent people from adding particular categories to a page, but this isn't necessarily the most reliable, and could cause issues with people editing near the category, as it will think they are changing it. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 03:42, 4 April 2018 (UTC)
:What should happen if a user adds a template to a page, and that template includes a category?
:And what about removing a category from a page? [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:29, 4 April 2018 (UTC)

== Funny problem regarding special chars such as á and ñ - II ==

Hi:

I've been experiencing difficulties with a new MW site and I've done everything at my reach to solve the situation.

I have a 1.29 installation facing a lot of problems with collation. I've installed several times trying different combinations (e.g. binary /utf8, etc) but special characters are not working at all (accented ones such as á, é and others like "ñ"). My tech stack (L: 2.6.32-696.23.1.el6.centos.plus.x86_64, A:2.4.18, MySQL:10.0.34-MariaDB, PHP 5.5.32)

I reviewed the charset in DB and it seems ok (utf8_unicode_ci) and db tables are InnoDB/Binary. I've tried utf8_general_ci, swedish and latin but nothing is working.

After several days trying to make it work i did something different: I used ISO-8859-1 (as a test) from the text editor and when clicking on preview the accented words looked fine! (e.g. when I wrote "Observaci&oacute;n" MW showed correctly "Observación" in the main area).

I've been looking around here for suggestions and I've tried most of them. To avoid a corrupted DB, after the changes (charsets / collations / Localsettings, etc) I've re-installed and recreated both the DB and configurations, pretty much with the same results.

So, if you can provide with a solution it'll be much appreciated.

Regards

Rick [[User:Rickstrat07|Rickstrat07]] ([[User talk:Rickstrat07|talk]]) 00:36, 4 April 2018 (UTC)
:[[Manual:$wgDBTableOptions]] DEFAULT CHARSET=binary is recommended. However note that changing the default collation of a database doesn't change the collation of the existing tables and columns, you'll need to drop all tables and create from scratch.
:If it doesn't work, maybe there's something weird in the server that's sending the page with ISO-8859-1 charset instead of utf-8. Look at the HTTP response headers (use developer tools of your browser, hit F12 and look at the network tab). It should return "content-type: text/html; charset=UTF-8" [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:40, 4 April 2018 (UTC)

== E-mail problems ==
{{Archive top|status=resolved}}

Hi to all, I have some problems with SMTP on my MediaWiki installation. I installed the pear chain, and configured Localsetting.php, but when I try to send emails (such as at the creation of a new user) the browser remains waiting some tens of seconds and then go on without errors, but I don't receive the mail... [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 07:15, 4 April 2018 (UTC)
:This is my configuration:
:<nowiki>#</nowiki>Configure SMTP
:$wgEnableEmail="true";
:$wgEnableUserEmail="true";
:$wgEmergencyContact="wiki@mydomain.it";
:$wgPasswordSender="wiki@mydomain.it";
:$wgNoReplyAddress="myname@gmail.com";
:$wgSMTP = array(
:'host' => "172.20.1.84",
:'IDHost' => "mydomain.it",
:'port' => 25,
:'auth' => false
:);
:$wgShowExceptionDetails = true; [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 07:17, 4 April 2018 (UTC)
:Have you checked the logs of your mail server which you host at 172.20.1.84? [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 09:02, 4 April 2018 (UTC)
:I can't, is out of my control... [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 09:16, 4 April 2018 (UTC)
:Set up a debug log as explained in [[Manual:How to debug]], then try the same action (for example, send yourself an email from Special:Emailuser), From the logs you may be able to see if there's an error trying to contact the SMTP server. For example, a firewall may be blocking such connections. [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:26, 4 April 2018 (UTC)
:Thank you. It returns:
:>>R&D wiki could not send your confirmation mail. Please check your email address for invalid characters.
:>>Mailer returned: Failed to connect to 172.20.1.84:25 [SMTP: Failed to connect socket: Connection timed out (code: -1, response: )]
:But from the console of the server that hosts the wiki I can use telnet to connect to the server and send mail via standard SMTP commands...
:Stefano [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 09:42, 4 April 2018 (UTC)
:Solved. I wrote a space into the server address. Now works.
:Thanks to all!
:Stefano [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 09:54, 4 April 2018 (UTC)
{{Archive bottom}}

== mediawiki smw-editpage-annotation-enabled editform to large ==

Hello,

my EditForm is to large and the save button is out of my screen. I must scroll down, to press the button.

After installing SmenaticMediaWiki there is a smw-editpage-annotation-enabled-section in the Firefox DebugConsole, that push the EditForm a little bit down.

I need a option to reduce the size of the editform, OR i need the option to collapsible the smw-editpage-annotation-enabled-section.

Can anyone help me?

I do not know the right section, here or in the extension-page: [[Topic:Uamkmg06h8y3oukz]] [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 08:22, 4 April 2018 (UTC)

== disable "editpage-copy-warn" for edit ? ==

Who can I disable the complete editpage-copy-warn-section?

When I cleared the MediaWiki:Copyrightwarning2 Page, I have a big red line in that area, in edit mode. [[Special:Contributions/213.61.254.67|213.61.254.67]] ([[User talk:213.61.254.67|talk]]) 09:25, 4 April 2018 (UTC)
:That section should have a CSS class or id. Find it inspecting the element in your browser, and add a CSS rule (see [[Manual:Interface/CSS]]) to hide it (display:none) [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:30, 5 April 2018 (UTC)
:Thank you, I need the [[Manual:$wgAllowUserCss|$wgAllowUserCss]] setting. Well [[Special:Contributions/213.61.254.67|213.61.254.67]] ([[User talk:213.61.254.67|talk]]) 10:12, 5 April 2018 (UTC)
:Only if you're going to add the CSS in your user's styles. You can add it to MediaWiki:Common.css and it will affect all users of your wiki [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 19:23, 5 April 2018 (UTC)
:I have my own use css, but the changes doesn't affect. After set this setting, it works [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 07:44, 6 April 2018 (UTC)

== Fatal Error Call to a member function ==
{{Archive top|status=resolved}}

Hi

I keep getting the below fatal error>

'''Fatal error''': Call to a member function getCode() on null in '''C:\xampp\htdocs\mediawiki\includes\user\User.php''' on line '''1538'''

This is line 1538>But cannot see a problem? Can anyone assist?

$defOptLang = $wgContLang->getCode();

{| class="wikitable"
!Product
!Version
|-
|[https://www.mediawiki.org/ MediaWiki]
|1.28.2
|-
|[https://php.net/ PHP]
|5.6.30 (apache2handler)
|-
|[https://mariadb.org/ MariaDB]
|10.1.21-MariaDB
|} [[User:Ron Barker|Ron Barker]] ([[User talk:Ron Barker|talk]]) 10:46, 4 April 2018 (UTC)
:We'd need a full stacktrace on a supported MediaWiki version - [[Manual:How to debug]]
:Version 1.28 is unsupported, insecure and has security vulnerabilities - [[Manual:Upgrading]] [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 12:42, 4 April 2018 (UTC)
:Thanks but that is far too complicated for me. Anyhow, I have figured it out. It is Malwarebytes protection and it will not allow me to exclude the wiki. It say address not valid, only way it works is by turning it off. [[User:Ron Barker|Ron Barker]] ([[User talk:Ron Barker|talk]]) 15:12, 4 April 2018 (UTC)
{{Archive bottom}}

== DatabaseBase::factory no viable database extension found for type 'mysql' ==

Hi,

I have upgraded to Debian 9 Stretch and am unable to access mediawiki.I get the following error:

[4e49bd3d5b498d4b4a69bfea] /mediawiki/index.php/Main_Page MWException from line 612 of /usr/share/mediawiki/includes/db/Database.php: DatabaseBase::factory no viable database extension found for type 'mysql'

Backtrace:

<nowiki>#</nowiki>0 /usr/share/mediawiki/includes/db/loadbalancer/LoadBalancer.php(828): DatabaseBase::factory(string, array)

<nowiki>#</nowiki>1 /usr/share/mediawiki/includes/db/loadbalancer/LoadBalancer.php(681): LoadBalancer->reallyOpenConnection(array, boolean)

<nowiki>#</nowiki>2 /usr/share/mediawiki/includes/db/loadbalancer/LoadBalancer.php(561): LoadBalancer->openConnection(integer, boolean)

<nowiki>#</nowiki>3 /usr/share/mediawiki/includes/GlobalFunctions.php(3155): LoadBalancer->getConnection(integer, array, boolean)

<nowiki>#</nowiki>4 /usr/share/mediawiki/includes/objectcache/SqlBagOStuff.php(165): wfGetDB(integer)

<nowiki>#</nowiki>5 /usr/share/mediawiki/includes/objectcache/SqlBagOStuff.php(247): SqlBagOStuff->getDB(integer)

<nowiki>#</nowiki>6 /usr/share/mediawiki/includes/objectcache/SqlBagOStuff.php(225): SqlBagOStuff->getMulti(array)

<nowiki>#</nowiki>7 /usr/share/mediawiki/includes/objectcache/SqlBagOStuff.php(221): SqlBagOStuff->getWithToken(string, NULL, integer)

<nowiki>#</nowiki>8 /usr/share/mediawiki/includes/libs/objectcache/CachedBagOStuff.php(52): SqlBagOStuff->doGet(string, integer)

<nowiki>#</nowiki>9 /usr/share/mediawiki/includes/libs/objectcache/BagOStuff.php(179): CachedBagOStuff->doGet(string, integer)

<nowiki>#</nowiki>10 /usr/share/mediawiki/includes/session/SessionManager.php(929): BagOStuff->get(string)

<nowiki>#</nowiki>11 /usr/share/mediawiki/includes/session/SessionInfo.php(149): MediaWiki\Session\SessionManager->generateSessionId()

<nowiki>#</nowiki>12 /usr/share/mediawiki/includes/session/SessionProvider.php(175): MediaWiki\Session\SessionInfo->__construct(integer, array)

<nowiki>#</nowiki>13 /usr/share/mediawiki/includes/session/SessionManager.php(261): MediaWiki\Session\SessionProvider->newSessionInfo(NULL)

<nowiki>#</nowiki>14 /usr/share/mediawiki/includes/session/SessionManager.php(235): MediaWiki\Session\SessionManager->getEmptySessionInternal(WebRequest)

<nowiki>#</nowiki>15 /usr/share/mediawiki/includes/session/SessionManager.php(185): MediaWiki\Session\SessionManager->getEmptySession(WebRequest)

<nowiki>#</nowiki>16 /usr/share/mediawiki/includes/WebRequest.php(700): MediaWiki\Session\SessionManager->getSessionForRequest(WebRequest)

<nowiki>#</nowiki>17 /usr/share/mediawiki/includes/session/SessionManager.php(121): WebRequest->getSession()

<nowiki>#</nowiki>18 /usr/share/mediawiki/includes/Setup.php(747): MediaWiki\Session\SessionManager::getGlobalSession()

<nowiki>#</nowiki>19 /usr/share/mediawiki/includes/WebStart.php(137): require_once(string)

<nowiki>#</nowiki>20 /usr/share/mediawiki/index.php(40): require(string)

<nowiki>#</nowiki>21 {main}

PHP version : PHP 7.0.27-0

Please could someone give me pointers to the issue.

Thanks,

Geetika [[User:GeetikaCS|GeetikaCS]] ([[User talk:GeetikaCS|talk]]) 11:34, 4 April 2018 (UTC)
:you need to install the php7.0-mysql package https://packages.debian.org/stretch/php7.0-mysql
:If it's already installed, you may need to enable it in [[php.ini]]. In that case, remember to restart the webserver after editing php.ini [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:29, 5 April 2018 (UTC)
:Hi,
:I have already installed the php-mysql package and enabled it in php.ini
:php7.0-mysql is already the newest version (7.0.27-0+deb9u1).
:extension=/usr/lib/php/20151012/mysqlnd.so
:extension=/usr/lib/php/20151012/mysqli.so
:even after these and restarting Apache, I get the below error.
:[8f25d88d9d5800b9516be5ab] /mediawiki/ MWException from line 612 of /usr/share/mediawiki/includes/db/Database.php: DatabaseBase::factory no viable database extension found for type 'mysql'
:php --ini
:PHP Warning: Module 'mysqlnd' already loaded in Unknown on line 0
:PHP Warning: Module 'mysqli' already loaded in Unknown on line 0
:Configuration File (php.ini) Path: /etc/php/7.0/cli
:Loaded Configuration File: /etc/php/7.0/cli/php.ini
:Scan for additional .ini files in: /etc/php/7.0/cli/conf.d
:Additional .ini files parsed: /etc/php/7.0/cli/conf.d/10-mysqlnd.ini,
:/etc/php/7.0/cli/conf.d/10-opcache.ini,
:/etc/php/7.0/cli/conf.d/10-pdo.ini,
:/etc/php/7.0/cli/conf.d/15-xml.ini,
:/etc/php/7.0/cli/conf.d/20-apcu.ini,
:/etc/php/7.0/cli/conf.d/20-apcu_bc.ini,
:/etc/php/7.0/cli/conf.d/20-bz2.ini,
:/etc/php/7.0/cli/conf.d/20-calendar.ini,
:/etc/php/7.0/cli/conf.d/20-ctype.ini,
:/etc/php/7.0/cli/conf.d/20-curl.ini,
:/etc/php/7.0/cli/conf.d/20-dom.ini,
:/etc/php/7.0/cli/conf.d/20-exif.ini,
:/etc/php/7.0/cli/conf.d/20-fileinfo.ini,
:/etc/php/7.0/cli/conf.d/20-ftp.ini,
:/etc/php/7.0/cli/conf.d/20-gd.ini,
:/etc/php/7.0/cli/conf.d/20-gettext.ini,
:/etc/php/7.0/cli/conf.d/20-iconv.ini,
:/etc/php/7.0/cli/conf.d/20-intl.ini,
:/etc/php/7.0/cli/conf.d/20-json.ini,
:/etc/php/7.0/cli/conf.d/20-mbstring.ini,
:/etc/php/7.0/cli/conf.d/20-mysqli.ini,
:/etc/php/7.0/cli/conf.d/20-pdo_mysql.ini,
:/etc/php/7.0/cli/conf.d/20-phar.ini,
:/etc/php/7.0/cli/conf.d/20-posix.ini,
:/etc/php/7.0/cli/conf.d/20-readline.ini,
:/etc/php/7.0/cli/conf.d/20-shmop.ini,
:/etc/php/7.0/cli/conf.d/20-simplexml.ini,
:/etc/php/7.0/cli/conf.d/20-sockets.ini,
:/etc/php/7.0/cli/conf.d/20-sysvmsg.ini,
:/etc/php/7.0/cli/conf.d/20-sysvsem.ini,
:/etc/php/7.0/cli/conf.d/20-sysvshm.ini,
:/etc/php/7.0/cli/conf.d/20-tokenizer.ini,
:/etc/php/7.0/cli/conf.d/20-wddx.ini,
:/etc/php/7.0/cli/conf.d/20-xmlreader.ini,
:/etc/php/7.0/cli/conf.d/20-xmlwriter.ini,
:/etc/php/7.0/cli/conf.d/20-xsl.ini,
:/etc/php/7.0/cli/conf.d/20-zip.ini [[User:GeetikaCS|GeetikaCS]] ([[User talk:GeetikaCS|talk]]) 13:23, 5 April 2018 (UTC)
:What you're displaying are the enabled modules for the php cli. You must enable it on the web server (it depends if it's php-fpm or mod_php). See [[Manual:Php.ini]] [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 21:26, 5 April 2018 (UTC)

== Could not create directory problem ==

Hello,

when uploading a file I get the error message: Could not create directory "mwstore://local-backend/local-public/8/83".

Permission rights to image folder is 755.

Do you maybe know a solution for it. I am not super advanced in programming, so anything simply described would be greatly appreciated.

Thank you, Klemen [[Special:Contributions/80.110.33.184|80.110.33.184]] ([[User talk:80.110.33.184|talk]]) 11:54, 4 April 2018 (UTC)
:755 permissions will only allow create files and folders to the ''owner'' of that folder. Maybe the owner is not correct.
:You can try to set 777 permissions (to folders only! not files), see who's the owner of the new created files/folders, and then reset it back to 755 and change the owner accordingly.
:For example, set 777 to folders:
:<code> find /path/to/images -type d -exec chmod 777 {} \;</code>
:Set 755 permissions to folders:
:<code> find /path/to/images -type d -exec chmod 755 {} \;</code>
:Change owner
:<code> chown -R wikiuser /path/to/images</code> [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:27, 5 April 2018 (UTC)

== Infobox ==

Does someone know how to install the right floating infobox in the WikiMedia, like this green box on the right side: [[Extension:Capiunto]]

I searched everywhere and couldn't find the solution.

Thank you! [[Special:Contributions/80.110.33.184|80.110.33.184]] ([[User talk:80.110.33.184|talk]]) 13:05, 4 April 2018 (UTC)
:The "right floating infobox" uses [[Template:Extension]]. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 15:22, 4 April 2018 (UTC)
:Thank you. I don't really understand this page. Is this a extension I have to install?
:I tried to copy the code they asked on the top of the page and nothing happens... [[Special:Contributions/80.110.33.184|80.110.33.184]] ([[User talk:80.110.33.184|talk]]) 07:47, 5 April 2018 (UTC)
:[[Manual:Importing Wikipedia infoboxes tutorial]] [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:15, 5 April 2018 (UTC)

== Color of visited interwiki and external links ==
{{Flow summary|Resolved by replacing
<pre>.mw-body-content a:link { color: #0000FF; } /* normal unvisited links */
.mw-body-content a:link:active { color: #FF0000; } /* active links */
.mw-body-content a:link.new { color: #FF0000; } /* new links */
.mw-body-content a:link.interwiki { color: #3366BB; } /* interwiki links */
.mw-body-content a:link.external { color: #3366BB; } /* external links */
.mw-body-content a.interwiki:visited { color: #3366BB; }
.mw-body-content a.external:visited { color: #3366BB; }</pre>
with
<pre>.mw-body-content a:visited { color: #0645AD !IMPORTANT; }
.mw-body-content a.new:link { color: #cc2200 !IMPORTANT; }
.mw-body-content a.new:visited { color: #a55858 !IMPORTANT; }</pre>}}

Hey all. I want to make it so that my external links and interwiki links stay the same color regardless of whether they've been clicked on or not.

I've looked through [[w:Help:Link color|Help:Link color]] and [[Topic:Puw8f2bizr19rwti|this old Support desk topic]] and came up with the following code to add to my MediaWiki:Common.css page. However, my visited links are still a different color. What am I missing?

<pre>.mw-body-content a:link { color: #0000FF; } /* normal unvisited links */
.mw-body-content a:link:active { color: #FF0000; } /* active links */
.mw-body-content a:link.new { color: #FF0000; } /* new links */
.mw-body-content a:link.interwiki { color: #3366BB; } /* interwiki links */
.mw-body-content a:link.external { color: #3366BB; } /* external links */
.mw-body-content a.interwiki:visited { color: #3366BB; }
.mw-body-content a.external:visited { color: #3366BB; }</pre> [[User:Ttwinic|Ttwinic]] ([[User talk:Ttwinic|talk]]) 14:18, 4 April 2018 (UTC)
:One messy but effective way that I have found to work for achieving this, would be:<syntaxhighlight lang='text'>
a:visited { color: #0645AD !IMPORTANT; }
a.new:link { color: #cc2200 !IMPORTANT; }
a.new:visited { color: #a55858 !IMPORTANT; }
</syntaxhighlight>The above rules appear to be enough for visited interwiki links too. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 14:41, 4 April 2018 (UTC)
:Cool! That helps, though I don't yet know enough about CSS to understand how. What's the purpose of the <code>!IMPORTANT</code> part? [[User:Ttwinic|Ttwinic]] ([[User talk:Ttwinic|talk]]) 15:04, 4 April 2018 (UTC)
:The <code>!IMPORTANT</code> (or <code>!important</code>) part forces the rule to override all other relevant rules. For example, at one place an object is defined in red colour, while at another place it is orange, the CSS rule with the !important will have a higher priority over all other colour definitions.
:These should be used sparingly as they can cause much confusion in large projects. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 15:15, 4 April 2018 (UTC)

== Memorializing the lives of a couple who were actively involved in the civil rights movement of the 50s and later as well as the stopping the Vietnam Was ==
{{Archive top|result=Offtopic for MediaWiki software technology support, as this is about some website content. Please refer to https://en.wikipedia.org/wiki/Wikipedia:Teahouse|status=resolved}}

The couple is my parents who passed away in 1993 and 1994, Starting in the 1940s they were active in in helping Black people move to their town of Baldwin New York, which was all White. Later, they demonstrated against the Vietnam War. Their most notable accomplishment occurred in 1967-68 when a Black teacher in their high school of all White teachers and all White students was accused by a White female student of sexually molesting her. During those times, one might expect that the outcome would not turn out well for the Black teacher, regardless of whether or not it was true. My parents knew the Black teacher and after confirming that the allegations had to be false, mobilized the community and other teachers in the school to expose the falsehood and save his job. In the end, the accuser admitted that she made it all up in an attempt to get the Black teacher out of her school. This was featured on the cover and in an article in the March 1968 issue of '''The Ladies Home Journal'''.

Currently there are six (6) people who have firsthand knowledge of their lives and work. These include myself (their oldest son (my brother passed away in 2000), my sister-in-law, and their four grandchildren. We have decided to create something on the Internet to memorize their lives, and the difference they made in other people's lives, for future generations and others. We think Wikipedia would be the best platform to present this information, which would include essays about them written by the six of us, their writings, The Ladies Home Journal cover and article, and pictures. '''However, I do not know if this would be appropriate under Wikipedia's guidelines and rules. I am sending this to the Support Desk to help determine whether or not we could put this on Wikipedia.''' I would appreciate a response as we begin to write, gather information, scan put everything together as to using Wikipedia.

Thank you. [[User:Bmperlman39|Bmperlman39]] ([[User talk:Bmperlman39|talk]]) 14:45, 4 April 2018 (UTC)
:This support desk is primarily for technical queries regarding the software which runs Wikipedia. For content on Wikipedia, you will get a much quicker and informed response at [[w:Wikipedia:Teahouse]]. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 15:18, 4 April 2018 (UTC)
{{Archive bottom}}

== i cant join for free ??? ==

i cant join for free keeps rejecting all my passwords i try to set? [[Special:Contributions/66.171.106.235|66.171.106.235]] ([[User talk:66.171.106.235|talk]]) 15:10, 4 April 2018 (UTC)
:Please tell us which website (a full link, please) you refer to, and why you think that some website rejects all your passwords - is there some error message, or what happens? [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 15:24, 4 April 2018 (UTC)

== Media Wiki Logon issue ==

I have Media Wiki installed on server 2016. When I access the webpage and try to login as Admin, or try to create an account I get Fatal Exception of type "BadMethodCallException" Any ideas on how to fix this? [[Special:Contributions/208.38.247.133|208.38.247.133]] ([[User talk:208.38.247.133|talk]]) 15:25, 4 April 2018 (UTC)
:We'll need a stack trace of the error to see where the error is being producing. See [[Manual:How to debug]] to see what do you need in order to improve the verbosity of that error message. [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:21, 5 April 2018 (UTC)

== Mobile editing ==

Hi,

on only one page of my site, there ist no "pencil" to edit the text with smartphones. I don´t know why. Have u any idea?

Thanks, Mitch [[User:Evetro|Evetro]] ([[User talk:Evetro|talk]]) 19:20, 4 April 2018 (UTC)
:The page may be protected [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:19, 5 April 2018 (UTC)
:On Desktop i can edit the page [[User:Evetro|Evetro]] ([[User talk:Evetro|talk]]) 09:37, 5 April 2018 (UTC)
:In ''Console'' section of the browser developer tools (F12), is there any error displayed? [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 17:02, 5 April 2018 (UTC)

== Error 500 when a new, non-default skin is added to Localsettings.php ==

I got an error 500 after adding new skins to my LocalSettings.php. This has only occurred with additional skins that are NOT one of four default skins (Cologne Blue, Modern, MonoBook, Vector), and I appeared to have used the correct skin addition method for my current MediaWiki version. I made this wiki with Webhostface, and it runs on a currently supported version. However, I had no problems with adding user rights or enabling extensions.

I have not found a solution to fix this error, and I need some help fixing the error 500 on my wiki. Is there any way to fix this strange error and enable the skins without getting any more errors? Thank you. [[User:Newman2|Newman2]] ([[User talk:Newman2|talk]]) 21:42, 4 April 2018 (UTC)
:It depends... In order to help you further, please answer the following questions:
:*Which skin did you try to add?
:*Which version of MediaWiki are you using?
:*How exactly does the line look like, which you added to LocalSettings.php? [[Special:Contributions/2001:16B8:1022:4F00:D9C7:A745:8FE2:7F2B|2001:16B8:1022:4F00:D9C7:A745:8FE2:7F2B]] ([[User talk:2001:16B8:1022:4F00:D9C7:A745:8FE2:7F2B|talk]]) 22:12, 4 April 2018 (UTC)
:-I was adding two skins, one of them being Monaco and another (being a skin I created) called Candy.
:-I am using MediaWiki 1.30
:-The line looks exactly like this (Candy is the skin that I added):
:<nowiki>#</nowiki> Enabled skins.
:<nowiki>#</nowiki> The following skins were automatically enabled:
:wfLoadSkin( 'Candy' );
:wfLoadSkin( 'CologneBlue' );
:wfLoadSkin( 'Modern' );
:wfLoadSkin( 'MonoBook' );
:wfLoadSkin( 'Vector' ); [[User:Newman2|Newman2]] ([[User talk:Newman2|talk]]) 22:16, 4 April 2018 (UTC)
:A 500 error message is not helpful at all. You'll need to look at server error logs to see a meaningful error message. See [[blank page]] [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:19, 5 April 2018 (UTC)
:What do you mean by a meaningful error message? I'm looking only to fix the error on my wiki. [[User:Newman2|Newman2]] ([[User talk:Newman2|talk]]) 13:16, 5 April 2018 (UTC)
:By the way, I could not find enough information on the error 500. [[User:Newman2|Newman2]] ([[User talk:Newman2|talk]]) 13:24, 5 April 2018 (UTC)
:On which skin did you base the Candy skin? Is it basically a copy of the Vector skin, which you then modified? Or is it based on the Monaco skin?
:> I could not find enough information on the error 500.
:That is why Ciencia is asking for more information. This information should be in the error log of the webserver.
:After looking at the Monaco skin,
:https://github.com/dantman/monaco-port
:this skin does '''not''' support the line with wfLoadSkin(), because it is still using the old skin architecture. The Monaco skin has to be included using a line with ''require_once "$IP/skins/monaco/monaco.php";''.
:Does the error happen for both skins, Candy and Monaco?
:Apart from that, the last changes to the Monaco skin have been done four years ago. Maybe the skin is no longer working with current versions of MediaWiki. [[Special:Contributions/2001:16B8:10A0:DB00:198F:24E4:C3ED:88E5|2001:16B8:10A0:DB00:198F:24E4:C3ED:88E5]] ([[User talk:2001:16B8:10A0:DB00:198F:24E4:C3ED:88E5|talk]]) 15:46, 5 April 2018 (UTC)
:Candy is a copy of the MonoBook skin. And yes, the error happens for both Candy and Monaco. [[User:Newman2|Newman2]] ([[User talk:Newman2|talk]]) 17:10, 5 April 2018 (UTC)

== How to Include Page Sections in DPL? ==
{{Archive top|result=Here's transclude using [[Extension:DynamicPageList3]]. <pre>
{{#dpl:

|category = Deep-Dives

|include = #Rebuttal

}}
</pre>It returns a bulleted list of all page titles in category "Deep-Dives", including all body text in page section called "Rebuttal". There are no errors for pages which don't have that section.

'''Notes:'''

* The [https://help.gamepedia.com/DPL:Source_and_Installation gamepedia.com manual] shows the older "require_once" installation syntax. The [[Extension:DynamicPageList3|mediawiki.org extension page]] contains the newer "wfLoadExtension" syntax.
* The output list displays a link to a non-existent Template at the top of the list. This can be suppressed by creating "Template:Extension DPL" and saving it as blank. It can even be deleted at this point, and it's display will continue to be suppressed in the DPL. More info on how to use that template to capture info when you have several DPL pages.

Since Extension:DynamicPageList3 description says it's re-written from the ground up, with improved performance, i don't see a strong reason to investigate the other two DPL extensions.|status=resolved}}

I'm looking at these three DPL extensions. Supposedly, some of or all them can display page sections, but i can't see how that's done. Ideally, i'd like to get that working with all of 'em, so i can compare performance and other features.

Can anyone share section-inclusion examples?

-thx

[[Extension:DynamicPageList3]]

[[Extension:DynamicPageListEngine]]

[[Extension:DynamicPageList (Wikimedia)]] [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 02:28, 5 April 2018 (UTC)
:For [[Extension:DynamicPageList3]], see [https://help.gamepedia.com/DPL:Parameters:_Criteria_for_Page_Selection#Select_articles_based_on_TITLE DPL:Parameters:_Criteria_for_Page_Selection#Select_articles_based_on_TITLE]. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 17:11, 5 April 2018 (UTC)
:Thx! Your link is for page-selection, but I'm actually looking to include page SECTION.
:Your link led me to the right place:
:https://help.gamepedia.com/DPL:Example_-_Show_Sections_from_an_Article [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 21:06, 5 April 2018 (UTC)
:The link I gave ''also'' uses the exact same example (with different variable names) for including page SECTION. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 22:17, 5 April 2018 (UTC)
:Fantastic. This works great! Here's my transclude:<syntaxhighlight lang='text'>
{{#dpl:
|category = Rebuttal_Deep-Dives
|include = #Rebuttal
}}
</syntaxhighlight>It returns a bulleted list of all page titles in category "Rebuttal_Deep-Dives", including all body text in page section called "Rebuttal".
:It displays a link to a non-existent Template at the top of the list. This can be suppressed by creating "Template:Extension DPL" and saving it as blank. It can even be deleted at this point, and it's display will continue to be suppressed in the DPL. [https://help.gamepedia.com/DPL:General_Usage_and_Invocation_Syntax#Implicit_link_to_Template:Extension_DPL More info].
:Since [[Extension:DynamicPageList3]] description says it's re-written from the ground up, with improved performance, i don't see a strong reason to investigate the other two DPL extensions. [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 22:50, 5 April 2018 (UTC)
{{Archive bottom}}

== Upgrade MySQL to version 5.5.8 ==
{{Archive top|result=Was a mistake.|status=resolved}}

MediaWiki 1.30 [[Release notes/1.30#Compatibility|needs]] MySQL version 5.5.8. At the moment we use 5.5.59. How can I update our MySQL installation? We use Ubuntu 14. [[User:Waanders|Waanders]] ([[User talk:Waanders|talk]]) 11:37, 5 April 2018 (UTC)
:Oops, 5.5.8 is older than 5.5.59 I see. Thought version 5.5.59 was in between 5.5.5 and 5.5.6 ... [[User:Waanders|Waanders]] ([[User talk:Waanders|talk]]) 11:42, 5 April 2018 (UTC)
{{Archive bottom}}

== customer service ticket or help request? ==

Hello, how would I put in a customer service ticket or help request? [[Special:Contributions/192.31.106.35|192.31.106.35]] ([[User talk:192.31.106.35|talk]]) 15:21, 5 April 2018 (UTC)
:You are already on the Support Desk for the MediaWiki software here, if your question is about the MediaWiki software itself. :) [[User:Malyacko|Malyacko]] ([[User talk:Malyacko|talk]]) 17:05, 5 April 2018 (UTC)

== Create Administration account ==

How do I create multiple administration accounts in media wiki? [[Special:Contributions/208.38.247.133|208.38.247.133]] ([[User talk:208.38.247.133|talk]]) 15:57, 5 April 2018 (UTC)
:The easiest way is to log in with a bureacrat account and to grant user rights through the wiki page [[Special:UserRights]] of your wiki.
:Using the maintenance script [[Manual:createAndPromote.php]] from the shell is the second way I know of. [[Special:Contributions/2001:16B8:10A0:DB00:84B7:451E:1D50:3CA1|2001:16B8:10A0:DB00:84B7:451E:1D50:3CA1]] ([[User talk:2001:16B8:10A0:DB00:84B7:451E:1D50:3CA1|talk]]) 16:50, 5 April 2018 (UTC)

== Why many wikis running a outdated version? ==

Many wiki (about 90%) is running a outdated version of Mediawiki. Why the webmasters of sites won't update Mediawiki? [[Special:Contributions/2A02:C7F:963F:BA00:5DF7:13F1:AFD3:B4B2|2A02:C7F:963F:BA00:5DF7:13F1:AFD3:B4B2]] ([[User talk:2A02:C7F:963F:BA00:5DF7:13F1:AFD3:B4B2|talk]]) 18:49, 5 April 2018 (UTC)
:Because there is no need to update if everything works fine [[User:Fokebox|Fokebox]] ([[User talk:Fokebox|talk]]) 06:46, 6 April 2018 (UTC)
:the release manager issued that only up-to-date version should be used in production wikis but the wiki owners says no. [[Special:Contributions/2A02:C7F:963F:BA00:78E9:F008:425B:BC2A|2A02:C7F:963F:BA00:78E9:F008:425B:BC2A]] ([[User talk:2A02:C7F:963F:BA00:78E9:F008:425B:BC2A|talk]]) 06:49, 6 April 2018 (UTC)

== integrate MW login with project ==

How do I make logged in users from my project automatically also logged in in MediaWiki? [[Special:Contributions/91.51.216.67|91.51.216.67]] ([[User talk:91.51.216.67|talk]]) 20:09, 5 April 2018 (UTC)

== Cannot log in after mediawiki installation ==

I have 4 themed wikis under my multimedia company. I recently wanted to start a 5th about the open movements. I bought the domain and installed mediawiki to find that I cannot log into the admin account. I have reinstalled it and had the same problem. I make it to the password page, i enter my password, and a white screen with a 403 error and a message saying i do not have access comes up. I am afraid I will be cut off from my other 4 wikis in the same fashion once i lose my cookies.

this is the wiki location: https://openmovement.wiki/

Here is a screen of the message I get: https://openmovement.wiki/images/forbidden-wiki-message.png

I am using mediawiki version 1.29.2 [[User:PW1984|PW1984]] ([[User talk:PW1984|talk]]) 20:14, 5 April 2018 (UTC)
:I ended up gaining access by requesting a password change, I was able to log in through such into the open movement wiki. I know my password was accurate. So something is going on. I have tried to change my email on my current wikis on my admin account, getting the same error I have since changed emails so this is pretty alarming... [[User:PW1984|PW1984]] ([[User talk:PW1984|talk]]) 21:07, 5 April 2018 (UTC)
:That "Forbidden" error is not triggered by MediaWiki. It's triggered by the webserver itself. It seems to have some special anti-spam rule or similar like [[ModSecurity]]. [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 21:21, 5 April 2018 (UTC)

== my cities are gone ==

My cities are gone when I sign in to Elvenar

I've logged out of my server and logged out of the game with not finding my cities. I have tried all three of the cities listed and they are the starting cities. [[Special:Contributions/2601:603:1E7F:C928:2579:FC6:A162:D0E7|2601:603:1E7F:C928:2579:FC6:A162:D0E7]] ([[User talk:2601:603:1E7F:C928:2579:FC6:A162:D0E7|talk]]) 02:00, 6 April 2018 (UTC)

Topic:Uamkoo09yfnt3h7n

2018-04-04T08:22:29Z

213.61.254.68 (talk) commented on "mediawiki smw-editpage-annotation-enabled editform to large" (Hello, my EditForm is to large and the save button is out of my screen. I must scroll down, to press the button. After installing Smenati...)

Project:Support desk/Flow/2018/04

2018-04-04T08:22:29Z

213.61.254.68: /* mediawiki smw-editpage-annotation-enabled editform to large */ New section

{{flow imported revision}}
{{Project:Support desk/Header}}my account has been hacked by jack ostroffi want my account back Rita Nachtigall

== How to get "Add topic", "Start a new topic", or "Add Section" on Content Page (not Talk), Without VisualEditor? ==

How to get "Add topic", "Start a new topic", or "Add Section" on Content Page (not Talk), Without VisualEditor?

thx [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 00:05, 1 April 2018 (UTC)
:Use <nowiki>__NEWSECTIONLINK__</nowiki> ([[Help:Magic words]]) [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:21, 3 April 2018 (UTC)

== TinyMCE infinite loop error and freeze ==

I have tried several Mediawiki versions, from 1.26.4 to 1.31-alpha and in every version i get infinite loop error when i go to "Show preview" and it freezes when i go to "Save page".... Is there anything i can do about that? [[User:Darkwarrior92|Darkwarrior92]] ([[User talk:Darkwarrior92|talk]]) 15:20, 1 April 2018 (UTC)

== What is {{Draft}} Tag? ==
{{Archive top|result=<pre>
{{Draft}}
</pre>by itself is not an extension. It is transcluding/rendering the page Template:Draft. The Template contains the "under-construction" image, the "This page is a draft" message, and other behind-the-scenes things, such as the use of Template:Mbox.

Normally, it has to be manually added and removed, but can be automatically added with a bot, a create-page button, or a boiler plate extension.|status=resolved}}

[[Annoying little bugs|This page]] says "This page is currently a draft." It's source contains <pre>
{{Draft}}
</pre>How is this done? [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 19:39, 1 April 2018 (UTC)
:It is transcluding/rendering the page [[Template:Draft]]. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 20:05, 1 April 2018 (UTC)
:It appears the Template contains nothing except the "under-construction" image, and the "This page is a draft" message, correct?
:[[Template:Draft]]
:And the transclude has to be manually added and removed, right? It's not automatically displayed based on namespace, correct? [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 22:03, 1 April 2018 (UTC)
:That is what the template appears to the reader, but there are other behind-the-scenes things, such as the use of [[Template:Mbox]], too.
:To automatically add the template a bot will have to be used, or a create page button which pre-fills some of the content on the page, or one of those boiler plate extensions, which based on some rules pre-fill content on the page. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 04:31, 2 April 2018 (UTC)
{{Archive bottom}}

== Preventing articles from appearing in maintenance pages ==

Is there a way to have certain pages not displayed in maintenance special pages? For example, to prevent an uncategorized page from appearing in Special:UncategorizedPages. Or a page with some broken files to not appear in Category:Pages with broken files links. Thanks! [[Special:Contributions/2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B|2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B]] ([[User talk:2001:16B8:2B53:3000:49C0:7AD:DF9F:9D2B|talk]]) 21:11, 1 April 2018 (UTC)

== Bug? New Page is Visible Before Approval by ApprovedRevs ==

To replicate problem:
# Login as user '''without''' `approverevisions` permission
# Create a new page. Enter some random text. Save the new page.
# Log out.
# Return to new page.
# View page history: the ApprovedRevs link says "approve", indicating the page has not yet been approved.
# Switch to `Read` mode on the page.

'''Expected result:''' The page contents should not be visible, because it has not be approved yet.

'''Actual result:''' The page contents are visible.

{{FlowMention|Yaron Koren}} [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 22:38, 1 April 2018 (UTC)
:[[Extension:Approved_Revs#Displaying_unapproved_pages_as_blank]] [[User:Wargo|wargo]] ([[User talk:Wargo|talk]]) 09:37, 2 April 2018 (UTC)
:you're right, i forgot about that config.
:i'm exploring if a mod involving Draft namespace could be done simply:
:- User manually creates new page in Draft namespace.
:- On first rev approval, auto-move page to "Main" namespace. [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 15:59, 2 April 2018 (UTC)

== bad CSS cuts off descenders ==

I'm a routine user of ArchLinux's and openSUSE's wikis. For many web sites I routinely use, I create user styles to override common idiotic site styles, e.g. non-default space-wasting leading. Font designers know how to design their fonts for optimal use. Extra leading is entirely unnecessary when appropriate line lengths, font size and contrast are declared.

Mediawiki's load.php includes the following:

.diff-addedline .diffchange, .diff-deletedline .diffchange {padding: 0.25em 0;}

The result of this rule causes descenders on diff pages where it is applied to be cut off in all Gecko versions tested, among which RV17, RV52 and RV59, on desktops using 108 DPI and 120 DPI, and browser default font settings of 18px and 20px. Thus with my line-height override to use *normal* leading, I found that an override to the above declaration that reduces the padding to 0 enables seeing all descenders. [[User:Mrmazda|Mrmazda]] ([[User talk:Mrmazda|talk]]) 08:10, 2 April 2018 (UTC)

== Get wiki's default timezone in JS? ==

I need to get the wiki's default timezone offset in order to correct the timestamp which the API returns, which for some reason ignores the wiki's timezone and is always in UTC, unlike magic words like <code>CURRENTTIMESTAMP</code> which use the wiki's timezone.

I know the offset is included in the <code>user.defaults</code> module, but there seems to be no way to access it. I can only retrieve the user's options, which does not include the default value if the user has changed the offset from the default. So far the only way seems to make another API request to the siteinfo API, which is annoying when the information is already included in the page. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 11:47, 2 April 2018 (UTC)
:Note, you can combine the two api requests into one if your initial api request is using action=query, as action=query allows you to specifiy both the meta=siteinfo and prop=whatever at the same time.
:I don't think there's any other way to fetch this data. FWIW, CURRENTTIMESTAMP is supposed to be always UTC (vs LOCALTIMESTAMP which is server timezone) [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:28, 3 April 2018 (UTC)
:Ah sorry I got mixed up with the magic words, it is <code>REVISIONTIMESTAMP</code> that uses the server timezone. Good tip about combining the requests, always forget about that, thanks. Still would be nice not to have to download all that extra data. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 03:55, 4 April 2018 (UTC)

== [SOLVED] images 404 ==
{{Archive top|status=resolved}}

Hi, I moved MW from root (<code>/</code>) to (<code>/w</code>) directory and upgrade from 1.20 to 1.30
Html pages are normally opened http://montibus.org/wiki/ old wiki url: http://wiki.mountainclub.ru/

My <code>/.htaccess</code> config

<pre>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^wiki/(.*)$ w/index.php?title=$1 [PT,L,QSA]
RewriteRule ^wiki/*$ w/index.php [L,QSA]
RewriteRule ^wiki$ w/index.php [L,QSA]
</pre>

My <code>/w/images/.htaccess</code> config
<pre>
# Protect against bug T30235
<IfModule rewrite_module>
RewriteEngine On
RewriteOptions inherit
RewriteCond %{QUERY_STRING} \.[^\\/:*?\x22<>|%]+(#|\?|$) [nocase]
RewriteRule . - [forbidden]
# Fix for bug T64289
Options +FollowSymLinks

</IfModule>
</pre>

Part of my <code>/w/LocalSettings.php</code>

<pre>
$wgScriptPath = "/w";
$wgArticlePath = "/wiki/$1";
</pre>

What's wrong? [[Special:Contributions/2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62|2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62]] ([[User talk:2A02:6B8:0:3903:51C7:D5DE:9F7B:2E62|talk]]) 13:24, 2 April 2018 (UTC)
:There problem, that images not opened,
:200 Normal: http://wiki.mountainclub.ru/images/8/89/Андрей_Антонов.jpg
:404 Not Found: http://montibus.org/w/images/8/89/Андрей_Антонов.jpg [[User:EAndreyF|EAndreyF]] ([[User talk:EAndreyF|talk]]) 14:24, 2 April 2018 (UTC)
:SOLVED. There were file permissions error. 620 change to 644 [[User:EAndreyF|EAndreyF]] ([[User talk:EAndreyF|talk]]) 04:51, 3 April 2018 (UTC)
{{Archive bottom}}

== Quickly Share CSS to Community? ==

What's best simple way share with the community, my preferred CSS tweak for this site?<pre>
#p-personal{
position:fixed;
background: rgb(255,255,255);
}
</pre>i assume would work on any MW site.

Keeps notification bar on top when scrolling.

<nowiki>https://preview.ibb.co/jOG8S7/fix_mw_bar.png</nowiki>

(how to embed images here?) [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 13:28, 2 April 2018 (UTC)
:https://userstyles.org/ ? [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:16, 3 April 2018 (UTC)

== How to change meta keywords ==

Is it possible to add, or change HTML meta keywords on pages? [[User:NeedAGoodUsername|NeedAGoodUsername]] ([[User talk:NeedAGoodUsername|talk]]) 15:56, 2 April 2018 (UTC)

== Can I update a wiki as a bureaucrat, or do I need access to the actual server installation? ==

As I understand it, to update a wiki I need access to the actual server installation (not physically, I can connect to its cPanel or FTP in or whatever), right? I can't just update it as a bureaucrat? [[User:Banaticus|Banaticus]] ([[User talk:Banaticus|talk]]) 19:35, 2 April 2018 (UTC)
:Yes. At the very minimum you need ftp access (To replace the files). Having ssh access is even better. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:15, 3 April 2018 (UTC)

== How to Hardcode a Namespace in Inputbox Create Function? ==

Extension:InputBox provides a GUI to create new pages, but pages are created in the default namespace.

[[Topic:T2l8bu51332l0tzy]] offers a mod for a namespace dropdown-picker. (not sure this mod is compatible with current releases of MW and InputBox).

But, how to hardcode the target namespace?

thx [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 21:21, 2 April 2018 (UTC)
:Use prefix= [[User:Ciencia Al Poder|Ciencia Al Poder]] ([[User talk:Ciencia Al Poder|talk]]) 09:15, 3 April 2018 (UTC)

== Necessity to install install Visual C++ Redistributable for the Visual Studio 2015 ==

Hello.

We currently have on our server the Wiki version 1.26.0 and PHP version 5.6.26 been installed.

Based on your instruction available on [[Manual:Upgrading]] it looks like we will do an upgrade to Wiki 1.30.0 and PHP v.7.1.15 or more recent.

I know that that our current PHP 5.6.26 uses '''''Visual C++ Redistributable for the Visual Studio 2011, and new PHP 7.1.x requires to install Visual C++ Redistributable for the Visual Studio 2015.'''''

QUESTION: Should I install on our wiki server the '''''Visual C++ Redistributable for the Visual Studio 2015''''' first before downloading MediaWiki tarball or will it re required on the step by running the command php update.php, or will it not be required at all?

Please let us know. Thank you! Alex [[Special:Contributions/198.232.184.254|198.232.184.254]] ([[User talk:198.232.184.254|talk]]) 23:33, 2 April 2018 (UTC)
:So first of all, MediaWiki 1.30 only requires PHP 5.5.9. Thus 5.6.26 is new enough for MediaWiki 1.30, so you do not have to upgrade PHP
:Second, You would only need visual studio if you were compiling PHP by hand. Which would be unusual. Most people get precompiled php packages via your operating system's package manager (e.g. apt, yum, etc) or they download a precompiled binary from the PHP website. [[User:Bawolff|Bawolff]] ([[User talk:Bawolff|talk]]) 07:14, 3 April 2018 (UTC)
:Hello!
:Thank you so much, Bawolff for your comment.
:So, am I correct that if we have PHP 5.6.26 and will upgrade our Wiki from 1.26.0 to 1.30.0 then the command php update.php will not upgrade PHP to the newer version, right?
:Thank you! [[Special:Contributions/198.232.187.14|198.232.187.14]] ([[User talk:198.232.187.14|talk]]) 17:58, 3 April 2018 (UTC)
:<code>php update.php</code> doesn't update PHP (or MySQL etc.), only the MediaWiki installation. [[User:AhmadF.Cheema|AhmadF.Cheema]] ([[User talk:AhmadF.Cheema|talk]]) 20:38, 3 April 2018 (UTC)

== "Thank" fails on this mobile site ==

I get:

<pre>Send thanks
Do you want to publicly send thanks for this comment?

The postid parameter must be set.</pre> [[User:Johnywhy|Johnywhy]] ([[User talk:Johnywhy|talk]]) 12:31, 3 April 2018 (UTC)

== How to limit who can add a category? ==

I would like only bureaucrats and administrators the ability to add a category. Is this possible. i would assume so [[User:Jamesghansen|Jamesghansen]] ([[User talk:Jamesghansen|talk]]) 22:11, 3 April 2018 (UTC)
:You could probably use abuse filters to prevent people from adding particular categories to a page, but this isn't necessarily the most reliable, and could cause issues with people editing near the category, as it will think they are changing it. [[Special:Contributions/110.149.143.35|110.149.143.35]] ([[User talk:110.149.143.35|talk]]) 03:42, 4 April 2018 (UTC)

== Funny problem regarding special chars such as á and ñ - II ==

Hi:

I've been experiencing difficulties with a new MW site and I've done everything at my reach to solve the situation.

I have a 1.29 installation facing a lot of problems with collation. I've installed several times trying different combinations (e.g. binary /utf8, etc) but special characters are not working at all (accented ones such as á, é and others like "ñ"). My tech stack (L: 2.6.32-696.23.1.el6.centos.plus.x86_64, A:2.4.18, MySQL:10.0.34-MariaDB, PHP 5.5.32)

I reviewed the charset in DB and it seems ok (utf8_unicode_ci) and db tables are InnoDB/Binary. I've tried utf8_general_ci, swedish and latin but nothing is working.

After several days trying to make it work i did something different: I used ISO-8859-1 (as a test) from the text editor and when clicking on preview the accented words looked fine! (e.g. when I wrote "Observaci&oacute;n" MW showed correctly "Observación" in the main area).

I've been looking around here for suggestions and I've tried most of them. To avoid a corrupted DB, after the changes (charsets / collations / Localsettings, etc) I've re-installed and recreated both the DB and configurations, pretty much with the same results.

So, if you can provide with a solution it'll be much appreciated.

Regards

Rick [[User:Rickstrat07|Rickstrat07]] ([[User talk:Rickstrat07|talk]]) 00:36, 4 April 2018 (UTC)

== E-mail problems ==

Hi to all, I have some problems with SMTP on my MediaWiki installation. I installed the pear chain, and configured Localsetting.php, but when I try to send emails (such as at the creation of a new user) the browser remains waiting some tens of seconds and then go on without errors, but I don't receive the mail... [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 07:15, 4 April 2018 (UTC)
:This is my configuration:
:<nowiki>#</nowiki>Configure SMTP
:$wgEnableEmail="true";
:$wgEnableUserEmail="true";
:$wgEmergencyContact="wiki@mydomain.it";
:$wgPasswordSender="wiki@mydomain.it";
:$wgNoReplyAddress="myname@gmail.com";
:$wgSMTP = array(
:'host' => "172.20.1.84",
:'IDHost' => "mydomain.it",
:'port' => 25,
:'auth' => false
:);
:$wgShowExceptionDetails = true; [[User:Stefano664|Stefano664]] ([[User talk:Stefano664|talk]]) 07:17, 4 April 2018 (UTC)

== mediawiki smw-editpage-annotation-enabled editform to large ==

Hello,

my EditForm is to large and the save button is out of my screen. I must scroll down, to press the button.

After installing SmenaticMediaWiki there is a smw-editpage-annotation-enabled-section in the Firefox DebugConsole, that push the EditForm a little bit down.

I need a option to reduce the size of the editform, OR i need the option to collapsible the smw-editpage-annotation-enabled-section.

Can anyone help me?

I do not know the right section, here or in the extension-page: [[Topic:Uamkmg06h8y3oukz]] [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 08:22, 4 April 2018 (UTC)

Topic:Uamkmg06h8y3oukz

2018-04-04T08:21:23Z

Extension talk:Semantic MediaWiki/Archive 2/Flow export

2018-04-04T08:21:23Z

213.61.254.68: /* mediawiki smw-editpage-annotation-enabled editform to large */ New section

{{flow imported revision}}
'''<big><span style="color: orange">The best way for getting support for Semantic MediaWiki is to post to its user mailing list.</span></big>''' Comments made below are not very well monitored by the developers. There are various options for making yourself heard:

* If you have a usage question, please post them to the [https://sourceforge.net/projects/semediawiki/lists/semediawiki-user SMW support mailing lists] ([https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/ archives]).
* If you found a bug or want to propose a new feature, please file it at [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues GitHub]. Bugs and requests are regularly considered by core developers and have a great impact on the future development of SMW.
* If you want to contribute to the development, please contact the development community at the [https://sourceforge.net/projects/semediawiki/lists/semediawiki-devel SMW developers' mailing list] ([https://sourceforge.net/p/semediawiki/mailman/semediawiki-devel/ archives]).

When asking for help or describing bugs, '''do not forget''' to provide necessary details about your configuration, version details for all relevant components, information about other extensions that are used, and, if possible, a URL where the problem can be seen. See the help page on '''[[semantic-mw:Help:Reporting bugs|reporting bugs]]''' for detailed information.

The below talk page is most useful for comments regarding the wiki page, but of course you may do as you like (it's a wiki, after all).

→ [[Extension talk:Semantic MediaWiki/Archive|previous talk on this page]]

== PHP Fatal error: Class 'SiteConfiguration' not found in updateArticleCount.php on line 59 ==

Moved to wiki support instead of SMW support. Sorry. [[Special:Contributions/85.80.205.112|85.80.205.112]] 11:42, 2 March 2013 (UTC)

== Syntax highlight lang for documenting Semantic MediaWiki code ==

This seems to work quite well:
<nowiki><syntaxhighlight lang="bibtex"></nowiki>
[[Extension_talk:SyntaxHighlight_GeSHi#lang_for_Mediwiki_Code_.3F|Thanks]] to [[User:Technical_13|Technical 13]] [[User:Daniel K. Schneider|Daniel K. Schneider]] ([[User talk:Daniel K. Schneider|talk]]) 11:15, 28 June 2013 (UTC)

== SMW "future-safe"? ==

Hello,

your extension SMW is great! I would like to integrate it into our private wiki.

Is the use "future-safe"?
What are your future plans? Will developing go further when new releases of mediawiki appear ... e.g. the next 10 years?
Or would you recommend to use the extension Dynamic Pagelist instead?

Regards
Janis --[[Special:Contributions/87.186.50.77|87.186.50.77]] 07:46, 2 October 2013 (UTC)
:Hi Janis,
:SMW is probably one of my main reasons for sticking with MediaWiki. If you look at the website (http://semantic-mediawiki.org) and the mailing list (https://lists.sourceforge.net/lists/listinfo/semediawiki-user), you'll find that the extension as well as related extensions like SF are actively supported and enjoy a lively user community - quite contrary I'd say to the bulk of MW extensions that you'll find here, so I know where your question is coming from. No one can tell where we will be ten years from now, but I don't think you'll regret it. If you have any questions regarding the future direction of SMW, the mailing list would be the place to ask. [[User:Cavila|Cavila]] <span style="font-size:65%;">(MW 1.19.7, MySQL 5.1.66, Php 5.3.3-7, SMW 1.8, SF 1.5.2}</span> 08:37, 2 October 2013 (UTC)

== Upgrading SMW old version ==

Hi,
My production wiki is on ver 1.15.1 and it has smw 1.0.1 installed. I am trying to test an upgrade in the dev environment which is mw 1.19.9 with smw 1.8. The extension has installed successfully and is showing up properly in special:version. But the pages using it are breaking. I was wondering about how i should go about upgrading smw to 1.8. Are the old SMW_settings and SMW_Globalsettings compatible with the latest install? Should the upgrade be done in steps? I was reading and I found that there have been several schema changes. Any help is greatly appreciated

Thanks in advance.

Arnab [[Special:Contributions/81.245.110.27|81.245.110.27]] 17:54, 22 December 2013 (UTC)
:Oh, this is quite an archaic installation. Hmm, did you completely [[semantic-mw:Help:Repairing_SMW's_data|rebuild your store and data]] (or [[semantic-mw:Help:Installation 1.8.0#Upgrading existing installations|upgrading to 1.8.x]])? Perhaps you are still using the "<code>:=</code>" syntax for annotating properties. I think this does not longer work in recent versions. The best way to ask questions about SMW is to use the [[semantic-mw:Semantic MediaWiki mailing lists]]. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:19, 31 December 2013 (UTC)
::Hi,
::<code> This is how I worked it out. I went with upgrading from 1.0.1 to 1.1 to 1.2 to 1.3 to 1.4 to 1.5 to 1.6 to 1.7.1.</code>
::So i did the upgrade in steps. I couldn't figure out a way of going directly from 1.0.1 to 1.8. It was lengthy but it worked out properly.
::Arnab [[Special:Contributions/81.247.85.62|81.247.85.62]] 14:22, 5 January 2014 (UTC)
:::Glad it worked out. :) [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:49, 5 January 2014 (UTC)

== What are the "issues" that break a wiki when you remove the extension? ==

Extension has been installed but never used and trying to reduce overhead by removing several unused extensions. If the extension wasn't used, is SMW_setup.php --delete enough? [[User:Skunark|Skunark]] ([[User talk:Skunark|talk]]) 02:40, 30 December 2013 (UTC)
:This should be enough. You can verify in your database if the SMW related tables are still there. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:11, 31 December 2013 (UTC)

== Logo ==

Hi,
Is there a way to control the enabling and disabling of the SMW logo at the right bottom of the page.

Arnab [[Special:Contributions/81.247.85.62|81.247.85.62]] 14:40, 5 January 2014 (UTC)
:The best way to ask questions about SMW is to use the [[semantic-mw:Semantic MediaWiki mailing lists]]. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:48, 5 January 2014 (UTC)

== Updated Semantic Mediawiki but cant run update.php, Err. SEMANTIC MEDIAWIKI MUST BE INSTALLED TO RUN SEMANTIC FORMS ==

I used composer to update my semantic mediawiki version. The installation ran successfully but I cant update.php. My current SMW version in 1.8.05. Running update gives me an error that says SEMANTIC MEDIAWIKI MUST BE INSTALLED TO RUN SEMANTIC FORMS. I did try placing the enableSemantics() call at the end of LocalSettings.php file. Please help. Thanks in advance [[User:Cmm9888|Cmm9888]] ([[User talk:Cmm9888|talk]]) 08:23, 25 August 2014 (UTC)
:Try uninstalling Semantic Forms (and any other SMW-requiring extensions) before doing the update. [[User:Yaron Koren|Yaron Koren]] ([[User talk:Yaron Koren|talk]]) 16:56, 28 August 2014 (UTC)

== Reunion instead of intersection ==

Hey guys,
Really would appreciate any help!
If I write <nowiki>{{#ask: [[Category:Cat1]] [[Category:Cat2]]</nowiki> it will give me an intersection between Cat1 and Cat2.
Is it possible to get a reunion (basically OR instead of AND)
Thanks so much! [[Special:Contributions/86.122.98.27|86.122.98.27]] 09:42, 12 September 2014 (UTC)
:The documentation for this is at https://semantic-mediawiki.org/wiki/Help:Selecting_pages (see "Unions of query results..."), where you'll find that you can do so in two possible ways.
:FWIW, there's also [[Extension:Semantic Compound Queries]], which does something similar although it is in some ways inferior to using #ask. [[User:Cavila|Cavila]] <span style="font-size:65%;">(MW 1.22, MySQL 5.5.37-0, Php 5.4.4-14 squeeze, SMW 1.9.2, SF 2.7)</span> 18:30, 12 September 2014 (UTC)
::thanks so much! really appreciate it! [[Special:Contributions/86.122.98.27|86.122.98.27]] 22:15, 12 September 2014 (UTC)

== Cannot install core SMW2.0 extension on MW1.23 ==

Hello, I'm trying to install just SMW by itself on MW1.23.5 but when I use either composer or the ExtensionDistributor I get the same result when trying to run the maintenance/update.php script which is about 15 warnings about classes such as "SMW\Store" not found and finally a fatal error as follows:
:'''Fatal error: Class 'SMW\SimpleDependencyBuilder' not found in /home/translat/public_html/w/123/mediawiki-1.23.5/extensions/SemanticMediaWiki/SemanticMediaWiki.php on line 112'''
Anyone have any ideas what might be wrong here? [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 15:28, 14 October 2014 (UTC)
:I've tried dropping back to SMW1.9 with Semantic Bundle so that I can be sure the versions of Validator etc match, but unbelievably I'm still getting the same result!!! [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 20:15, 14 October 2014 (UTC)
::You can not use Semantic Bundle with any other version of SMW of which it has been released because it registers the vendor/autoloader manually and doesn't use Composer to manage its package dependencies which caused issues in the past [0, 1] and will so in future because of the different class map.
::If you install SMW via Semantic Bundle then you have to wait until a new version is released otherwise trying to upgrade to another version of SMW will ultimately fail.
::I would suggest you deleted the vendor folder and re-install SB.
::For example, if on the other hand you install SMW via Composer, each time an update or removal occurs the autoloader (which is where the "Fatal error: Class" message comes from in case classes are not registered) is being re-generated to ensure it matches with the expected class map.
::[0] https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/229
::[1] http://wikimedia.7.x6.nabble.com/Installing-SMW-without-composer-tp5023207p5023218.html [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 15:04, 15 October 2014 (UTC)
:::I'm not installing a different version or upgrading, I've just tried to install SMW and some of the other related extensions in the SemanticBundle and I'm getting the errors shown above. When I sadi "I've tried dropping SMW back to 1.9" what I meant is that I've tried the entire installation operation from scratch using Semantic Bundle that comes with version 1.9 of SMW. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 12:19, 17 October 2014 (UTC)
:Installing SMW 2.* via Composer works as expected (being constantly monitored and tested via Travis-CI [0]).
:[0] https://s3.amazonaws.com/archive.travis-ci.org/jobs/38009543/log.txt [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 15:09, 15 October 2014 (UTC)
::In my case it's not working as expected, it's giving the errors shown above. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 12:26, 17 October 2014 (UTC)
:::I've got it working with composer. What I was doing wrong was installing composer and the SMW extensions within the extensions directory which didn't work. When I did it within the mw root dir it installed the extensions properly. Next I had includes for SMW extensions in the LocalSettings.php file which were raising errors as they're not needed anymore when installing with composer. Thanks for your help. [[User:Nad|Nad]] ([[User talk:Nad|talk]]) 16:02, 20 October 2014 (UTC)

== loops and images ==

Hi, I am new to Semantic. I have been trying to build a basic query that will list all items in a category and their properties :
<pre>{{#ask:[[Category:items]] [[name::+]] [[size::+]]
| ?name
| ?size#-
| ?stacklimit#-

| ?location
| ?description#-
| mainlabel=-
| headers=plain
}}
</pre>
And I keep getting several repeated over and over again, receiving some 500 items for what should have been 20. Can you point me in the right way to solve this?

Also what is the right way to list all image files in a category. I have tried using this:
<pre>{{#ask:[[Category:items images]]
| format=ul
}}</pre>
But I get a list of thumbnails and change it plain, result in a plain list of names. How can I get a list of name + links? [[Special:Contributions/87.68.255.133|87.68.255.133]] 00:28, 9 November 2014 (UTC)

== Installation. MW 1.25 ==

I installed Mediawiki 1.25.1 (new empty DB, no extensions). I run the installation script for SMW (https://www.semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.22%2B)

#> composer.phar require mediawiki/semantic-media-wiki "~2.1"

The composer reports:

[RuntimeException]
The lock file does not contain require-dev information, run install with the --no-dev option or run update to install those packages.

What am I doing wrong? [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 19:32, 31 May 2015 (UTC)
:See [0].
:[0] https://semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.22%2B#MW_1.25.2B [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 17:46, 1 June 2015 (UTC)
::Thanks a ton, I just wanted to start investigating about this.
::Edit: I have just created a [[semantic-mw:Help:Installation/Using_Composer_with_MediaWiki_1.25%2B|dedicated page for MW 1.25+]] based on your info. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 17:49, 1 June 2015 (UTC)
:::Thanks! ) [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 19:43, 1 June 2015 (UTC)
::::The problem was not solved. The script <code>composer.phar install</code> still reports ''run install with the --no-dev''. The script <code>composer.phar install --no-dev</code> reports ''ok'' but the script <code>composer.phar require mediawiki/semantic-media-wiki "~2.2"</code> again reports the same error.
::::What I need to do? [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 20:39, 1 June 2015 (UTC)
:::::Apparently it is not <code>composer.phar install</code> but <code>composer.phar update</code> that would ensure that all packages for MW 1.25 are installed (because 1.25 comes with a pre-deployed composer .json) before SMW can be added. [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 22:43, 1 June 2015 (UTC)
::::::Thanks, it's work! [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 23:13, 1 June 2015 (UTC)

== SMW and MW 1.25.1 not showing property names correctly ==

:'''MW: 1.25.1'''
:'''SMW: (latest from composer, "~2.1")'''
:Working tirelessly to get this to work and understand it. I'm using the "Berlin" example from the "Demo::", vis-a-vis this:
:<code> Berlin is home to [[Population::3,520,061]] souls. It is located in [[located in::Germany]].</code>
:Basically, the problem is I have is, in the fact box, the incorrect output following:
:<code> Facts about "Sandbox:Berlin"</code>
:<code> RDF feed</code>
:<code> Population|3,520,061|Population 3,520,061 +</code>
:<code> located in|Germany|located in Germany +</code>
:and - just this morning - I see the correct output briefly IF I write LocalSettings.php after commenting out enableSemantics()
:<code> Facts about "Sandbox:Berlin"</code>
:<code> RDF feed</code>
:<code> Located in Germany +</code>
:<code> Population 3,520,061 +</code>
:Upon refresh of the correctly-displaying page, without touching LocalSettings.php again, it reverts to the old, incorrect output.
:Bottom line: I cannot get consistent, correct behavior.
:What I have the 'enableSemantics" is of this form:
:enableSemantics( 'web.mysite.com/wiki' );
:I read somewhere that "enableSemantics" is no longer necessary, but there is no consistent idempotency: hitting refresh even on a correctly-displayed page with Factbox always reverts back to the wrong one.
:Everything else in the MW install works correctly. I see tremendous potential in Semantic-MediaWiki and would very much like to become an advocate of its power.
:Additional details:
:If, on the correct page, I click on Population (for which I've entered a page definining it as a number, ergo "This is a property of type [[Has type::Number]]"), the "Number" links (correctly) to Special:Types/Number.
:On the incorrectly-displayed page, clicking on Populate tries to create a page called "Property:3,520,061".
:Any help appreciated.
:-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 16:23, 11 June 2015 (UTC)
::It appears that commenting in/out the
::<code> enableSemantics( 'web.mysite.com/wiki' );</code>
::is a red herring (will leave commented out since it's no longer necessary according to SMW documentation).
::Appparently I am up against some kind of caching issue. As much caching as possible has been turned OFF for debugging.
::Again, any help deeply appreciated.
::-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 16:45, 11 June 2015 (UTC)
:::It appears that setting this (in LocalSettings.php) thus
:::<code> $smwgEnableUpdateJobs = false;</code>
:::has helped ENORMOUSLY.
:::-Greg [[Special:Contributions/162.17.190.121|162.17.190.121]] 19:47, 11 June 2015 (UTC)
::If you follow the video [0] you should get an idea how it supposed to work on a vanilla installation.
::> On the incorrectly-displayed page, clicking on Populate tries to create a page called "Property:3,520,061".
::This is a clear indication that your Property NS isn't setup correctly otherwise "3,520,061" would be just a plain text (under the assumption that Has number is of type number) and not be red linked.
::> enableSemantics( 'web.mysite.com/wiki' );
::> is a red herring (will leave commented out since it's no longer necessary according to SMW documentation).
::I don't think the installation [1, 2] is mentioning that "enableSemantics" is no longer required.
::> It appears that setting this (in LocalSettings.php) thus
::> $smwgEnableUpdateJobs = false;
::$smwgEnableUpdateJobs [3] has nothing to do with the Property namespace and should only be temporary set to false in order to disable inserting UpdateJob's into the job queue (due to high load).
::In the matter of the Property NS, please have a look at [4].
::[0] https://vimeo.com/82255034 (https://semantic-mediawiki.org/wiki/Help:Getting_started)
::[1] https://semantic-mediawiki.org/wiki/Help:Installation/Using_Composer_with_MediaWiki_1.25%2B
::[2] https://github.com/SemanticMediaWiki/SemanticMediaWiki/blob/master/docs/INSTALL.md#step-5
::[3] https://semantic-mediawiki.org/wiki/Help:$smwgEnableUpdateJobs
::[4] https://semantic-mediawiki.org/wiki/Help:Namespaces [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 13:20, 17 June 2015 (UTC)
:It turns out that other extensions loaded via MW's extension.json can in fact nullify the SMW NS setting. For more information and a solution, see [0].
:[0] <nowiki>http://wikimedia.7.x6.nabble.com/MW1-25-1-SMW-2-2-breaks-when-installed-with-DynamicSidebar-tp5049862.html</nowiki> [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 14:53, 30 July 2015 (UTC)

== . ==
{{Archive top|result=.|status=resolved}}

[[User:Tenbergen|Tenbergen]] ([[User talk:Tenbergen|talk]]) 15:46, 22 July 2015 (UTC)
{{Archive bottom}}

== Can't see the Special:SMWAdmin to finish installation ==

Hi, I have an issue when try to initialise tables for semantic,

The wiki show me the special page Special:SMWAdmin does't exist, I can see the extension listed in the Special:Version page.

My wiki are on subfolder domain.

I try this:

enableSemantics('<nowiki>http://mydomain'</nowiki>);

and

enableSemantics('<nowiki>http://mydomain/subfolder'</nowiki>);

without any favorable result, what can be? [[Special:Contributions/187.189.160.180|187.189.160.180]] ([[User talk:187.189.160.180|talk]]) 20:08, 14 August 2015 (UTC)
:Please have a look at [0].
:[0] https://semantic-mediawiki.org/w/index.php?title=Help:Special:SMWAdmin#Access%20restrictions [[User:MWJames|MWJames]] ([[User talk:MWJames|talk]]) 12:38, 21 August 2015 (UTC)
:That doesn't help. The Special page SMWAdmin does not appear if the read permissions are set to "false" for every group :
:<code> $wgGroupPermissions['*']['read'] = false;</code>
:You have to set it to '"true to see the Special page SMWAdmin. That's an issue ! [[Special:Contributions/31.39.114.223|31.39.114.223]] ([[User talk:31.39.114.223|talk]]) 18:02, 26 February 2016 (UTC)
:The cause of this problem seems to be the incompatibility with the ConfirmEdit Extension : [[Thread:Talk:Semantic Bundle/Property namespace disappears with SB]] [[Special:Contributions/31.39.114.223|31.39.114.223]] ([[User talk:31.39.114.223|talk]]) 20:25, 28 February 2016 (UTC)

== Please add this page to translate ==

Please add this page to translate [[User:Перевод15|Перевод15]] ([[User talk:Перевод15|talk]]) 19:47, 11 March 2016 (UTC)

== Resources fail to load with non-default extensions setup (e.g. symlinks) ==
{{Archive top|result=SMW 2.4.0 brought a [https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/1476 solution]|status=resolved}}

I configured a shared wiki setup with different extension features per wiki. In SMW 2.3.1 when debug=true in the URL some resources issue an error not to be loaded. With MW 1.25+ it is considered to set up a different extension directory ([[Manual:$wgExtensionDirectory]]) but it is not taken into account for SMW resources. I checked out and see why: SemanticMediaWiki/res/Resources.php assumes folder extensions to be there but allowing a different <code>$wgExtensionDirectory</code> this assumption is proven wrong. So if I add <code>debug=true</code> to the URL I get <nowiki>http://offene-naturfuehrer.de/w/extensions//usr/share/mediawiki26/extensions-rich-features/SemanticMediaWiki/res/smw/util/ext.smw.util.tooltip.js</nowiki> it becomes 404 and does not get loaded. Is there any fix I can do, LocalSettings or so? See also https://phabricator.wikimedia.org/T130520 [[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 11:01, 21 March 2016 (UTC)
:There is an [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/1466 issue at GitHub] for this now. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 13:22, 21 March 2016 (UTC)
{{Archive bottom}}

== Semantic queries aren't showing all the results ==
{{Archive top|result=SMW 2.5.0 brought [https://www.semantic-mediawiki.org/wiki/Help:Full-text_search full-text search]|status=resolved}}

Hi,

For some reasons, semantic queries aren't showing all the results on my wiki.

On Wikifab.org, the property "Material" of the page "[http://en.wikifab.org/index.php/ZipStich_Chair_with_plywood_pieces_and_zip_ties ZipStick Chair...]" contains the terms "Plywood" and "strong". However:
* this [http://en.wikifab.org/index.php?title=Special%3AAsk&q=%5B%5BMaterial%3A%3A~*Plywood*%5D%5D&po=&eq=yes&p%5Bformat%5D=broadtable&sort_num=&order_num=ASC&p%5Blimit%5D=&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=...+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&p%5Bsep%5D=&eq=yes query] correctly have "ZipStich Chair..." in the results
* But this [http://en.wikifab.org/index.php?title=Special%3AAsk&q=%5B%5BMaterial%3A%3A~*strong*%5D%5D&po=&eq=yes&p%5Bformat%5D=broadtable&sort_num=&order_num=ASC&p%5Blimit%5D=&p%5Boffset%5D=&p%5Blink%5D=all&p%5Bsort%5D=&p%5Bheaders%5D=show&p%5Bmainlabel%5D=&p%5Bintro%5D=&p%5Boutro%5D=&p%5Bsearchlabel%5D=...+further+results&p%5Bdefault%5D=&p%5Bclass%5D=sortable+wikitable+smwtable&p%5Bsep%5D=&eq=yes query] dont...
Do you know why? Is it a known issue?

Thanks in advance for your help. [[Special:Contributions/85.54.29.115|85.54.29.115]] ([[User talk:85.54.29.115|talk]]) 05:55, 5 July 2016 (UTC)
:This is currently not supported. See [[semantic-mw:Help:Type_Text#Searching_within_values|for why]]. This may however change [https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/1481 very well with SMW 2.5] later this year. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 15:40, 5 July 2016 (UTC)
:Thanks for your reply. I have subscribe to the notifications and asked a developer of our team to see if he can help. [[Special:Contributions/83.47.139.142|83.47.139.142]] ([[User talk:83.47.139.142|talk]]) 09:38, 6 July 2016 (UTC)
{{Archive bottom}}

== Semantic Mediawiki website offline ==
{{Archive top|result=The website is back on-line.|status=resolved}}

https://www.semantic-mediawiki.org/ has been offline for some time. What is going on?
[[User:Henryfunk|Henryfunk]] ([[User talk:Henryfunk|talk]]) 11:47, 11 January 2017 (UTC)
:Thanks for reporting. I guess this is a DOS attack. The VM should be rebooted and see if this makes them back off. Currently I do not have access to the interface enabling me to do this but I am working on it. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 15:47, 11 January 2017 (UTC)
:Thanks. I hope you succeed. In the meantime, people who need access to the site can do as follows:
:# Navigate to: https://archive.org/
:# In the WaybackMachine input area at the top of the page, type in: https://www.semantic-mediawiki.org/ and press Enter
:# After a few seconds a calendar will appear. Click the blue circle on the last item (so far): 31 December 2016, and wait five or 10 seconds
:# You should now see a copy of semantic-mediawiki.org's frontpage. You can use the menus etc., just be a little patient, it takes a while before pages are shown, and be aware that this is a static copy of the site. [[User:Henryfunk|Henryfunk]] ([[User talk:Henryfunk|talk]]) 10:26, 12 January 2017 (UTC)
{{Archive bottom}}

== Help for Wikia users ==
{{Archive top|result=see http://smwtest.wikia.com|status=resolved}}

Wikia provides a "Semantic MediaWiki Test Wiki " to help users of the relatively few Wikia sites that use semantic extensions: <nowiki>http://smwtest.wikia.com</nowiki>. Some material is copied from this MW site, augmented by the occasional note about the current Wikia version of each extension. [[User:Robin Patterson|Robin Patterson]] ([[User talk:Robin Patterson|talk]]) 06:59, 16 February 2017 (UTC)
{{Archive bottom}}

== mediawiki/semantic-media-wiki: 2.5.0 installed, ~2.5 required. ==
{{Archive top|result=use "update.php --skip-external-dependencies"|status=resolved}}

I'm not sure is it a bug or I'm doing something wrong but after the command <code>composer require mediawiki/semantic-media-wiki "~2.5" --update-no-dev</code> when I'm running <code>php $IP/maintenance/updae.php</code> this message appears:

<pre>
mediawiki/semantic-media-wiki: 2.5.0 installed, ~2.5 required.
Error: your composer.lock file is not up to date. Run "composer update" to install newer dependencies
</pre>

This problem was solved when I changed 'semantic-media-wiki' directive in <code>composer.json</code> from:

<pre>"mediawiki/semantic-media-wiki": "~2.5"</pre>

to:

<pre>"mediawiki/semantic-media-wiki": "2.5.0"</pre>

'''It it the right solution?''' [[User:Spas.Z.Spasov|Spas.Z.Spasov]] ([[User talk:Spas.Z.Spasov|talk]]) 13:47, 4 April 2017 (UTC)
:This way you will have to update your file every time a new version is released. See [https://www.semantic-mediawiki.org/wiki/Help:Installation/Troubleshooting#Error:_your_composer.lock_file_is_not_up_to_date. here] for another way around this. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 20:35, 4 April 2017 (UTC)
{{Archive bottom}}

== How to rebuild semantic mediawiki information? ==
{{Archive top|result=The script is located at "<code>/../extensions/SemanticMediaWiki/maintenance/</code>"|status=resolved}}

I have a page A and page B. Both page does not have properties which link each page. But page A show me B have a property which linked to A. I can not find a property of page B which link to page A.

Maybe something wrong on database. I'd like to clear this. I run /maintenance/rebuildall.php but not fixed.

Would you recommend me how to fix this? Thanks.

my private wiki have mediawiki 1.28.2, SMW 1.25.1, Apache PHP MySql on debian linux. [[User:Naramoksu|Naramoksu]] ([[User talk:Naramoksu|talk]]) 00:13, 2 May 2017 (UTC)
:I am not sure if I understand the issue correctly. However if you would like to rebuild semantic data you will have to use the [https://www.semantic-mediawiki.org/wiki/Help:Maintenance_script_%22rebuildData.php%22 "rebuildData.php"] script which is located in "/extensions/SemanticMediaWiki/maintenance". The "rebuildall.php" script has a different scope and is provided by MediaWiki core. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 08:34, 2 May 2017 (UTC)
:Thanks for your information. I just looked at the maintenance directory. [[User:Naramoksu|Naramoksu]] ([[User talk:Naramoksu|talk]]) 13:29, 2 May 2017 (UTC)
{{Archive bottom}}

== MyISAM support is blocking use of Azure Database for MySql ==
{{Archive top|result=See [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/2661 this issue and the linked documentation].|status=resolved}}

I just attempted to move my mediawiki DB into Azure Database for MySql (their new hosted MySql offering). Got blocked on the use of MyISAM fulltext search on smw_ft_search.

Can this be migrated to InnoDB soon? Latest MySQLs have support for fulltext in InnoDB. [[User:Lsilverman|Lsilverman]] ([[User talk:Lsilverman|talk]]) 18:41, 11 July 2017 (UTC)
:Sorry, I did not see this. See [https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/2661 this issue and the linked documentation] on how to switch to InnoDB. It is just a configuration parameter setting. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 12:07, 9 September 2017 (UTC)
{{Archive bottom}}

== Mediawiki 1.29.1 and Semantic ==
{{Archive top|status=resolved}}

I have update from MW 1.26.4 to
{| class="wikitable"
!Software
!Version
|-
|[https://www.mediawiki.org/ MediaWiki]
|1.29.1
|-
|[https://php.net/ PHP]
|5.6.30-nmm1 (fpm-fcgi)
|-
|[https://www.mysql.com/ MySQL]
|5.7.15-nmm5-log
|-
|[http://site.icu-project.org/ ICU]
|55.1
|}
I have install the last version of all Semantic extensions. Now i get this Semantic Errors:

http://kubb290.kubbwiki.de/

'''Warning''': Class 'SMW\Updater\DeferredCallableUpdate' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''8'''

'''Warning''': Class 'SMW\Parser\InTextAnnotationParser' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''9'''

'''Warning''': Class 'SMW\Encoder' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''10'''

'''Warning''': Class 'SMW\Query\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''11'''

'''Warning''': Class 'SMW\Query\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''12'''

'''Warning''': Class 'SMW\Query\ExportPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''13'''

'''Warning''': Class 'SMW\Query\ResultPrinters\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''14'''

'''Warning''': Class 'SMW\Query\ResultPrinters\ResultPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''15'''

'''Warning''': Class 'SMW\Query\ResultPrinters\FileExportPrinter' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''16'''

'''Warning''': Class 'SMW\Query\Parser' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/src/Aliases.php''' on line '''17'''

'''Fatal error''': Interface 'SMW\QueryEngine' not found in '''/www/htdocs/w0101624/kubb290/extensions/SemanticMediaWiki/includes/storage/SMW_Store.php''' on line '''34'''

All Pathe are correct and all Files are exist.

Idea what is wrong?

thank's

Bastor [[User:Bastor de|Bastor de]] ([[User talk:Bastor de|talk]]) 22:59, 28 October 2017 (UTC)
:I the files are not loaded than it does not matter if they are existing or not. I guess you did not install and upgrade via command line. You used [https://github.com/SemanticMediaWiki/SemanticMediaWiki/releases/tag/2.5.5 one of the tarballs with dependencies]? If yes there may be some issue mashing this up with MediaWiki. In this case I recommend to install MW on a machine with command line add SMW to it and after this is done move the files all over. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 16:06, 30 October 2017 (UTC)
:MMh, thanks for tip.
:After my first test i get the same error :-(
:Think you my database have a error or the file structur a wrong? [[User:Bastor de|Bastor de]] ([[User talk:Bastor de|talk]]) 17:04, 31 October 2017 (UTC)
:I think the issue is that the files are not being loaded properly. So installing MW on a machine with command line adding SMW to it and after this moving the files all over did not work? This has nothing to do with the database. [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 21:11, 31 October 2017 (UTC)
:Thanks for help, You were right [[Special:Contributions/77.180.154.2|77.180.154.2]] ([[User talk:77.180.154.2|talk]]) 00:43, 4 November 2017 (UTC)
:Glad it worked out! [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 14:07, 4 November 2017 (UTC)
{{Archive bottom}}

== mediawiki smw-editpage-annotation-enabled editform to large ==

Hello,

my EditForm is to large and the save button is out of my screen. I must scroll down, to press the button.

After installing SmenaticMediaWiki there is a smw-editpage-annotation-enabled-section in the Firefox DebugConsole, that push the EditForm a little bit down.

I need a option to reduce the size of the editform, OR i need the option to collapsible the smw-editpage-annotation-enabled-section.

Can anyone help me? [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 08:21, 4 April 2018 (UTC)

Manual talk:Collapsible elements

2018-03-29T11:02:41Z

213.61.254.68: /* not working collapse */

== Expand/Collapse All? ==

Does this have any support for an "expand all" or "collapse all" button? Pretty desperate for the ability to use such myself.

== Doesn't work? ==

This didn't work correctly in my Mediawiki 1.12.0 install. Looking at the source code of the page it created, initially hidden content is indeed hidden, but there is no "Show" link to reveal the content. Do you have any ideas? --[[User:Gadlen|Gadlen]] 19:13, 5 June 2008 (UTC)

== I'm not seeing the "hide" or "show" links ==

I'm running 1.13.4. any thoughts, could it be firefox? --[[Special:Contributions/69.244.124.138|69.244.124.138]] 01:16, 17 March 2009 (UTC)

== still doesn't work any thoughts this what is is displayed: ==

Edited both common.js and common.css
This is the header cell, which is always shown
This cell is not shown by default.

(no hide or show links)

--[[Special:Contributions/69.244.124.138|69.244.124.138]] 04:42, 25 March 2009 (UTC)

:Is this code for 13.3 + ?
--[[User:Mappc|Mappc]] 00:00, 5 April 2009 (UTC)

::I'm still interested in getting some resolution....any thoughts
--[[User:Mappc|Mappc]] 22:54, 6 April 2009 (UTC)

== This does work for me (IE6 , Firefox 3 and MediaWiki 13.4) ==
I had to change the function below the rest stay as it is. --[[User:AndreasMueller|AndreasMueller]] 21:56, 26 May 2009 (UTC)
<pre>
function createCollapseButtons()
{
var tableIndex = 0;
var NavigationBoxes = new Object();
var Tables = getElementsByClassName(document, "table", "collapsible");

for ( var i = 0; i < Tables.length; i++ ) {
/* only add button and increment count if there is a header row to work with */
var HeaderRow = Tables[i].getElementsByTagName( "tr" )[0];
if (!HeaderRow) continue;
var Header = HeaderRow.getElementsByTagName( "th" )[0];
if (!Header) continue;

NavigationBoxes[ tableIndex ] = Tables[i];
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );

var Button = document.createElement( "span" );
var ButtonLink = document.createElement( "a" );
var ButtonText = document.createTextNode( collapseCaption );

Button.className = "collapseButton"; //Styles are declared in Common.css

ButtonLink.style.color = Header.style.color;
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );
ButtonLink.appendChild( ButtonText );

Button.appendChild( document.createTextNode( "[" ) );
Button.appendChild( ButtonLink );
Button.appendChild( document.createTextNode( "]" ) );

Header.insertBefore( Button, Header.childNodes[0] );
tableIndex++;
}

var Tables = getElementsByClassName(document, "table", "collapsed");
for ( var i = 0; i < Tables.length; i++ ) {
collapseTable( i );
}

var Tables = getElementsByClassName(document, "table", "autocollapse");
for ( var i = 0; i < Tables.length; i++ ) {
if ( i >= autoCollapse ) {
collapseTable( i );
}
}
}
</pre>

== Worked A-OK ==

No editing needed over here. Using MediaWiki 1.15.1 with no other custom JS.
[[Special:Contributions/74.65.88.219|74.65.88.219]] 01:55, 7 October 2009 (UTC)

: Worked for me too on 1.15.1. At first it was very frustrating, I couldn't get it to work, but all I needed to do was the Shift-Refresh thing in my browser. =D --[[User:J.nesta|J.nesta]] 18:36, 5 November 2009 (UTC)

== hide/show placement not working ==

I updgraded to 1.15.1. Now my hide/show buttons are always on the left even though I have the Common.css file with float right. See at http://sunshinereview.org/index.php/User:Ljarratt

== 1.16 functionality ==

Beta 3. This function works flawlessly for me.
:Funny, not doing a damn thing for me (as describe, prior to 1.7 in the main article)
:MediaWiki 1.16.2
:PHP 5.2.11 (apache2handler)
:MySQL 5.0.77
:--[[Special:Contributions/99.197.224.57|99.197.224.57]] 06:04, 26 March 2011 (UTC)

==1.15.3 Not Working - Using skin Cavendish==

can anyone help with making this functional?
http://emajenanything.com/mainwiki/wiki/index.php?title=Test THANKS

== What? ==

How come I don't have neither common.js nor common.css in my wiki? how do I make this effect? :( --[[Special:Contributions/201.255.119.39|201.255.119.39]] 07:22, 19 July 2010 (UTC)
: You can create them using your search box and searching for
MediaWiki:Common.css
MediaWiki:Common.js
: --Skew 03:14, 22 September 2010 (UTC)

== show/hide: jumping to top ==

A click on my show/hide button causes the page to jump to the top. Any ideas? [[User:Gohnarch|Gohnarch]] 20:30, 27 September 2010 (UTC)

: I have same problem on two different installs of 1.15 (Ubuntu and CentOS) - tried code from "This does work for me ..." above and that seems to be OK for now ... WBN [[Special:Contributions/82.41.58.191|82.41.58.191]] 23:49, 13 October 2010 (UTC)

:That's as a result of these two lines

ButtonLink.setAttribute( 'href', '#' );
addHandler( ButtonLink, 'click', new Function( 'evt', 'collapseTable(' + tableIndex + ' ); return killEvt( evt );' ) );

:If you look at the current mw [[MediaWiki:Common.js]], it reads

ButtonLink.setAttribute( 'href', "javascript:collapseTable(" + tableIndex + ");" );

:(see [[W:Fragment identifier]]). I will update the page to show this change if that is all right with everybody. --[[User:JCrue|JCrue]] 18:24, 30 November 2010 (UTC)

== Still not working ==

Hi, I'm trying to install this on 1.15, and the "hide/show" tags aren't appearing. I've edited the common.js and common.css, as above and as shown on the article page, purged webcaches, etc, etc, and still no go. Any ideas for how to troubleshoot this? - very frustrating!

== 1.17 example not working on diffs ==

Hi!

I noticed that the new examples doesn't works when the page is seen in a diff like [http://www.mediawiki.org/w/index.php?title=Manual:Collapsible_tables&diff=cur&oldid=367004#After_1.17 this]. I think it should work even in this case (not only when viewing the page directly). [[b:pt:User:Helder.wiki|Helder]] 16:03, 23 February 2011 (UTC)
: During development it worked fine in preview, diff and oldid view. Will look into it. [[User:Krinkle|Krinkle]] 11:00, 24 February 2011 (UTC)
:: It does work in the latest development version, as for example ran on TranslateWiki, [http://translatewiki.net/w/i.php?title=User%3AKrinkle%2FCollapsingTestpageMw&diff=2756282 here]. Hm.. [[User:Krinkle|Krinkle]] 11:32, 24 February 2011 (UTC)
::: Seems the cause isn't in the script after all. The problem is the FlaggedRevisions-extension which loads the page-contents afterwards via JavaScript causing any onload handlers to fail miserably since there isn't a page at that time (TOC-toggle, mw-collapsible, mw.util.$content) See also [[bugzilla: 26175]] and [[bugzilla: 27513]]. I can't fix this untill FlaggedRevs has some kind of hook or is fixed otherwise. Any javascript handlers will fail (potentially $.fn.placeholder and $.fn.checkboxShiftClick as well) [[User:Krinkle|Krinkle]]

== Cannot get Collapse to work in 1.17 ==

I have tried to different 1.17 installs and I cannot get collapse to work at all. I am following the examples exactly:

:<nowiki><div class="toccolours mw-collapsible" style="width:400px"></nowiki>
:<nowiki>This is text is collapsible. {{Lorem}}</nowiki>
:<nowiki></div></nowiki>

Just shows the text. There is no option to collapse. The other examples give the same results. The ability to collapse is completely missing, even though the directions say "After 1.17... Basically all you do is add the class "mw-collapsible" to an element." What am I missing?

* Site #1: http://wiki.cyanogenmod.com/wiki/User:Pconwell/sandbox2
* Site #2: http://w.gu1dry.com/User:Pconwell/Sandbox2

: I can't get this to work over at http://everquest.wikkii.net either. I also couldn't get the old style of collapsible tables using common.css and common.js to work either. I'm going nuts trying to figure out what I have done wrong. [[Special:Contributions/24.40.138.185|24.40.138.185]] 21:52, 24 June 2011 (UTC)

On [[ResourceLoader/Default_modules#jQuery.makeCollapsible]] it is said that this feature is currently available on trunk, since [[rev:78914]], but there is no mention of MW 1.'''17'''. So, I think this page is outdated.

Anyway, on [[meta:User_talk:Krinkle/1-17-allwikis#Wikis_using_jquery.makeCollapsible|this page]] it is explained how to install the plugin on MW 1.17 (as was made here on MediaWiki.org). [[b:pt:User:Helder.wiki|Helder]] 12:43, 28 June 2011 (UTC)

: Thank you for your concern. I had created MediaWiki:JQuery-makeCollapsible.js and MediaWiki:JQuery-makeCollapsible.css on my wiki and put the two lines in my Common.js before posting here. But it just doesn't seem to work. Neither does the old style collapsible tables. I'm at a loss here to understand why. [[Special:Contributions/24.40.138.185|24.40.138.185]] 07:29, 29 June 2011 (UTC)
::Notice that the current code of your MediaWiki:Common.js has syntax errors before the makeCollapsible plugin is loaded (copy and paste it on [http://jshint.com/ JSHint] to check the syntax). Specifically, this will not work: <syntaxhighlight lang="javascript">if ( {{PAGENAME}} == 'Main Page' )</syntaxhighlight>
::So, I think the plugin will work if you add [http://everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&curid=439&diff=1181&oldid=1029 these lines] again and fix the syntax errors above (or just remove everything from [http://everquest.wikkii.net/w/index.php?title=MediaWiki:Common.js&action=edit your MediaWiki:Common.js] except this:
<syntaxhighlight lang="javascript">/* FROM MEDIAWIKI.ORG COMMON.JS Load collapsible javascript */
mw.loader.load( 'http://www.everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&action=raw&ctype=text/javascript' );
</syntaxhighlight>
::) and clear your cache. [[b:pt:User:Helder.wiki|Helder]] 13:18, 29 June 2011 (UTC)

::: Helder, thank you a million times. That was the problem all right. Thanks. [[Special:Contributions/24.40.138.185|24.40.138.185]] 06:22, 30 June 2011 (UTC)

== Indication of collapsed/expandable status ==
: ''<small>Moved from [http://meta.wikimedia.org/w/index.php?title=User_talk:Krinkle/1-17-allwikis&oldid=2703017#Indication_of_collapsed.2Fexpandable_status Meta-Wiki]</small>''

Hi,

This might be the wrong place to ask, but we were wondering if their is an easy way to know which status of the class="mw-customtoggle-myDivision" is set in terms of being collapsed/expandable.

Using the standard solution indicates the status through the display of either [Collapsed] or [Expand], in our case we trigger the area which need to be collapsed with the display of an icon, and as soon the user switches from one status to the other one we wanted to indicated a change through a change in the icon displayed.
<pre>
<div class="mw-customtoggle-topicon" style="cursor:pointer">[[File:icon-set-10-arrow-down.png|14px|link=]]</div>
</pre>
So in case the class contains "mw-collapsible mw-collapsed" display one type of icon, and in case of the class just being "mw-collapsible" display another icon. --[[m:User:MWJames|MWJames]] 18:13, 6 July 2011 (UTC)
: Hi MWJames,
: If you can provide a link to where this happends on a live-wiki I may be able to give a more fine-tuned detail. I'll show you how I would do it though. I'm assuming your toggle-icon is inside {{tag|div|params= class="mw-collasible"}}:
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible">
<div class="mw-collapsible-toggle toccolours" style="width: 100%">
<span class="down">[[File:Arrow-down-dash-2.0.svg|50px|center|link=]]</span>
<span class="up">[[File:Arrow-up-dash-2.0.svg|50px|center|link=]]</span>
</div>
<div class="mw-collapsible-content">
{{User:Krinkle/Lorem}}
</div>
</div>
</pre>

CSS:
<source lang="css">
#collapse-pre-one .mw-collapsible-toggle .up,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .down {
display: none;
}
#collapse-pre-one .mw-collapsible-toggle .down,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .up {
display: block;
}
</source>
</blockquote>
: A demo of this can be found at [[testwiki:User:Krinkle/CollapsingTestpageMw#collapse-pre-one]]
: Note that the <code>collapse-pre-one</code> is not required, it's just to make sure it won't apply to other collapsible constructions on the same page. Use whatever identifier you like [[User:Krinkle|Krinkle]] 21:14, 6 July 2011 (UTC)

== makeCollapsible "in core" ==

Does "in core as of MediaWiki 1.18 or higher" mean that it will be enabled by default on all wikis, loaded and activated on every page? If so, will there be any way to disable it? --[[User:Yair rand|Yair rand]] 08:54, 14 July 2011 (UTC)
: There is nothing to disable as all the scripts mentioned on this page are only triggered if there are elements on the page marked as "mw-collapsible". If your wiki doesn't want or have collapsible elements, this script will not be triggered and nothing will change when upgrading to 1.18. [[User:Krinkle|Krinkle]] 04:21, 4 August 2011 (UTC)
::Really? It won't even load the scripts or take up time running any JS if there aren't any mw-collapsible elements in the wikitext? --[[User:Yair rand|Yair rand]] 05:14, 4 August 2011 (UTC)

== Use new 1.18 collapsible in 1.17 ==

You can use the new 1.18 collapsible code in a 1.17 install. Just paste the contents of jquery-makeCollapsible.js into your MediaWiki:Common.js

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.js?view=co Download head version from MediaWiki]

Then at the bottom of MediaWiki:Common.js, add:

mw.messages.set({"collapsible-collapse":"Collapse","collapsible-expand":"Expand"});
$(document).ready(function(){
$('.mw-collapsible').makeCollapsible();
});

And add the contents of jquery.makeCollapsible.css into your MediaWiki:Common.css

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.css?view=co Download head version from MediaWiki]

If there is a tidier way of doing this, please let me know. --[[User:Thenickdude|Thenickdude]] 11:33, 13 September 2011 (UTC)

== Autocollapse ==

Has a version of autocollapse been implemented in core in 1.18? --<small style="background:#f00">'''★ [[User:Airon90|<span style="color:#000">→ A</span>]][[Special:Contributions/Airon90|<span style="color:#f00;background:#000">ir</span>]][[User talk:Airon90|<span style="color:#000">on Ĉ</span>]]'''</small> 14:09, 7 October 2011 (UTC)

== Common.js script (Before 1.18) don't works ==

Hey there!

I have some Wikis running on an Debian Linux 6.0 (Squeeze) Webserver.<br>
MediaWiki 1.17.0 (Version 95135)<br>
PHP 5.3.3-7+squeeze3 (apache2handler)<br>
MySQL 5.1.49-3<br>

and i have the Problem, that this Collapse Hide & Show didnt works. I try it on two local Servers installed in Virtual Box and i have there the same problem. Could it be, that Debian Squeeze is the problem? Ive tryd all things, that i found here. But without a happy ending... [[User:Yukii|Yukii]] 12:27, 10 October 2011 (UTC)

== mw-collapsible will not work (1.18) ==

I've copied and pasted the examples and none of them work no matter what I do - upgraded my wiki, completely reinstalled the wiki, no dice. [[User:Leangle|Leangle]] 8:54 PM, Dec 29 2011

== Customizing Collapse/Expand location ==

Using 1.18, how would I customize the mw-collapsible mw-collapsed CSS so that the 'Expand' or 'Collapse' buttons appear on the left?

I'm thinking of something like what the mobile site does for certain sections - rather than having the 'expand' button float out of site off to the right, i'd prefer it to be on the left. It doesn't necessarily need to use a button, but that would be interesting as well.

[[Special:Contributions/66.3.56.92|66.3.56.92]] 23:21, 1 March 2012 (UTC)

Update:

Solved it, more or less

/* leave toggle on the right for tables */
.tablecollapse span.mw-collapsible-toggle{
float:right;
}

/* put it on the left for everything else */
.collapse span.mw-collapsible-toggle {
float: left;
}

By setting those classes, I can make sure that for tables, the toggle still appears where it should, and for other areas, the toggle appears floating left.

not sure how to swap out images, but at this point, thats no big deal. Hope this helps someone.

Another way:<br>
For those of you who don't like having the toggle right beside text, here's how to make text appear below it:
.mw-collapsible-toggle {
display:inline-block;
float:none;
}

[[User:Bluekuma|Bluekuma]] ([[User talk:Bluekuma|talk]]) 17:43, 22 May 2015 (UTC)

== Only Works for Anons ==

When i log into my wiki the expand/collapse links disappear and all content within them defaults to expanded. Any idea on how to fix this? I'm thinking it's not loading the java after login but don't know what to change to fix it.

Thanks!

== Extensions that disrupts collapsible elements. ==

I notice that with mediwiki 1.17 I didn't have any collapsible elements, even doing all the things to be done. I upgrade to mediawiki 1.18, and didn't work.

So I notice that, when '''I disable''' the [http://www.mediawiki.org/wiki/Extension:Page_Object_Model Page Object Model] Extension It worked.

Check it.

== 1.19.1 Nested Collapsible elements ==
{{tracked|35257}}
In 1.19.1, using the builtin JQuery mw-collapsible and mw-collapsed classes works as expected, except if you have nested elements and "Expand" a collapsed element, it will also expand all nested elements. Ideally this could either be toggled via a setting or by default not expand all child collapsible elements.
:That seems to be [[bugzilla:35257]]. [[b:pt:User:Helder.wiki|Helder]] 18:31, 6 July 2012 (UTC)

== 19.2 - Collapsible Elements Load Open ==

I was previously using the now obsolete [[Extension:ToggleDisplay|ToggleDisplay]] extension which worked nicely but now after upgrading to 1.19.2 I have started trying to use the built in Collapsible elements feature. It seems fine but when the page loads, all toggle areas load as open and only close once the page is completely loaded. This creates a kind of unwanted stutter in the visual loading of the page.
Can this be fixed or is there a way to use Collapsible elements so it doesn't do this? The reason I mention the extension above is that it doesn't do this. The page loads with elements already closed and it looks great. Would love to have that effect again.

== Loading issue ==

Is it possible to keep all the content collapsed while the rest of the page loads? I have a problem that, on pages with many images and other content, the information that I have initially collapsed is visible until the entire page loads in the browser.
: It looks like this has been a proper nuisance for some time already. [[User:Cavila|Cavila]] <sup>MW 1.19.2, MySQL 5.1.63, Php 5.3.3-7, SMW 1.8</sup> 22:47, 17 January 2013 (UTC) {{tracked|34876}}

== Broken in Old Custom Skins ==

This functionality has been completely destroyed in pre 1.17 skins. It is impossible to implement any of the fixes suggested as the skins do not conform to the new framework, and the files used in the old framework no longer exist. Can anyone suggest a fix to re-implement this behaviour in pre 1.17 skins?

== Custom Toggle with arrow indicator and header ==
This code makes a nice Toggle element with an Arror indicator image. The image can be anything really but an arrow is the most logical choice.<br>
I have not tested backwards compatibility on this for MediaWiki versions < V1.21.<br>
Credit goes to [[User:Krinkle|Krinkle]] as this was adapted from his examples.
<br>
A demo can be seen here: [http://test.wikipedia.org/wiki/User:Shift9999#collapse-pre-one| Toggle with Arrow]
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible mw-collapsed">
<div class="mw-collapsible-toggle toccolours" style="float: none;">
<div class="mw-collapsible-toggle-row">
<div class="mw-collapsible-toggle-header"><big>'''Example Header'''<br>Example sub</big></div>
<div class="mw-collapsible-toggle-indicator">[[File:right-black-arrow.png|150px|link=]]</div>
</div>
</div>
<div class="mw-collapsible-content">
{{Lorem}}
</div>
</pre>

CSS:
<source lang="css">
/* Collapse Toggle container */
#collapse-pre-one .mw-collapsible-toggle{
display: table;
border-collapse: collapse;
width: 100%;
}

#collapse-pre-one .mw-collapsible-toggle-row{
display: table-row;
}

/* Collapse Header should be on the left */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-header{
display: table-cell;
vertical-align: middle;
padding: 5px;
}

/* Collapse indicator image should be inline. align wherever you would like */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator{
display: table-cell;
vertical-align: middle;
padding: 5px;
text-align: right;
}

/* Collapse indicator image size should be something sane*/
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
height: 20px !important;
width: 20px !important;
}

/* Collapse indicator image should rotate when toggled*/
#collapse-pre-one:not(.mw-collapsed) .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
/* Safari */
-webkit-transform: rotate(90deg);

/* Firefox */
-moz-transform: rotate(90deg);

/* IE */
-ms-transform: rotate(90deg);

/* Opera */
-o-transform: rotate(90deg);

/* Internet Explorer */
filter: progid:DXImageTransform.Microsoft.BasicImage(rotation=1);
}
</source>
</blockquote>
--[[User:Shift9999|Shift9999]] at 2:06AM PST - 07-17-2013

== on() causes problems for older jq versions ==

In the code for collpasible tables, on() is used to bind behavior to the <a> for the show/hide button.... This is a jq function introduced in 1.4.2, so if you're using an older jq version, instead use the (old) bind() method instead of on().

== Font color of collapsible button ==

{|class="mw-collapsible" style="float:right;background:#00f;color:#fff"
!Header
|-
|Collapsed content
|}
Previously the font color of collapsible button was inheritable but now it doesn't. The problem is if someone changes the background color of talbe/div to blue, the [expand/collapse] button text is almost invisible even if the user has set color:#fff. -- [[User:Sameboat|Sameboat]] ([[User talk:Sameboat|talk]]) 02:44, 7 February 2014 (UTC)
: Is there any news about this issue? --[[User:Rotpunkt|Rotpunkt]] ([[User talk:Rotpunkt|talk]]) 10:09, 23 May 2016 (UTC)

== Wasn't this feature removed from the latest update? It is not in 1.24.1 ==

I think this has been removed. How do I get it back for new updates? <small><span class="autosigned">— Preceding [[w:Signatures|unsigned]] comment added by [[User:68.119.83.109|68.119.83.109]] ([[User talk:68.119.83.109|talk]] • [[Special:Contributions/68.119.83.109|contribs]]) 21:45, Nov 5, 2015 (UTC)</span></small>

== Cannot make it work with Vector sidebar panels ==

I've tried to incorporate this on the sidebar panels under Vector to no avail. Applying the following...
<source lang="javascript">
( function ( mw, $ ) {
$( '#mw-panel > .portal' ).each( function ( i ) {
var id = $( this ).attr( 'id' );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle-' + id );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle' );
$( this ).find( 'div' ).attr( 'id', 'mw-customcollapsible-' + id ).addClass( 'mw-collapsible mw-collapsed' );
} );
}( mediaWiki, jQuery ) );
</source>
...seems to place all the nuances class & id wise just fine but there is no collapsing or toggling of the H3 element at all (can't even force everything to collapsed state by default). When I duplicate a sidebar portal in a sandbox with the exact same structure, everything works as expected.

Is there any chance the ''mw-collapsible'' (jQuery) scheme is limited to only work within the ''.mw-body'' content container while the sidebar is outside that in it's own ''mw-navigation'' container?

Maybe it's a dependency thing?

Any help would be appreciated. Thanks in advance. -- [[User:George Orwell III|George Orwell III]] ([[User talk:George Orwell III|talk]]) 04:56, 12 December 2015 (UTC)

== mw-customcollapsible ==

Why the mw-customcollapsible application is not documented? [[Special:Contributions/93.57.251.180|93.57.251.180]] 13:46, 30 April 2016 (UTC)
:Why don't you do it yourself? <wink, wink> --[[User:Tactica amiga|Tactica amiga]] ([[User talk:Tactica amiga|talk]]) 13:58, 30 April 2016 (UTC)
::There is a line about it on [[ResourceLoader/Modules#jquery.makeCollapsible]] and on https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/jQuery.plugin.makeCollapsible. [[User:He7d3r|Helder]] 02:20, 2 May 2016 (UTC)

== Expand, collapse all? ==
I want a remote button that only expands and a button that only collapses, any ideas? mw-customtoggle seems to only toggle between them, which doesn't work that good when a couple of tables are already expanded and I want to expand all of them.

<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Expand all]'''</div>
<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Collapse all]'''</div>

<div class="mw-customtoggle-1" style="background:#e0e8ff">Collapsed table</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Some text in here.</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Other text here.</div>

<div class="mw-customtoggle-2" style="background:#e0e8ff">Expanded table</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">Even more text here.</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">No more text please.</div>

Note that I think being able to click anywhere on the table to expand is important.

== How to fix a collapsed spoiler? ==

I use spoilers type:
<pre><div class="mw-collapsible mw-collapsed">
Spoiler name
<div class="mw-collapsible-content">
Text
</div></div>
</pre>
At the same time, when the page loads - each time they are turned off, and it shows.

How to make so that it was unnoticed? Maybe there are other options spoilers?

== One toggle ==

I would like to add, at the top of some pages, a toggle to hide some sentences of the page. So I have two questions.

# Is it possible to place the show/hide toggle at the top of the page?
# Can the toggle hide/show multiple texts?

[[User:Derugon|Derugon]] ([[User talk:Derugon|talk]]) 08:40, 30 April 2017 (UTC)

== Toggle text of collapse/expand for ''custom''toggle? ==

Hi,

I have to use customtoggle because the toggler is always outside the toggle content, and here I found no solution to alter the text of the ''custom''toggle. Is there any official way to go? --[[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 13:29, 9 August 2017 (UTC)

== Selected collapsible table rows ==

{| class="wikitable mw-collapsible"
|+ Caption
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

{| class="wikitable mw-collapsible"
|-
! Header row
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

Although it only shows it with <code>div</code> elements, the documentation makes it seem as if <code>mw-collapsible-content</code> could be used on ''any'' child of a <code>mw-collapsible</code> element, but this does not work for table rows. It should – bug report or feature request? — [[:en:User:Crissov|Christoph]] [[:en:User talk:Crissov|Päper]] 13:51, 16 November 2017 (UTC)

== Click on a TOC item which lies within a currently hidden area, nothing will happen ==

If a person clicks on a TOC item which lies within a currently hidden area, nothing will happen.

It should toggle open the area, and jump to the anchor.

Seen with version 1.19.

[[User:Jidanni|Jidanni]] ([[User talk:Jidanni|talk]]) 12:14, 8 February 2018 (UTC)

== not working collapse ==

I have this in a Template, in my old MW 1.25 working fine, after update to 1.30 not working. Ahy ideas?

<nowiki><span class="_togglegroup _toggle_initshow _toggle _toggler toggle-visible" style="display:none;">[Anzeigen]</span><span class="_toggle_inithide _toggle _toggler toggle-hidden" style="display:none;">[Verstecken]</span>
<div class="_toggle_inithide _toggle toggle-hidden">
{{{1}}}</div></nowiki>

Manual talk:Collapsible elements

2018-03-29T11:02:04Z

213.61.254.68: /* not working collapse */

== Expand/Collapse All? ==

Does this have any support for an "expand all" or "collapse all" button? Pretty desperate for the ability to use such myself.

== Doesn't work? ==

This didn't work correctly in my Mediawiki 1.12.0 install. Looking at the source code of the page it created, initially hidden content is indeed hidden, but there is no "Show" link to reveal the content. Do you have any ideas? --[[User:Gadlen|Gadlen]] 19:13, 5 June 2008 (UTC)

== I'm not seeing the "hide" or "show" links ==

I'm running 1.13.4. any thoughts, could it be firefox? --[[Special:Contributions/69.244.124.138|69.244.124.138]] 01:16, 17 March 2009 (UTC)

== still doesn't work any thoughts this what is is displayed: ==

Edited both common.js and common.css
This is the header cell, which is always shown
This cell is not shown by default.

(no hide or show links)

--[[Special:Contributions/69.244.124.138|69.244.124.138]] 04:42, 25 March 2009 (UTC)

:Is this code for 13.3 + ?
--[[User:Mappc|Mappc]] 00:00, 5 April 2009 (UTC)

::I'm still interested in getting some resolution....any thoughts
--[[User:Mappc|Mappc]] 22:54, 6 April 2009 (UTC)

== This does work for me (IE6 , Firefox 3 and MediaWiki 13.4) ==
I had to change the function below the rest stay as it is. --[[User:AndreasMueller|AndreasMueller]] 21:56, 26 May 2009 (UTC)
<pre>
function createCollapseButtons()
{
var tableIndex = 0;
var NavigationBoxes = new Object();
var Tables = getElementsByClassName(document, "table", "collapsible");

for ( var i = 0; i < Tables.length; i++ ) {
/* only add button and increment count if there is a header row to work with */
var HeaderRow = Tables[i].getElementsByTagName( "tr" )[0];
if (!HeaderRow) continue;
var Header = HeaderRow.getElementsByTagName( "th" )[0];
if (!Header) continue;

NavigationBoxes[ tableIndex ] = Tables[i];
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );

var Button = document.createElement( "span" );
var ButtonLink = document.createElement( "a" );
var ButtonText = document.createTextNode( collapseCaption );

Button.className = "collapseButton"; //Styles are declared in Common.css

ButtonLink.style.color = Header.style.color;
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );
ButtonLink.appendChild( ButtonText );

Button.appendChild( document.createTextNode( "[" ) );
Button.appendChild( ButtonLink );
Button.appendChild( document.createTextNode( "]" ) );

Header.insertBefore( Button, Header.childNodes[0] );
tableIndex++;
}

var Tables = getElementsByClassName(document, "table", "collapsed");
for ( var i = 0; i < Tables.length; i++ ) {
collapseTable( i );
}

var Tables = getElementsByClassName(document, "table", "autocollapse");
for ( var i = 0; i < Tables.length; i++ ) {
if ( i >= autoCollapse ) {
collapseTable( i );
}
}
}
</pre>

== Worked A-OK ==

No editing needed over here. Using MediaWiki 1.15.1 with no other custom JS.
[[Special:Contributions/74.65.88.219|74.65.88.219]] 01:55, 7 October 2009 (UTC)

: Worked for me too on 1.15.1. At first it was very frustrating, I couldn't get it to work, but all I needed to do was the Shift-Refresh thing in my browser. =D --[[User:J.nesta|J.nesta]] 18:36, 5 November 2009 (UTC)

== hide/show placement not working ==

I updgraded to 1.15.1. Now my hide/show buttons are always on the left even though I have the Common.css file with float right. See at http://sunshinereview.org/index.php/User:Ljarratt

== 1.16 functionality ==

Beta 3. This function works flawlessly for me.
:Funny, not doing a damn thing for me (as describe, prior to 1.7 in the main article)
:MediaWiki 1.16.2
:PHP 5.2.11 (apache2handler)
:MySQL 5.0.77
:--[[Special:Contributions/99.197.224.57|99.197.224.57]] 06:04, 26 March 2011 (UTC)

==1.15.3 Not Working - Using skin Cavendish==

can anyone help with making this functional?
http://emajenanything.com/mainwiki/wiki/index.php?title=Test THANKS

== What? ==

How come I don't have neither common.js nor common.css in my wiki? how do I make this effect? :( --[[Special:Contributions/201.255.119.39|201.255.119.39]] 07:22, 19 July 2010 (UTC)
: You can create them using your search box and searching for
MediaWiki:Common.css
MediaWiki:Common.js
: --Skew 03:14, 22 September 2010 (UTC)

== show/hide: jumping to top ==

A click on my show/hide button causes the page to jump to the top. Any ideas? [[User:Gohnarch|Gohnarch]] 20:30, 27 September 2010 (UTC)

: I have same problem on two different installs of 1.15 (Ubuntu and CentOS) - tried code from "This does work for me ..." above and that seems to be OK for now ... WBN [[Special:Contributions/82.41.58.191|82.41.58.191]] 23:49, 13 October 2010 (UTC)

:That's as a result of these two lines

ButtonLink.setAttribute( 'href', '#' );
addHandler( ButtonLink, 'click', new Function( 'evt', 'collapseTable(' + tableIndex + ' ); return killEvt( evt );' ) );

:If you look at the current mw [[MediaWiki:Common.js]], it reads

ButtonLink.setAttribute( 'href', "javascript:collapseTable(" + tableIndex + ");" );

:(see [[W:Fragment identifier]]). I will update the page to show this change if that is all right with everybody. --[[User:JCrue|JCrue]] 18:24, 30 November 2010 (UTC)

== Still not working ==

Hi, I'm trying to install this on 1.15, and the "hide/show" tags aren't appearing. I've edited the common.js and common.css, as above and as shown on the article page, purged webcaches, etc, etc, and still no go. Any ideas for how to troubleshoot this? - very frustrating!

== 1.17 example not working on diffs ==

Hi!

I noticed that the new examples doesn't works when the page is seen in a diff like [http://www.mediawiki.org/w/index.php?title=Manual:Collapsible_tables&diff=cur&oldid=367004#After_1.17 this]. I think it should work even in this case (not only when viewing the page directly). [[b:pt:User:Helder.wiki|Helder]] 16:03, 23 February 2011 (UTC)
: During development it worked fine in preview, diff and oldid view. Will look into it. [[User:Krinkle|Krinkle]] 11:00, 24 February 2011 (UTC)
:: It does work in the latest development version, as for example ran on TranslateWiki, [http://translatewiki.net/w/i.php?title=User%3AKrinkle%2FCollapsingTestpageMw&diff=2756282 here]. Hm.. [[User:Krinkle|Krinkle]] 11:32, 24 February 2011 (UTC)
::: Seems the cause isn't in the script after all. The problem is the FlaggedRevisions-extension which loads the page-contents afterwards via JavaScript causing any onload handlers to fail miserably since there isn't a page at that time (TOC-toggle, mw-collapsible, mw.util.$content) See also [[bugzilla: 26175]] and [[bugzilla: 27513]]. I can't fix this untill FlaggedRevs has some kind of hook or is fixed otherwise. Any javascript handlers will fail (potentially $.fn.placeholder and $.fn.checkboxShiftClick as well) [[User:Krinkle|Krinkle]]

== Cannot get Collapse to work in 1.17 ==

I have tried to different 1.17 installs and I cannot get collapse to work at all. I am following the examples exactly:

:<nowiki><div class="toccolours mw-collapsible" style="width:400px"></nowiki>
:<nowiki>This is text is collapsible. {{Lorem}}</nowiki>
:<nowiki></div></nowiki>

Just shows the text. There is no option to collapse. The other examples give the same results. The ability to collapse is completely missing, even though the directions say "After 1.17... Basically all you do is add the class "mw-collapsible" to an element." What am I missing?

* Site #1: http://wiki.cyanogenmod.com/wiki/User:Pconwell/sandbox2
* Site #2: http://w.gu1dry.com/User:Pconwell/Sandbox2

: I can't get this to work over at http://everquest.wikkii.net either. I also couldn't get the old style of collapsible tables using common.css and common.js to work either. I'm going nuts trying to figure out what I have done wrong. [[Special:Contributions/24.40.138.185|24.40.138.185]] 21:52, 24 June 2011 (UTC)

On [[ResourceLoader/Default_modules#jQuery.makeCollapsible]] it is said that this feature is currently available on trunk, since [[rev:78914]], but there is no mention of MW 1.'''17'''. So, I think this page is outdated.

Anyway, on [[meta:User_talk:Krinkle/1-17-allwikis#Wikis_using_jquery.makeCollapsible|this page]] it is explained how to install the plugin on MW 1.17 (as was made here on MediaWiki.org). [[b:pt:User:Helder.wiki|Helder]] 12:43, 28 June 2011 (UTC)

: Thank you for your concern. I had created MediaWiki:JQuery-makeCollapsible.js and MediaWiki:JQuery-makeCollapsible.css on my wiki and put the two lines in my Common.js before posting here. But it just doesn't seem to work. Neither does the old style collapsible tables. I'm at a loss here to understand why. [[Special:Contributions/24.40.138.185|24.40.138.185]] 07:29, 29 June 2011 (UTC)
::Notice that the current code of your MediaWiki:Common.js has syntax errors before the makeCollapsible plugin is loaded (copy and paste it on [http://jshint.com/ JSHint] to check the syntax). Specifically, this will not work: <syntaxhighlight lang="javascript">if ( {{PAGENAME}} == 'Main Page' )</syntaxhighlight>
::So, I think the plugin will work if you add [http://everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&curid=439&diff=1181&oldid=1029 these lines] again and fix the syntax errors above (or just remove everything from [http://everquest.wikkii.net/w/index.php?title=MediaWiki:Common.js&action=edit your MediaWiki:Common.js] except this:
<syntaxhighlight lang="javascript">/* FROM MEDIAWIKI.ORG COMMON.JS Load collapsible javascript */
mw.loader.load( 'http://www.everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&action=raw&ctype=text/javascript' );
</syntaxhighlight>
::) and clear your cache. [[b:pt:User:Helder.wiki|Helder]] 13:18, 29 June 2011 (UTC)

::: Helder, thank you a million times. That was the problem all right. Thanks. [[Special:Contributions/24.40.138.185|24.40.138.185]] 06:22, 30 June 2011 (UTC)

== Indication of collapsed/expandable status ==
: ''<small>Moved from [http://meta.wikimedia.org/w/index.php?title=User_talk:Krinkle/1-17-allwikis&oldid=2703017#Indication_of_collapsed.2Fexpandable_status Meta-Wiki]</small>''

Hi,

This might be the wrong place to ask, but we were wondering if their is an easy way to know which status of the class="mw-customtoggle-myDivision" is set in terms of being collapsed/expandable.

Using the standard solution indicates the status through the display of either [Collapsed] or [Expand], in our case we trigger the area which need to be collapsed with the display of an icon, and as soon the user switches from one status to the other one we wanted to indicated a change through a change in the icon displayed.
<pre>
<div class="mw-customtoggle-topicon" style="cursor:pointer">[[File:icon-set-10-arrow-down.png|14px|link=]]</div>
</pre>
So in case the class contains "mw-collapsible mw-collapsed" display one type of icon, and in case of the class just being "mw-collapsible" display another icon. --[[m:User:MWJames|MWJames]] 18:13, 6 July 2011 (UTC)
: Hi MWJames,
: If you can provide a link to where this happends on a live-wiki I may be able to give a more fine-tuned detail. I'll show you how I would do it though. I'm assuming your toggle-icon is inside {{tag|div|params= class="mw-collasible"}}:
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible">
<div class="mw-collapsible-toggle toccolours" style="width: 100%">
<span class="down">[[File:Arrow-down-dash-2.0.svg|50px|center|link=]]</span>
<span class="up">[[File:Arrow-up-dash-2.0.svg|50px|center|link=]]</span>
</div>
<div class="mw-collapsible-content">
{{User:Krinkle/Lorem}}
</div>
</div>
</pre>

CSS:
<source lang="css">
#collapse-pre-one .mw-collapsible-toggle .up,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .down {
display: none;
}
#collapse-pre-one .mw-collapsible-toggle .down,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .up {
display: block;
}
</source>
</blockquote>
: A demo of this can be found at [[testwiki:User:Krinkle/CollapsingTestpageMw#collapse-pre-one]]
: Note that the <code>collapse-pre-one</code> is not required, it's just to make sure it won't apply to other collapsible constructions on the same page. Use whatever identifier you like [[User:Krinkle|Krinkle]] 21:14, 6 July 2011 (UTC)

== makeCollapsible "in core" ==

Does "in core as of MediaWiki 1.18 or higher" mean that it will be enabled by default on all wikis, loaded and activated on every page? If so, will there be any way to disable it? --[[User:Yair rand|Yair rand]] 08:54, 14 July 2011 (UTC)
: There is nothing to disable as all the scripts mentioned on this page are only triggered if there are elements on the page marked as "mw-collapsible". If your wiki doesn't want or have collapsible elements, this script will not be triggered and nothing will change when upgrading to 1.18. [[User:Krinkle|Krinkle]] 04:21, 4 August 2011 (UTC)
::Really? It won't even load the scripts or take up time running any JS if there aren't any mw-collapsible elements in the wikitext? --[[User:Yair rand|Yair rand]] 05:14, 4 August 2011 (UTC)

== Use new 1.18 collapsible in 1.17 ==

You can use the new 1.18 collapsible code in a 1.17 install. Just paste the contents of jquery-makeCollapsible.js into your MediaWiki:Common.js

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.js?view=co Download head version from MediaWiki]

Then at the bottom of MediaWiki:Common.js, add:

mw.messages.set({"collapsible-collapse":"Collapse","collapsible-expand":"Expand"});
$(document).ready(function(){
$('.mw-collapsible').makeCollapsible();
});

And add the contents of jquery.makeCollapsible.css into your MediaWiki:Common.css

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.css?view=co Download head version from MediaWiki]

If there is a tidier way of doing this, please let me know. --[[User:Thenickdude|Thenickdude]] 11:33, 13 September 2011 (UTC)

== Autocollapse ==

Has a version of autocollapse been implemented in core in 1.18? --<small style="background:#f00">'''★ [[User:Airon90|<span style="color:#000">→ A</span>]][[Special:Contributions/Airon90|<span style="color:#f00;background:#000">ir</span>]][[User talk:Airon90|<span style="color:#000">on Ĉ</span>]]'''</small> 14:09, 7 October 2011 (UTC)

== Common.js script (Before 1.18) don't works ==

Hey there!

I have some Wikis running on an Debian Linux 6.0 (Squeeze) Webserver.<br>
MediaWiki 1.17.0 (Version 95135)<br>
PHP 5.3.3-7+squeeze3 (apache2handler)<br>
MySQL 5.1.49-3<br>

and i have the Problem, that this Collapse Hide & Show didnt works. I try it on two local Servers installed in Virtual Box and i have there the same problem. Could it be, that Debian Squeeze is the problem? Ive tryd all things, that i found here. But without a happy ending... [[User:Yukii|Yukii]] 12:27, 10 October 2011 (UTC)

== mw-collapsible will not work (1.18) ==

I've copied and pasted the examples and none of them work no matter what I do - upgraded my wiki, completely reinstalled the wiki, no dice. [[User:Leangle|Leangle]] 8:54 PM, Dec 29 2011

== Customizing Collapse/Expand location ==

Using 1.18, how would I customize the mw-collapsible mw-collapsed CSS so that the 'Expand' or 'Collapse' buttons appear on the left?

I'm thinking of something like what the mobile site does for certain sections - rather than having the 'expand' button float out of site off to the right, i'd prefer it to be on the left. It doesn't necessarily need to use a button, but that would be interesting as well.

[[Special:Contributions/66.3.56.92|66.3.56.92]] 23:21, 1 March 2012 (UTC)

Update:

Solved it, more or less

/* leave toggle on the right for tables */
.tablecollapse span.mw-collapsible-toggle{
float:right;
}

/* put it on the left for everything else */
.collapse span.mw-collapsible-toggle {
float: left;
}

By setting those classes, I can make sure that for tables, the toggle still appears where it should, and for other areas, the toggle appears floating left.

not sure how to swap out images, but at this point, thats no big deal. Hope this helps someone.

Another way:<br>
For those of you who don't like having the toggle right beside text, here's how to make text appear below it:
.mw-collapsible-toggle {
display:inline-block;
float:none;
}

[[User:Bluekuma|Bluekuma]] ([[User talk:Bluekuma|talk]]) 17:43, 22 May 2015 (UTC)

== Only Works for Anons ==

When i log into my wiki the expand/collapse links disappear and all content within them defaults to expanded. Any idea on how to fix this? I'm thinking it's not loading the java after login but don't know what to change to fix it.

Thanks!

== Extensions that disrupts collapsible elements. ==

I notice that with mediwiki 1.17 I didn't have any collapsible elements, even doing all the things to be done. I upgrade to mediawiki 1.18, and didn't work.

So I notice that, when '''I disable''' the [http://www.mediawiki.org/wiki/Extension:Page_Object_Model Page Object Model] Extension It worked.

Check it.

== 1.19.1 Nested Collapsible elements ==
{{tracked|35257}}
In 1.19.1, using the builtin JQuery mw-collapsible and mw-collapsed classes works as expected, except if you have nested elements and "Expand" a collapsed element, it will also expand all nested elements. Ideally this could either be toggled via a setting or by default not expand all child collapsible elements.
:That seems to be [[bugzilla:35257]]. [[b:pt:User:Helder.wiki|Helder]] 18:31, 6 July 2012 (UTC)

== 19.2 - Collapsible Elements Load Open ==

I was previously using the now obsolete [[Extension:ToggleDisplay|ToggleDisplay]] extension which worked nicely but now after upgrading to 1.19.2 I have started trying to use the built in Collapsible elements feature. It seems fine but when the page loads, all toggle areas load as open and only close once the page is completely loaded. This creates a kind of unwanted stutter in the visual loading of the page.
Can this be fixed or is there a way to use Collapsible elements so it doesn't do this? The reason I mention the extension above is that it doesn't do this. The page loads with elements already closed and it looks great. Would love to have that effect again.

== Loading issue ==

Is it possible to keep all the content collapsed while the rest of the page loads? I have a problem that, on pages with many images and other content, the information that I have initially collapsed is visible until the entire page loads in the browser.
: It looks like this has been a proper nuisance for some time already. [[User:Cavila|Cavila]] <sup>MW 1.19.2, MySQL 5.1.63, Php 5.3.3-7, SMW 1.8</sup> 22:47, 17 January 2013 (UTC) {{tracked|34876}}

== Broken in Old Custom Skins ==

This functionality has been completely destroyed in pre 1.17 skins. It is impossible to implement any of the fixes suggested as the skins do not conform to the new framework, and the files used in the old framework no longer exist. Can anyone suggest a fix to re-implement this behaviour in pre 1.17 skins?

== Custom Toggle with arrow indicator and header ==
This code makes a nice Toggle element with an Arror indicator image. The image can be anything really but an arrow is the most logical choice.<br>
I have not tested backwards compatibility on this for MediaWiki versions < V1.21.<br>
Credit goes to [[User:Krinkle|Krinkle]] as this was adapted from his examples.
<br>
A demo can be seen here: [http://test.wikipedia.org/wiki/User:Shift9999#collapse-pre-one| Toggle with Arrow]
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible mw-collapsed">
<div class="mw-collapsible-toggle toccolours" style="float: none;">
<div class="mw-collapsible-toggle-row">
<div class="mw-collapsible-toggle-header"><big>'''Example Header'''<br>Example sub</big></div>
<div class="mw-collapsible-toggle-indicator">[[File:right-black-arrow.png|150px|link=]]</div>
</div>
</div>
<div class="mw-collapsible-content">
{{Lorem}}
</div>
</pre>

CSS:
<source lang="css">
/* Collapse Toggle container */
#collapse-pre-one .mw-collapsible-toggle{
display: table;
border-collapse: collapse;
width: 100%;
}

#collapse-pre-one .mw-collapsible-toggle-row{
display: table-row;
}

/* Collapse Header should be on the left */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-header{
display: table-cell;
vertical-align: middle;
padding: 5px;
}

/* Collapse indicator image should be inline. align wherever you would like */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator{
display: table-cell;
vertical-align: middle;
padding: 5px;
text-align: right;
}

/* Collapse indicator image size should be something sane*/
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
height: 20px !important;
width: 20px !important;
}

/* Collapse indicator image should rotate when toggled*/
#collapse-pre-one:not(.mw-collapsed) .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
/* Safari */
-webkit-transform: rotate(90deg);

/* Firefox */
-moz-transform: rotate(90deg);

/* IE */
-ms-transform: rotate(90deg);

/* Opera */
-o-transform: rotate(90deg);

/* Internet Explorer */
filter: progid:DXImageTransform.Microsoft.BasicImage(rotation=1);
}
</source>
</blockquote>
--[[User:Shift9999|Shift9999]] at 2:06AM PST - 07-17-2013

== on() causes problems for older jq versions ==

In the code for collpasible tables, on() is used to bind behavior to the <a> for the show/hide button.... This is a jq function introduced in 1.4.2, so if you're using an older jq version, instead use the (old) bind() method instead of on().

== Font color of collapsible button ==

{|class="mw-collapsible" style="float:right;background:#00f;color:#fff"
!Header
|-
|Collapsed content
|}
Previously the font color of collapsible button was inheritable but now it doesn't. The problem is if someone changes the background color of talbe/div to blue, the [expand/collapse] button text is almost invisible even if the user has set color:#fff. -- [[User:Sameboat|Sameboat]] ([[User talk:Sameboat|talk]]) 02:44, 7 February 2014 (UTC)
: Is there any news about this issue? --[[User:Rotpunkt|Rotpunkt]] ([[User talk:Rotpunkt|talk]]) 10:09, 23 May 2016 (UTC)

== Wasn't this feature removed from the latest update? It is not in 1.24.1 ==

I think this has been removed. How do I get it back for new updates? <small><span class="autosigned">— Preceding [[w:Signatures|unsigned]] comment added by [[User:68.119.83.109|68.119.83.109]] ([[User talk:68.119.83.109|talk]] • [[Special:Contributions/68.119.83.109|contribs]]) 21:45, Nov 5, 2015 (UTC)</span></small>

== Cannot make it work with Vector sidebar panels ==

I've tried to incorporate this on the sidebar panels under Vector to no avail. Applying the following...
<source lang="javascript">
( function ( mw, $ ) {
$( '#mw-panel > .portal' ).each( function ( i ) {
var id = $( this ).attr( 'id' );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle-' + id );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle' );
$( this ).find( 'div' ).attr( 'id', 'mw-customcollapsible-' + id ).addClass( 'mw-collapsible mw-collapsed' );
} );
}( mediaWiki, jQuery ) );
</source>
...seems to place all the nuances class & id wise just fine but there is no collapsing or toggling of the H3 element at all (can't even force everything to collapsed state by default). When I duplicate a sidebar portal in a sandbox with the exact same structure, everything works as expected.

Is there any chance the ''mw-collapsible'' (jQuery) scheme is limited to only work within the ''.mw-body'' content container while the sidebar is outside that in it's own ''mw-navigation'' container?

Maybe it's a dependency thing?

Any help would be appreciated. Thanks in advance. -- [[User:George Orwell III|George Orwell III]] ([[User talk:George Orwell III|talk]]) 04:56, 12 December 2015 (UTC)

== mw-customcollapsible ==

Why the mw-customcollapsible application is not documented? [[Special:Contributions/93.57.251.180|93.57.251.180]] 13:46, 30 April 2016 (UTC)
:Why don't you do it yourself? <wink, wink> --[[User:Tactica amiga|Tactica amiga]] ([[User talk:Tactica amiga|talk]]) 13:58, 30 April 2016 (UTC)
::There is a line about it on [[ResourceLoader/Modules#jquery.makeCollapsible]] and on https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/jQuery.plugin.makeCollapsible. [[User:He7d3r|Helder]] 02:20, 2 May 2016 (UTC)

== Expand, collapse all? ==
I want a remote button that only expands and a button that only collapses, any ideas? mw-customtoggle seems to only toggle between them, which doesn't work that good when a couple of tables are already expanded and I want to expand all of them.

<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Expand all]'''</div>
<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Collapse all]'''</div>

<div class="mw-customtoggle-1" style="background:#e0e8ff">Collapsed table</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Some text in here.</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Other text here.</div>

<div class="mw-customtoggle-2" style="background:#e0e8ff">Expanded table</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">Even more text here.</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">No more text please.</div>

Note that I think being able to click anywhere on the table to expand is important.

== How to fix a collapsed spoiler? ==

I use spoilers type:
<pre><div class="mw-collapsible mw-collapsed">
Spoiler name
<div class="mw-collapsible-content">
Text
</div></div>
</pre>
At the same time, when the page loads - each time they are turned off, and it shows.

How to make so that it was unnoticed? Maybe there are other options spoilers?

== One toggle ==

I would like to add, at the top of some pages, a toggle to hide some sentences of the page. So I have two questions.

# Is it possible to place the show/hide toggle at the top of the page?
# Can the toggle hide/show multiple texts?

[[User:Derugon|Derugon]] ([[User talk:Derugon|talk]]) 08:40, 30 April 2017 (UTC)

== Toggle text of collapse/expand for ''custom''toggle? ==

Hi,

I have to use customtoggle because the toggler is always outside the toggle content, and here I found no solution to alter the text of the ''custom''toggle. Is there any official way to go? --[[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 13:29, 9 August 2017 (UTC)

== Selected collapsible table rows ==

{| class="wikitable mw-collapsible"
|+ Caption
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

{| class="wikitable mw-collapsible"
|-
! Header row
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

Although it only shows it with <code>div</code> elements, the documentation makes it seem as if <code>mw-collapsible-content</code> could be used on ''any'' child of a <code>mw-collapsible</code> element, but this does not work for table rows. It should – bug report or feature request? — [[:en:User:Crissov|Christoph]] [[:en:User talk:Crissov|Päper]] 13:51, 16 November 2017 (UTC)

== Click on a TOC item which lies within a currently hidden area, nothing will happen ==

If a person clicks on a TOC item which lies within a currently hidden area, nothing will happen.

It should toggle open the area, and jump to the anchor.

Seen with version 1.19.

[[User:Jidanni|Jidanni]] ([[User talk:Jidanni|talk]]) 12:14, 8 February 2018 (UTC)

== not working collapse ==

I have this in a Template, in my old MW 1.25 working fine, after update to 1.30 not working. Ahy ideas?

<span class="_togglegroup _toggle_initshow _toggle _toggler toggle-visible" style="display:none;">[Anzeigen]</span><span class="_toggle_inithide _toggle _toggler toggle-hidden" style="display:none;">[Verstecken]</span>
<div class="_toggle_inithide _toggle toggle-hidden">
{{{1}}}</div>

Manual talk:Collapsible elements

2018-03-29T11:01:45Z

213.61.254.68: /* not working collapse */

== Expand/Collapse All? ==

Does this have any support for an "expand all" or "collapse all" button? Pretty desperate for the ability to use such myself.

== Doesn't work? ==

This didn't work correctly in my Mediawiki 1.12.0 install. Looking at the source code of the page it created, initially hidden content is indeed hidden, but there is no "Show" link to reveal the content. Do you have any ideas? --[[User:Gadlen|Gadlen]] 19:13, 5 June 2008 (UTC)

== I'm not seeing the "hide" or "show" links ==

I'm running 1.13.4. any thoughts, could it be firefox? --[[Special:Contributions/69.244.124.138|69.244.124.138]] 01:16, 17 March 2009 (UTC)

== still doesn't work any thoughts this what is is displayed: ==

Edited both common.js and common.css
This is the header cell, which is always shown
This cell is not shown by default.

(no hide or show links)

--[[Special:Contributions/69.244.124.138|69.244.124.138]] 04:42, 25 March 2009 (UTC)

:Is this code for 13.3 + ?
--[[User:Mappc|Mappc]] 00:00, 5 April 2009 (UTC)

::I'm still interested in getting some resolution....any thoughts
--[[User:Mappc|Mappc]] 22:54, 6 April 2009 (UTC)

== This does work for me (IE6 , Firefox 3 and MediaWiki 13.4) ==
I had to change the function below the rest stay as it is. --[[User:AndreasMueller|AndreasMueller]] 21:56, 26 May 2009 (UTC)
<pre>
function createCollapseButtons()
{
var tableIndex = 0;
var NavigationBoxes = new Object();
var Tables = getElementsByClassName(document, "table", "collapsible");

for ( var i = 0; i < Tables.length; i++ ) {
/* only add button and increment count if there is a header row to work with */
var HeaderRow = Tables[i].getElementsByTagName( "tr" )[0];
if (!HeaderRow) continue;
var Header = HeaderRow.getElementsByTagName( "th" )[0];
if (!Header) continue;

NavigationBoxes[ tableIndex ] = Tables[i];
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );

var Button = document.createElement( "span" );
var ButtonLink = document.createElement( "a" );
var ButtonText = document.createTextNode( collapseCaption );

Button.className = "collapseButton"; //Styles are declared in Common.css

ButtonLink.style.color = Header.style.color;
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );
ButtonLink.appendChild( ButtonText );

Button.appendChild( document.createTextNode( "[" ) );
Button.appendChild( ButtonLink );
Button.appendChild( document.createTextNode( "]" ) );

Header.insertBefore( Button, Header.childNodes[0] );
tableIndex++;
}

var Tables = getElementsByClassName(document, "table", "collapsed");
for ( var i = 0; i < Tables.length; i++ ) {
collapseTable( i );
}

var Tables = getElementsByClassName(document, "table", "autocollapse");
for ( var i = 0; i < Tables.length; i++ ) {
if ( i >= autoCollapse ) {
collapseTable( i );
}
}
}
</pre>

== Worked A-OK ==

No editing needed over here. Using MediaWiki 1.15.1 with no other custom JS.
[[Special:Contributions/74.65.88.219|74.65.88.219]] 01:55, 7 October 2009 (UTC)

: Worked for me too on 1.15.1. At first it was very frustrating, I couldn't get it to work, but all I needed to do was the Shift-Refresh thing in my browser. =D --[[User:J.nesta|J.nesta]] 18:36, 5 November 2009 (UTC)

== hide/show placement not working ==

I updgraded to 1.15.1. Now my hide/show buttons are always on the left even though I have the Common.css file with float right. See at http://sunshinereview.org/index.php/User:Ljarratt

== 1.16 functionality ==

Beta 3. This function works flawlessly for me.
:Funny, not doing a damn thing for me (as describe, prior to 1.7 in the main article)
:MediaWiki 1.16.2
:PHP 5.2.11 (apache2handler)
:MySQL 5.0.77
:--[[Special:Contributions/99.197.224.57|99.197.224.57]] 06:04, 26 March 2011 (UTC)

==1.15.3 Not Working - Using skin Cavendish==

can anyone help with making this functional?
http://emajenanything.com/mainwiki/wiki/index.php?title=Test THANKS

== What? ==

How come I don't have neither common.js nor common.css in my wiki? how do I make this effect? :( --[[Special:Contributions/201.255.119.39|201.255.119.39]] 07:22, 19 July 2010 (UTC)
: You can create them using your search box and searching for
MediaWiki:Common.css
MediaWiki:Common.js
: --Skew 03:14, 22 September 2010 (UTC)

== show/hide: jumping to top ==

A click on my show/hide button causes the page to jump to the top. Any ideas? [[User:Gohnarch|Gohnarch]] 20:30, 27 September 2010 (UTC)

: I have same problem on two different installs of 1.15 (Ubuntu and CentOS) - tried code from "This does work for me ..." above and that seems to be OK for now ... WBN [[Special:Contributions/82.41.58.191|82.41.58.191]] 23:49, 13 October 2010 (UTC)

:That's as a result of these two lines

ButtonLink.setAttribute( 'href', '#' );
addHandler( ButtonLink, 'click', new Function( 'evt', 'collapseTable(' + tableIndex + ' ); return killEvt( evt );' ) );

:If you look at the current mw [[MediaWiki:Common.js]], it reads

ButtonLink.setAttribute( 'href', "javascript:collapseTable(" + tableIndex + ");" );

:(see [[W:Fragment identifier]]). I will update the page to show this change if that is all right with everybody. --[[User:JCrue|JCrue]] 18:24, 30 November 2010 (UTC)

== Still not working ==

Hi, I'm trying to install this on 1.15, and the "hide/show" tags aren't appearing. I've edited the common.js and common.css, as above and as shown on the article page, purged webcaches, etc, etc, and still no go. Any ideas for how to troubleshoot this? - very frustrating!

== 1.17 example not working on diffs ==

Hi!

I noticed that the new examples doesn't works when the page is seen in a diff like [http://www.mediawiki.org/w/index.php?title=Manual:Collapsible_tables&diff=cur&oldid=367004#After_1.17 this]. I think it should work even in this case (not only when viewing the page directly). [[b:pt:User:Helder.wiki|Helder]] 16:03, 23 February 2011 (UTC)
: During development it worked fine in preview, diff and oldid view. Will look into it. [[User:Krinkle|Krinkle]] 11:00, 24 February 2011 (UTC)
:: It does work in the latest development version, as for example ran on TranslateWiki, [http://translatewiki.net/w/i.php?title=User%3AKrinkle%2FCollapsingTestpageMw&diff=2756282 here]. Hm.. [[User:Krinkle|Krinkle]] 11:32, 24 February 2011 (UTC)
::: Seems the cause isn't in the script after all. The problem is the FlaggedRevisions-extension which loads the page-contents afterwards via JavaScript causing any onload handlers to fail miserably since there isn't a page at that time (TOC-toggle, mw-collapsible, mw.util.$content) See also [[bugzilla: 26175]] and [[bugzilla: 27513]]. I can't fix this untill FlaggedRevs has some kind of hook or is fixed otherwise. Any javascript handlers will fail (potentially $.fn.placeholder and $.fn.checkboxShiftClick as well) [[User:Krinkle|Krinkle]]

== Cannot get Collapse to work in 1.17 ==

I have tried to different 1.17 installs and I cannot get collapse to work at all. I am following the examples exactly:

:<nowiki><div class="toccolours mw-collapsible" style="width:400px"></nowiki>
:<nowiki>This is text is collapsible. {{Lorem}}</nowiki>
:<nowiki></div></nowiki>

Just shows the text. There is no option to collapse. The other examples give the same results. The ability to collapse is completely missing, even though the directions say "After 1.17... Basically all you do is add the class "mw-collapsible" to an element." What am I missing?

* Site #1: http://wiki.cyanogenmod.com/wiki/User:Pconwell/sandbox2
* Site #2: http://w.gu1dry.com/User:Pconwell/Sandbox2

: I can't get this to work over at http://everquest.wikkii.net either. I also couldn't get the old style of collapsible tables using common.css and common.js to work either. I'm going nuts trying to figure out what I have done wrong. [[Special:Contributions/24.40.138.185|24.40.138.185]] 21:52, 24 June 2011 (UTC)

On [[ResourceLoader/Default_modules#jQuery.makeCollapsible]] it is said that this feature is currently available on trunk, since [[rev:78914]], but there is no mention of MW 1.'''17'''. So, I think this page is outdated.

Anyway, on [[meta:User_talk:Krinkle/1-17-allwikis#Wikis_using_jquery.makeCollapsible|this page]] it is explained how to install the plugin on MW 1.17 (as was made here on MediaWiki.org). [[b:pt:User:Helder.wiki|Helder]] 12:43, 28 June 2011 (UTC)

: Thank you for your concern. I had created MediaWiki:JQuery-makeCollapsible.js and MediaWiki:JQuery-makeCollapsible.css on my wiki and put the two lines in my Common.js before posting here. But it just doesn't seem to work. Neither does the old style collapsible tables. I'm at a loss here to understand why. [[Special:Contributions/24.40.138.185|24.40.138.185]] 07:29, 29 June 2011 (UTC)
::Notice that the current code of your MediaWiki:Common.js has syntax errors before the makeCollapsible plugin is loaded (copy and paste it on [http://jshint.com/ JSHint] to check the syntax). Specifically, this will not work: <syntaxhighlight lang="javascript">if ( {{PAGENAME}} == 'Main Page' )</syntaxhighlight>
::So, I think the plugin will work if you add [http://everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&curid=439&diff=1181&oldid=1029 these lines] again and fix the syntax errors above (or just remove everything from [http://everquest.wikkii.net/w/index.php?title=MediaWiki:Common.js&action=edit your MediaWiki:Common.js] except this:
<syntaxhighlight lang="javascript">/* FROM MEDIAWIKI.ORG COMMON.JS Load collapsible javascript */
mw.loader.load( 'http://www.everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&action=raw&ctype=text/javascript' );
</syntaxhighlight>
::) and clear your cache. [[b:pt:User:Helder.wiki|Helder]] 13:18, 29 June 2011 (UTC)

::: Helder, thank you a million times. That was the problem all right. Thanks. [[Special:Contributions/24.40.138.185|24.40.138.185]] 06:22, 30 June 2011 (UTC)

== Indication of collapsed/expandable status ==
: ''<small>Moved from [http://meta.wikimedia.org/w/index.php?title=User_talk:Krinkle/1-17-allwikis&oldid=2703017#Indication_of_collapsed.2Fexpandable_status Meta-Wiki]</small>''

Hi,

This might be the wrong place to ask, but we were wondering if their is an easy way to know which status of the class="mw-customtoggle-myDivision" is set in terms of being collapsed/expandable.

Using the standard solution indicates the status through the display of either [Collapsed] or [Expand], in our case we trigger the area which need to be collapsed with the display of an icon, and as soon the user switches from one status to the other one we wanted to indicated a change through a change in the icon displayed.
<pre>
<div class="mw-customtoggle-topicon" style="cursor:pointer">[[File:icon-set-10-arrow-down.png|14px|link=]]</div>
</pre>
So in case the class contains "mw-collapsible mw-collapsed" display one type of icon, and in case of the class just being "mw-collapsible" display another icon. --[[m:User:MWJames|MWJames]] 18:13, 6 July 2011 (UTC)
: Hi MWJames,
: If you can provide a link to where this happends on a live-wiki I may be able to give a more fine-tuned detail. I'll show you how I would do it though. I'm assuming your toggle-icon is inside {{tag|div|params= class="mw-collasible"}}:
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible">
<div class="mw-collapsible-toggle toccolours" style="width: 100%">
<span class="down">[[File:Arrow-down-dash-2.0.svg|50px|center|link=]]</span>
<span class="up">[[File:Arrow-up-dash-2.0.svg|50px|center|link=]]</span>
</div>
<div class="mw-collapsible-content">
{{User:Krinkle/Lorem}}
</div>
</div>
</pre>

CSS:
<source lang="css">
#collapse-pre-one .mw-collapsible-toggle .up,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .down {
display: none;
}
#collapse-pre-one .mw-collapsible-toggle .down,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .up {
display: block;
}
</source>
</blockquote>
: A demo of this can be found at [[testwiki:User:Krinkle/CollapsingTestpageMw#collapse-pre-one]]
: Note that the <code>collapse-pre-one</code> is not required, it's just to make sure it won't apply to other collapsible constructions on the same page. Use whatever identifier you like [[User:Krinkle|Krinkle]] 21:14, 6 July 2011 (UTC)

== makeCollapsible "in core" ==

Does "in core as of MediaWiki 1.18 or higher" mean that it will be enabled by default on all wikis, loaded and activated on every page? If so, will there be any way to disable it? --[[User:Yair rand|Yair rand]] 08:54, 14 July 2011 (UTC)
: There is nothing to disable as all the scripts mentioned on this page are only triggered if there are elements on the page marked as "mw-collapsible". If your wiki doesn't want or have collapsible elements, this script will not be triggered and nothing will change when upgrading to 1.18. [[User:Krinkle|Krinkle]] 04:21, 4 August 2011 (UTC)
::Really? It won't even load the scripts or take up time running any JS if there aren't any mw-collapsible elements in the wikitext? --[[User:Yair rand|Yair rand]] 05:14, 4 August 2011 (UTC)

== Use new 1.18 collapsible in 1.17 ==

You can use the new 1.18 collapsible code in a 1.17 install. Just paste the contents of jquery-makeCollapsible.js into your MediaWiki:Common.js

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.js?view=co Download head version from MediaWiki]

Then at the bottom of MediaWiki:Common.js, add:

mw.messages.set({"collapsible-collapse":"Collapse","collapsible-expand":"Expand"});
$(document).ready(function(){
$('.mw-collapsible').makeCollapsible();
});

And add the contents of jquery.makeCollapsible.css into your MediaWiki:Common.css

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.css?view=co Download head version from MediaWiki]

If there is a tidier way of doing this, please let me know. --[[User:Thenickdude|Thenickdude]] 11:33, 13 September 2011 (UTC)

== Autocollapse ==

Has a version of autocollapse been implemented in core in 1.18? --<small style="background:#f00">'''★ [[User:Airon90|<span style="color:#000">→ A</span>]][[Special:Contributions/Airon90|<span style="color:#f00;background:#000">ir</span>]][[User talk:Airon90|<span style="color:#000">on Ĉ</span>]]'''</small> 14:09, 7 October 2011 (UTC)

== Common.js script (Before 1.18) don't works ==

Hey there!

I have some Wikis running on an Debian Linux 6.0 (Squeeze) Webserver.<br>
MediaWiki 1.17.0 (Version 95135)<br>
PHP 5.3.3-7+squeeze3 (apache2handler)<br>
MySQL 5.1.49-3<br>

and i have the Problem, that this Collapse Hide & Show didnt works. I try it on two local Servers installed in Virtual Box and i have there the same problem. Could it be, that Debian Squeeze is the problem? Ive tryd all things, that i found here. But without a happy ending... [[User:Yukii|Yukii]] 12:27, 10 October 2011 (UTC)

== mw-collapsible will not work (1.18) ==

I've copied and pasted the examples and none of them work no matter what I do - upgraded my wiki, completely reinstalled the wiki, no dice. [[User:Leangle|Leangle]] 8:54 PM, Dec 29 2011

== Customizing Collapse/Expand location ==

Using 1.18, how would I customize the mw-collapsible mw-collapsed CSS so that the 'Expand' or 'Collapse' buttons appear on the left?

I'm thinking of something like what the mobile site does for certain sections - rather than having the 'expand' button float out of site off to the right, i'd prefer it to be on the left. It doesn't necessarily need to use a button, but that would be interesting as well.

[[Special:Contributions/66.3.56.92|66.3.56.92]] 23:21, 1 March 2012 (UTC)

Update:

Solved it, more or less

/* leave toggle on the right for tables */
.tablecollapse span.mw-collapsible-toggle{
float:right;
}

/* put it on the left for everything else */
.collapse span.mw-collapsible-toggle {
float: left;
}

By setting those classes, I can make sure that for tables, the toggle still appears where it should, and for other areas, the toggle appears floating left.

not sure how to swap out images, but at this point, thats no big deal. Hope this helps someone.

Another way:<br>
For those of you who don't like having the toggle right beside text, here's how to make text appear below it:
.mw-collapsible-toggle {
display:inline-block;
float:none;
}

[[User:Bluekuma|Bluekuma]] ([[User talk:Bluekuma|talk]]) 17:43, 22 May 2015 (UTC)

== Only Works for Anons ==

When i log into my wiki the expand/collapse links disappear and all content within them defaults to expanded. Any idea on how to fix this? I'm thinking it's not loading the java after login but don't know what to change to fix it.

Thanks!

== Extensions that disrupts collapsible elements. ==

I notice that with mediwiki 1.17 I didn't have any collapsible elements, even doing all the things to be done. I upgrade to mediawiki 1.18, and didn't work.

So I notice that, when '''I disable''' the [http://www.mediawiki.org/wiki/Extension:Page_Object_Model Page Object Model] Extension It worked.

Check it.

== 1.19.1 Nested Collapsible elements ==
{{tracked|35257}}
In 1.19.1, using the builtin JQuery mw-collapsible and mw-collapsed classes works as expected, except if you have nested elements and "Expand" a collapsed element, it will also expand all nested elements. Ideally this could either be toggled via a setting or by default not expand all child collapsible elements.
:That seems to be [[bugzilla:35257]]. [[b:pt:User:Helder.wiki|Helder]] 18:31, 6 July 2012 (UTC)

== 19.2 - Collapsible Elements Load Open ==

I was previously using the now obsolete [[Extension:ToggleDisplay|ToggleDisplay]] extension which worked nicely but now after upgrading to 1.19.2 I have started trying to use the built in Collapsible elements feature. It seems fine but when the page loads, all toggle areas load as open and only close once the page is completely loaded. This creates a kind of unwanted stutter in the visual loading of the page.
Can this be fixed or is there a way to use Collapsible elements so it doesn't do this? The reason I mention the extension above is that it doesn't do this. The page loads with elements already closed and it looks great. Would love to have that effect again.

== Loading issue ==

Is it possible to keep all the content collapsed while the rest of the page loads? I have a problem that, on pages with many images and other content, the information that I have initially collapsed is visible until the entire page loads in the browser.
: It looks like this has been a proper nuisance for some time already. [[User:Cavila|Cavila]] <sup>MW 1.19.2, MySQL 5.1.63, Php 5.3.3-7, SMW 1.8</sup> 22:47, 17 January 2013 (UTC) {{tracked|34876}}

== Broken in Old Custom Skins ==

This functionality has been completely destroyed in pre 1.17 skins. It is impossible to implement any of the fixes suggested as the skins do not conform to the new framework, and the files used in the old framework no longer exist. Can anyone suggest a fix to re-implement this behaviour in pre 1.17 skins?

== Custom Toggle with arrow indicator and header ==
This code makes a nice Toggle element with an Arror indicator image. The image can be anything really but an arrow is the most logical choice.<br>
I have not tested backwards compatibility on this for MediaWiki versions < V1.21.<br>
Credit goes to [[User:Krinkle|Krinkle]] as this was adapted from his examples.
<br>
A demo can be seen here: [http://test.wikipedia.org/wiki/User:Shift9999#collapse-pre-one| Toggle with Arrow]
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible mw-collapsed">
<div class="mw-collapsible-toggle toccolours" style="float: none;">
<div class="mw-collapsible-toggle-row">
<div class="mw-collapsible-toggle-header"><big>'''Example Header'''<br>Example sub</big></div>
<div class="mw-collapsible-toggle-indicator">[[File:right-black-arrow.png|150px|link=]]</div>
</div>
</div>
<div class="mw-collapsible-content">
{{Lorem}}
</div>
</pre>

CSS:
<source lang="css">
/* Collapse Toggle container */
#collapse-pre-one .mw-collapsible-toggle{
display: table;
border-collapse: collapse;
width: 100%;
}

#collapse-pre-one .mw-collapsible-toggle-row{
display: table-row;
}

/* Collapse Header should be on the left */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-header{
display: table-cell;
vertical-align: middle;
padding: 5px;
}

/* Collapse indicator image should be inline. align wherever you would like */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator{
display: table-cell;
vertical-align: middle;
padding: 5px;
text-align: right;
}

/* Collapse indicator image size should be something sane*/
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
height: 20px !important;
width: 20px !important;
}

/* Collapse indicator image should rotate when toggled*/
#collapse-pre-one:not(.mw-collapsed) .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
/* Safari */
-webkit-transform: rotate(90deg);

/* Firefox */
-moz-transform: rotate(90deg);

/* IE */
-ms-transform: rotate(90deg);

/* Opera */
-o-transform: rotate(90deg);

/* Internet Explorer */
filter: progid:DXImageTransform.Microsoft.BasicImage(rotation=1);
}
</source>
</blockquote>
--[[User:Shift9999|Shift9999]] at 2:06AM PST - 07-17-2013

== on() causes problems for older jq versions ==

In the code for collpasible tables, on() is used to bind behavior to the <a> for the show/hide button.... This is a jq function introduced in 1.4.2, so if you're using an older jq version, instead use the (old) bind() method instead of on().

== Font color of collapsible button ==

{|class="mw-collapsible" style="float:right;background:#00f;color:#fff"
!Header
|-
|Collapsed content
|}
Previously the font color of collapsible button was inheritable but now it doesn't. The problem is if someone changes the background color of talbe/div to blue, the [expand/collapse] button text is almost invisible even if the user has set color:#fff. -- [[User:Sameboat|Sameboat]] ([[User talk:Sameboat|talk]]) 02:44, 7 February 2014 (UTC)
: Is there any news about this issue? --[[User:Rotpunkt|Rotpunkt]] ([[User talk:Rotpunkt|talk]]) 10:09, 23 May 2016 (UTC)

== Wasn't this feature removed from the latest update? It is not in 1.24.1 ==

I think this has been removed. How do I get it back for new updates? <small><span class="autosigned">— Preceding [[w:Signatures|unsigned]] comment added by [[User:68.119.83.109|68.119.83.109]] ([[User talk:68.119.83.109|talk]] • [[Special:Contributions/68.119.83.109|contribs]]) 21:45, Nov 5, 2015 (UTC)</span></small>

== Cannot make it work with Vector sidebar panels ==

I've tried to incorporate this on the sidebar panels under Vector to no avail. Applying the following...
<source lang="javascript">
( function ( mw, $ ) {
$( '#mw-panel > .portal' ).each( function ( i ) {
var id = $( this ).attr( 'id' );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle-' + id );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle' );
$( this ).find( 'div' ).attr( 'id', 'mw-customcollapsible-' + id ).addClass( 'mw-collapsible mw-collapsed' );
} );
}( mediaWiki, jQuery ) );
</source>
...seems to place all the nuances class & id wise just fine but there is no collapsing or toggling of the H3 element at all (can't even force everything to collapsed state by default). When I duplicate a sidebar portal in a sandbox with the exact same structure, everything works as expected.

Is there any chance the ''mw-collapsible'' (jQuery) scheme is limited to only work within the ''.mw-body'' content container while the sidebar is outside that in it's own ''mw-navigation'' container?

Maybe it's a dependency thing?

Any help would be appreciated. Thanks in advance. -- [[User:George Orwell III|George Orwell III]] ([[User talk:George Orwell III|talk]]) 04:56, 12 December 2015 (UTC)

== mw-customcollapsible ==

Why the mw-customcollapsible application is not documented? [[Special:Contributions/93.57.251.180|93.57.251.180]] 13:46, 30 April 2016 (UTC)
:Why don't you do it yourself? <wink, wink> --[[User:Tactica amiga|Tactica amiga]] ([[User talk:Tactica amiga|talk]]) 13:58, 30 April 2016 (UTC)
::There is a line about it on [[ResourceLoader/Modules#jquery.makeCollapsible]] and on https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/jQuery.plugin.makeCollapsible. [[User:He7d3r|Helder]] 02:20, 2 May 2016 (UTC)

== Expand, collapse all? ==
I want a remote button that only expands and a button that only collapses, any ideas? mw-customtoggle seems to only toggle between them, which doesn't work that good when a couple of tables are already expanded and I want to expand all of them.

<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Expand all]'''</div>
<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Collapse all]'''</div>

<div class="mw-customtoggle-1" style="background:#e0e8ff">Collapsed table</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Some text in here.</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Other text here.</div>

<div class="mw-customtoggle-2" style="background:#e0e8ff">Expanded table</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">Even more text here.</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">No more text please.</div>

Note that I think being able to click anywhere on the table to expand is important.

== How to fix a collapsed spoiler? ==

I use spoilers type:
<pre><div class="mw-collapsible mw-collapsed">
Spoiler name
<div class="mw-collapsible-content">
Text
</div></div>
</pre>
At the same time, when the page loads - each time they are turned off, and it shows.

How to make so that it was unnoticed? Maybe there are other options spoilers?

== One toggle ==

I would like to add, at the top of some pages, a toggle to hide some sentences of the page. So I have two questions.

# Is it possible to place the show/hide toggle at the top of the page?
# Can the toggle hide/show multiple texts?

[[User:Derugon|Derugon]] ([[User talk:Derugon|talk]]) 08:40, 30 April 2017 (UTC)

== Toggle text of collapse/expand for ''custom''toggle? ==

Hi,

I have to use customtoggle because the toggler is always outside the toggle content, and here I found no solution to alter the text of the ''custom''toggle. Is there any official way to go? --[[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 13:29, 9 August 2017 (UTC)

== Selected collapsible table rows ==

{| class="wikitable mw-collapsible"
|+ Caption
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

{| class="wikitable mw-collapsible"
|-
! Header row
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

Although it only shows it with <code>div</code> elements, the documentation makes it seem as if <code>mw-collapsible-content</code> could be used on ''any'' child of a <code>mw-collapsible</code> element, but this does not work for table rows. It should – bug report or feature request? — [[:en:User:Crissov|Christoph]] [[:en:User talk:Crissov|Päper]] 13:51, 16 November 2017 (UTC)

== Click on a TOC item which lies within a currently hidden area, nothing will happen ==

If a person clicks on a TOC item which lies within a currently hidden area, nothing will happen.

It should toggle open the area, and jump to the anchor.

Seen with version 1.19.

[[User:Jidanni|Jidanni]] ([[User talk:Jidanni|talk]]) 12:14, 8 February 2018 (UTC)

== not working collapse ==

I have this in a Template, in my old MW 1.25 working fine, after update to 1.30 not working. Ahy ideas?

<span class="_togglegroup _toggle_initshow _toggle _toggler toggle-visible" style="display:none;">[Anzeigen]</span><span class="_toggle_inithide _toggle _toggler toggle-hidden" style="display:none;">[Verstecken]</span>
<div class="_toggle_inithide _toggle toggle-hidden">
{{{1}}}</div></includeonly>

Manual talk:Collapsible elements

2018-03-29T11:01:33Z

213.61.254.68: /* not working collapse */ new section

== Expand/Collapse All? ==

Does this have any support for an "expand all" or "collapse all" button? Pretty desperate for the ability to use such myself.

== Doesn't work? ==

This didn't work correctly in my Mediawiki 1.12.0 install. Looking at the source code of the page it created, initially hidden content is indeed hidden, but there is no "Show" link to reveal the content. Do you have any ideas? --[[User:Gadlen|Gadlen]] 19:13, 5 June 2008 (UTC)

== I'm not seeing the "hide" or "show" links ==

I'm running 1.13.4. any thoughts, could it be firefox? --[[Special:Contributions/69.244.124.138|69.244.124.138]] 01:16, 17 March 2009 (UTC)

== still doesn't work any thoughts this what is is displayed: ==

Edited both common.js and common.css
This is the header cell, which is always shown
This cell is not shown by default.

(no hide or show links)

--[[Special:Contributions/69.244.124.138|69.244.124.138]] 04:42, 25 March 2009 (UTC)

:Is this code for 13.3 + ?
--[[User:Mappc|Mappc]] 00:00, 5 April 2009 (UTC)

::I'm still interested in getting some resolution....any thoughts
--[[User:Mappc|Mappc]] 22:54, 6 April 2009 (UTC)

== This does work for me (IE6 , Firefox 3 and MediaWiki 13.4) ==
I had to change the function below the rest stay as it is. --[[User:AndreasMueller|AndreasMueller]] 21:56, 26 May 2009 (UTC)
<pre>
function createCollapseButtons()
{
var tableIndex = 0;
var NavigationBoxes = new Object();
var Tables = getElementsByClassName(document, "table", "collapsible");

for ( var i = 0; i < Tables.length; i++ ) {
/* only add button and increment count if there is a header row to work with */
var HeaderRow = Tables[i].getElementsByTagName( "tr" )[0];
if (!HeaderRow) continue;
var Header = HeaderRow.getElementsByTagName( "th" )[0];
if (!Header) continue;

NavigationBoxes[ tableIndex ] = Tables[i];
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );

var Button = document.createElement( "span" );
var ButtonLink = document.createElement( "a" );
var ButtonText = document.createTextNode( collapseCaption );

Button.className = "collapseButton"; //Styles are declared in Common.css

ButtonLink.style.color = Header.style.color;
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );
ButtonLink.appendChild( ButtonText );

Button.appendChild( document.createTextNode( "[" ) );
Button.appendChild( ButtonLink );
Button.appendChild( document.createTextNode( "]" ) );

Header.insertBefore( Button, Header.childNodes[0] );
tableIndex++;
}

var Tables = getElementsByClassName(document, "table", "collapsed");
for ( var i = 0; i < Tables.length; i++ ) {
collapseTable( i );
}

var Tables = getElementsByClassName(document, "table", "autocollapse");
for ( var i = 0; i < Tables.length; i++ ) {
if ( i >= autoCollapse ) {
collapseTable( i );
}
}
}
</pre>

== Worked A-OK ==

No editing needed over here. Using MediaWiki 1.15.1 with no other custom JS.
[[Special:Contributions/74.65.88.219|74.65.88.219]] 01:55, 7 October 2009 (UTC)

: Worked for me too on 1.15.1. At first it was very frustrating, I couldn't get it to work, but all I needed to do was the Shift-Refresh thing in my browser. =D --[[User:J.nesta|J.nesta]] 18:36, 5 November 2009 (UTC)

== hide/show placement not working ==

I updgraded to 1.15.1. Now my hide/show buttons are always on the left even though I have the Common.css file with float right. See at http://sunshinereview.org/index.php/User:Ljarratt

== 1.16 functionality ==

Beta 3. This function works flawlessly for me.
:Funny, not doing a damn thing for me (as describe, prior to 1.7 in the main article)
:MediaWiki 1.16.2
:PHP 5.2.11 (apache2handler)
:MySQL 5.0.77
:--[[Special:Contributions/99.197.224.57|99.197.224.57]] 06:04, 26 March 2011 (UTC)

==1.15.3 Not Working - Using skin Cavendish==

can anyone help with making this functional?
http://emajenanything.com/mainwiki/wiki/index.php?title=Test THANKS

== What? ==

How come I don't have neither common.js nor common.css in my wiki? how do I make this effect? :( --[[Special:Contributions/201.255.119.39|201.255.119.39]] 07:22, 19 July 2010 (UTC)
: You can create them using your search box and searching for
MediaWiki:Common.css
MediaWiki:Common.js
: --Skew 03:14, 22 September 2010 (UTC)

== show/hide: jumping to top ==

A click on my show/hide button causes the page to jump to the top. Any ideas? [[User:Gohnarch|Gohnarch]] 20:30, 27 September 2010 (UTC)

: I have same problem on two different installs of 1.15 (Ubuntu and CentOS) - tried code from "This does work for me ..." above and that seems to be OK for now ... WBN [[Special:Contributions/82.41.58.191|82.41.58.191]] 23:49, 13 October 2010 (UTC)

:That's as a result of these two lines

ButtonLink.setAttribute( 'href', '#' );
addHandler( ButtonLink, 'click', new Function( 'evt', 'collapseTable(' + tableIndex + ' ); return killEvt( evt );' ) );

:If you look at the current mw [[MediaWiki:Common.js]], it reads

ButtonLink.setAttribute( 'href', "javascript:collapseTable(" + tableIndex + ");" );

:(see [[W:Fragment identifier]]). I will update the page to show this change if that is all right with everybody. --[[User:JCrue|JCrue]] 18:24, 30 November 2010 (UTC)

== Still not working ==

Hi, I'm trying to install this on 1.15, and the "hide/show" tags aren't appearing. I've edited the common.js and common.css, as above and as shown on the article page, purged webcaches, etc, etc, and still no go. Any ideas for how to troubleshoot this? - very frustrating!

== 1.17 example not working on diffs ==

Hi!

I noticed that the new examples doesn't works when the page is seen in a diff like [http://www.mediawiki.org/w/index.php?title=Manual:Collapsible_tables&diff=cur&oldid=367004#After_1.17 this]. I think it should work even in this case (not only when viewing the page directly). [[b:pt:User:Helder.wiki|Helder]] 16:03, 23 February 2011 (UTC)
: During development it worked fine in preview, diff and oldid view. Will look into it. [[User:Krinkle|Krinkle]] 11:00, 24 February 2011 (UTC)
:: It does work in the latest development version, as for example ran on TranslateWiki, [http://translatewiki.net/w/i.php?title=User%3AKrinkle%2FCollapsingTestpageMw&diff=2756282 here]. Hm.. [[User:Krinkle|Krinkle]] 11:32, 24 February 2011 (UTC)
::: Seems the cause isn't in the script after all. The problem is the FlaggedRevisions-extension which loads the page-contents afterwards via JavaScript causing any onload handlers to fail miserably since there isn't a page at that time (TOC-toggle, mw-collapsible, mw.util.$content) See also [[bugzilla: 26175]] and [[bugzilla: 27513]]. I can't fix this untill FlaggedRevs has some kind of hook or is fixed otherwise. Any javascript handlers will fail (potentially $.fn.placeholder and $.fn.checkboxShiftClick as well) [[User:Krinkle|Krinkle]]

== Cannot get Collapse to work in 1.17 ==

I have tried to different 1.17 installs and I cannot get collapse to work at all. I am following the examples exactly:

:<nowiki><div class="toccolours mw-collapsible" style="width:400px"></nowiki>
:<nowiki>This is text is collapsible. {{Lorem}}</nowiki>
:<nowiki></div></nowiki>

Just shows the text. There is no option to collapse. The other examples give the same results. The ability to collapse is completely missing, even though the directions say "After 1.17... Basically all you do is add the class "mw-collapsible" to an element." What am I missing?

* Site #1: http://wiki.cyanogenmod.com/wiki/User:Pconwell/sandbox2
* Site #2: http://w.gu1dry.com/User:Pconwell/Sandbox2

: I can't get this to work over at http://everquest.wikkii.net either. I also couldn't get the old style of collapsible tables using common.css and common.js to work either. I'm going nuts trying to figure out what I have done wrong. [[Special:Contributions/24.40.138.185|24.40.138.185]] 21:52, 24 June 2011 (UTC)

On [[ResourceLoader/Default_modules#jQuery.makeCollapsible]] it is said that this feature is currently available on trunk, since [[rev:78914]], but there is no mention of MW 1.'''17'''. So, I think this page is outdated.

Anyway, on [[meta:User_talk:Krinkle/1-17-allwikis#Wikis_using_jquery.makeCollapsible|this page]] it is explained how to install the plugin on MW 1.17 (as was made here on MediaWiki.org). [[b:pt:User:Helder.wiki|Helder]] 12:43, 28 June 2011 (UTC)

: Thank you for your concern. I had created MediaWiki:JQuery-makeCollapsible.js and MediaWiki:JQuery-makeCollapsible.css on my wiki and put the two lines in my Common.js before posting here. But it just doesn't seem to work. Neither does the old style collapsible tables. I'm at a loss here to understand why. [[Special:Contributions/24.40.138.185|24.40.138.185]] 07:29, 29 June 2011 (UTC)
::Notice that the current code of your MediaWiki:Common.js has syntax errors before the makeCollapsible plugin is loaded (copy and paste it on [http://jshint.com/ JSHint] to check the syntax). Specifically, this will not work: <syntaxhighlight lang="javascript">if ( {{PAGENAME}} == 'Main Page' )</syntaxhighlight>
::So, I think the plugin will work if you add [http://everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&curid=439&diff=1181&oldid=1029 these lines] again and fix the syntax errors above (or just remove everything from [http://everquest.wikkii.net/w/index.php?title=MediaWiki:Common.js&action=edit your MediaWiki:Common.js] except this:
<syntaxhighlight lang="javascript">/* FROM MEDIAWIKI.ORG COMMON.JS Load collapsible javascript */
mw.loader.load( 'http://www.everquest.wikkii.net/w/index.php?title=MediaWiki:JQuery-makeCollapsible.js&action=raw&ctype=text/javascript' );
</syntaxhighlight>
::) and clear your cache. [[b:pt:User:Helder.wiki|Helder]] 13:18, 29 June 2011 (UTC)

::: Helder, thank you a million times. That was the problem all right. Thanks. [[Special:Contributions/24.40.138.185|24.40.138.185]] 06:22, 30 June 2011 (UTC)

== Indication of collapsed/expandable status ==
: ''<small>Moved from [http://meta.wikimedia.org/w/index.php?title=User_talk:Krinkle/1-17-allwikis&oldid=2703017#Indication_of_collapsed.2Fexpandable_status Meta-Wiki]</small>''

Hi,

This might be the wrong place to ask, but we were wondering if their is an easy way to know which status of the class="mw-customtoggle-myDivision" is set in terms of being collapsed/expandable.

Using the standard solution indicates the status through the display of either [Collapsed] or [Expand], in our case we trigger the area which need to be collapsed with the display of an icon, and as soon the user switches from one status to the other one we wanted to indicated a change through a change in the icon displayed.
<pre>
<div class="mw-customtoggle-topicon" style="cursor:pointer">[[File:icon-set-10-arrow-down.png|14px|link=]]</div>
</pre>
So in case the class contains "mw-collapsible mw-collapsed" display one type of icon, and in case of the class just being "mw-collapsible" display another icon. --[[m:User:MWJames|MWJames]] 18:13, 6 July 2011 (UTC)
: Hi MWJames,
: If you can provide a link to where this happends on a live-wiki I may be able to give a more fine-tuned detail. I'll show you how I would do it though. I'm assuming your toggle-icon is inside {{tag|div|params= class="mw-collasible"}}:
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible">
<div class="mw-collapsible-toggle toccolours" style="width: 100%">
<span class="down">[[File:Arrow-down-dash-2.0.svg|50px|center|link=]]</span>
<span class="up">[[File:Arrow-up-dash-2.0.svg|50px|center|link=]]</span>
</div>
<div class="mw-collapsible-content">
{{User:Krinkle/Lorem}}
</div>
</div>
</pre>

CSS:
<source lang="css">
#collapse-pre-one .mw-collapsible-toggle .up,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .down {
display: none;
}
#collapse-pre-one .mw-collapsible-toggle .down,
#collapse-pre-one.mw-collapsed .mw-collapsible-toggle .up {
display: block;
}
</source>
</blockquote>
: A demo of this can be found at [[testwiki:User:Krinkle/CollapsingTestpageMw#collapse-pre-one]]
: Note that the <code>collapse-pre-one</code> is not required, it's just to make sure it won't apply to other collapsible constructions on the same page. Use whatever identifier you like [[User:Krinkle|Krinkle]] 21:14, 6 July 2011 (UTC)

== makeCollapsible "in core" ==

Does "in core as of MediaWiki 1.18 or higher" mean that it will be enabled by default on all wikis, loaded and activated on every page? If so, will there be any way to disable it? --[[User:Yair rand|Yair rand]] 08:54, 14 July 2011 (UTC)
: There is nothing to disable as all the scripts mentioned on this page are only triggered if there are elements on the page marked as "mw-collapsible". If your wiki doesn't want or have collapsible elements, this script will not be triggered and nothing will change when upgrading to 1.18. [[User:Krinkle|Krinkle]] 04:21, 4 August 2011 (UTC)
::Really? It won't even load the scripts or take up time running any JS if there aren't any mw-collapsible elements in the wikitext? --[[User:Yair rand|Yair rand]] 05:14, 4 August 2011 (UTC)

== Use new 1.18 collapsible in 1.17 ==

You can use the new 1.18 collapsible code in a 1.17 install. Just paste the contents of jquery-makeCollapsible.js into your MediaWiki:Common.js

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.js?view=co Download head version from MediaWiki]

Then at the bottom of MediaWiki:Common.js, add:

mw.messages.set({"collapsible-collapse":"Collapse","collapsible-expand":"Expand"});
$(document).ready(function(){
$('.mw-collapsible').makeCollapsible();
});

And add the contents of jquery.makeCollapsible.css into your MediaWiki:Common.css

[http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/resources/jquery/jquery.makeCollapsible.css?view=co Download head version from MediaWiki]

If there is a tidier way of doing this, please let me know. --[[User:Thenickdude|Thenickdude]] 11:33, 13 September 2011 (UTC)

== Autocollapse ==

Has a version of autocollapse been implemented in core in 1.18? --<small style="background:#f00">'''★ [[User:Airon90|<span style="color:#000">→ A</span>]][[Special:Contributions/Airon90|<span style="color:#f00;background:#000">ir</span>]][[User talk:Airon90|<span style="color:#000">on Ĉ</span>]]'''</small> 14:09, 7 October 2011 (UTC)

== Common.js script (Before 1.18) don't works ==

Hey there!

I have some Wikis running on an Debian Linux 6.0 (Squeeze) Webserver.<br>
MediaWiki 1.17.0 (Version 95135)<br>
PHP 5.3.3-7+squeeze3 (apache2handler)<br>
MySQL 5.1.49-3<br>

and i have the Problem, that this Collapse Hide & Show didnt works. I try it on two local Servers installed in Virtual Box and i have there the same problem. Could it be, that Debian Squeeze is the problem? Ive tryd all things, that i found here. But without a happy ending... [[User:Yukii|Yukii]] 12:27, 10 October 2011 (UTC)

== mw-collapsible will not work (1.18) ==

I've copied and pasted the examples and none of them work no matter what I do - upgraded my wiki, completely reinstalled the wiki, no dice. [[User:Leangle|Leangle]] 8:54 PM, Dec 29 2011

== Customizing Collapse/Expand location ==

Using 1.18, how would I customize the mw-collapsible mw-collapsed CSS so that the 'Expand' or 'Collapse' buttons appear on the left?

I'm thinking of something like what the mobile site does for certain sections - rather than having the 'expand' button float out of site off to the right, i'd prefer it to be on the left. It doesn't necessarily need to use a button, but that would be interesting as well.

[[Special:Contributions/66.3.56.92|66.3.56.92]] 23:21, 1 March 2012 (UTC)

Update:

Solved it, more or less

/* leave toggle on the right for tables */
.tablecollapse span.mw-collapsible-toggle{
float:right;
}

/* put it on the left for everything else */
.collapse span.mw-collapsible-toggle {
float: left;
}

By setting those classes, I can make sure that for tables, the toggle still appears where it should, and for other areas, the toggle appears floating left.

not sure how to swap out images, but at this point, thats no big deal. Hope this helps someone.

Another way:<br>
For those of you who don't like having the toggle right beside text, here's how to make text appear below it:
.mw-collapsible-toggle {
display:inline-block;
float:none;
}

[[User:Bluekuma|Bluekuma]] ([[User talk:Bluekuma|talk]]) 17:43, 22 May 2015 (UTC)

== Only Works for Anons ==

When i log into my wiki the expand/collapse links disappear and all content within them defaults to expanded. Any idea on how to fix this? I'm thinking it's not loading the java after login but don't know what to change to fix it.

Thanks!

== Extensions that disrupts collapsible elements. ==

I notice that with mediwiki 1.17 I didn't have any collapsible elements, even doing all the things to be done. I upgrade to mediawiki 1.18, and didn't work.

So I notice that, when '''I disable''' the [http://www.mediawiki.org/wiki/Extension:Page_Object_Model Page Object Model] Extension It worked.

Check it.

== 1.19.1 Nested Collapsible elements ==
{{tracked|35257}}
In 1.19.1, using the builtin JQuery mw-collapsible and mw-collapsed classes works as expected, except if you have nested elements and "Expand" a collapsed element, it will also expand all nested elements. Ideally this could either be toggled via a setting or by default not expand all child collapsible elements.
:That seems to be [[bugzilla:35257]]. [[b:pt:User:Helder.wiki|Helder]] 18:31, 6 July 2012 (UTC)

== 19.2 - Collapsible Elements Load Open ==

I was previously using the now obsolete [[Extension:ToggleDisplay|ToggleDisplay]] extension which worked nicely but now after upgrading to 1.19.2 I have started trying to use the built in Collapsible elements feature. It seems fine but when the page loads, all toggle areas load as open and only close once the page is completely loaded. This creates a kind of unwanted stutter in the visual loading of the page.
Can this be fixed or is there a way to use Collapsible elements so it doesn't do this? The reason I mention the extension above is that it doesn't do this. The page loads with elements already closed and it looks great. Would love to have that effect again.

== Loading issue ==

Is it possible to keep all the content collapsed while the rest of the page loads? I have a problem that, on pages with many images and other content, the information that I have initially collapsed is visible until the entire page loads in the browser.
: It looks like this has been a proper nuisance for some time already. [[User:Cavila|Cavila]] <sup>MW 1.19.2, MySQL 5.1.63, Php 5.3.3-7, SMW 1.8</sup> 22:47, 17 January 2013 (UTC) {{tracked|34876}}

== Broken in Old Custom Skins ==

This functionality has been completely destroyed in pre 1.17 skins. It is impossible to implement any of the fixes suggested as the skins do not conform to the new framework, and the files used in the old framework no longer exist. Can anyone suggest a fix to re-implement this behaviour in pre 1.17 skins?

== Custom Toggle with arrow indicator and header ==
This code makes a nice Toggle element with an Arror indicator image. The image can be anything really but an arrow is the most logical choice.<br>
I have not tested backwards compatibility on this for MediaWiki versions < V1.21.<br>
Credit goes to [[User:Krinkle|Krinkle]] as this was adapted from his examples.
<br>
A demo can be seen here: [http://test.wikipedia.org/wiki/User:Shift9999#collapse-pre-one| Toggle with Arrow]
<blockquote>
Wikitext:
<pre>
<div id="collapse-pre-one" class="mw-collapsible mw-collapsed">
<div class="mw-collapsible-toggle toccolours" style="float: none;">
<div class="mw-collapsible-toggle-row">
<div class="mw-collapsible-toggle-header"><big>'''Example Header'''<br>Example sub</big></div>
<div class="mw-collapsible-toggle-indicator">[[File:right-black-arrow.png|150px|link=]]</div>
</div>
</div>
<div class="mw-collapsible-content">
{{Lorem}}
</div>
</pre>

CSS:
<source lang="css">
/* Collapse Toggle container */
#collapse-pre-one .mw-collapsible-toggle{
display: table;
border-collapse: collapse;
width: 100%;
}

#collapse-pre-one .mw-collapsible-toggle-row{
display: table-row;
}

/* Collapse Header should be on the left */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-header{
display: table-cell;
vertical-align: middle;
padding: 5px;
}

/* Collapse indicator image should be inline. align wherever you would like */
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator{
display: table-cell;
vertical-align: middle;
padding: 5px;
text-align: right;
}

/* Collapse indicator image size should be something sane*/
#collapse-pre-one .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
height: 20px !important;
width: 20px !important;
}

/* Collapse indicator image should rotate when toggled*/
#collapse-pre-one:not(.mw-collapsed) .mw-collapsible-toggle .mw-collapsible-toggle-indicator img{
/* Safari */
-webkit-transform: rotate(90deg);

/* Firefox */
-moz-transform: rotate(90deg);

/* IE */
-ms-transform: rotate(90deg);

/* Opera */
-o-transform: rotate(90deg);

/* Internet Explorer */
filter: progid:DXImageTransform.Microsoft.BasicImage(rotation=1);
}
</source>
</blockquote>
--[[User:Shift9999|Shift9999]] at 2:06AM PST - 07-17-2013

== on() causes problems for older jq versions ==

In the code for collpasible tables, on() is used to bind behavior to the <a> for the show/hide button.... This is a jq function introduced in 1.4.2, so if you're using an older jq version, instead use the (old) bind() method instead of on().

== Font color of collapsible button ==

{|class="mw-collapsible" style="float:right;background:#00f;color:#fff"
!Header
|-
|Collapsed content
|}
Previously the font color of collapsible button was inheritable but now it doesn't. The problem is if someone changes the background color of talbe/div to blue, the [expand/collapse] button text is almost invisible even if the user has set color:#fff. -- [[User:Sameboat|Sameboat]] ([[User talk:Sameboat|talk]]) 02:44, 7 February 2014 (UTC)
: Is there any news about this issue? --[[User:Rotpunkt|Rotpunkt]] ([[User talk:Rotpunkt|talk]]) 10:09, 23 May 2016 (UTC)

== Wasn't this feature removed from the latest update? It is not in 1.24.1 ==

I think this has been removed. How do I get it back for new updates? <small><span class="autosigned">— Preceding [[w:Signatures|unsigned]] comment added by [[User:68.119.83.109|68.119.83.109]] ([[User talk:68.119.83.109|talk]] • [[Special:Contributions/68.119.83.109|contribs]]) 21:45, Nov 5, 2015 (UTC)</span></small>

== Cannot make it work with Vector sidebar panels ==

I've tried to incorporate this on the sidebar panels under Vector to no avail. Applying the following...
<source lang="javascript">
( function ( mw, $ ) {
$( '#mw-panel > .portal' ).each( function ( i ) {
var id = $( this ).attr( 'id' );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle-' + id );
$( this ).find( 'h3' ).addClass( 'mw-customtoggle' );
$( this ).find( 'div' ).attr( 'id', 'mw-customcollapsible-' + id ).addClass( 'mw-collapsible mw-collapsed' );
} );
}( mediaWiki, jQuery ) );
</source>
...seems to place all the nuances class & id wise just fine but there is no collapsing or toggling of the H3 element at all (can't even force everything to collapsed state by default). When I duplicate a sidebar portal in a sandbox with the exact same structure, everything works as expected.

Is there any chance the ''mw-collapsible'' (jQuery) scheme is limited to only work within the ''.mw-body'' content container while the sidebar is outside that in it's own ''mw-navigation'' container?

Maybe it's a dependency thing?

Any help would be appreciated. Thanks in advance. -- [[User:George Orwell III|George Orwell III]] ([[User talk:George Orwell III|talk]]) 04:56, 12 December 2015 (UTC)

== mw-customcollapsible ==

Why the mw-customcollapsible application is not documented? [[Special:Contributions/93.57.251.180|93.57.251.180]] 13:46, 30 April 2016 (UTC)
:Why don't you do it yourself? <wink, wink> --[[User:Tactica amiga|Tactica amiga]] ([[User talk:Tactica amiga|talk]]) 13:58, 30 April 2016 (UTC)
::There is a line about it on [[ResourceLoader/Modules#jquery.makeCollapsible]] and on https://doc.wikimedia.org/mediawiki-core/master/js/#!/api/jQuery.plugin.makeCollapsible. [[User:He7d3r|Helder]] 02:20, 2 May 2016 (UTC)

== Expand, collapse all? ==
I want a remote button that only expands and a button that only collapses, any ideas? mw-customtoggle seems to only toggle between them, which doesn't work that good when a couple of tables are already expanded and I want to expand all of them.

<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Expand all]'''</div>
<div class="mw-customtoggle-1 mw-customtoggle-2">'''[Collapse all]'''</div>

<div class="mw-customtoggle-1" style="background:#e0e8ff">Collapsed table</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Some text in here.</div>
<div class="mw-collapsible mw-collapsed toccolours mw-collapsible-content" id="mw-customcollapsible-1">Other text here.</div>

<div class="mw-customtoggle-2" style="background:#e0e8ff">Expanded table</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">Even more text here.</div>
<div class="mw-collapsible toccolours mw-collapsible-content" id="mw-customcollapsible-2">No more text please.</div>

Note that I think being able to click anywhere on the table to expand is important.

== How to fix a collapsed spoiler? ==

I use spoilers type:
<pre><div class="mw-collapsible mw-collapsed">
Spoiler name
<div class="mw-collapsible-content">
Text
</div></div>
</pre>
At the same time, when the page loads - each time they are turned off, and it shows.

How to make so that it was unnoticed? Maybe there are other options spoilers?

== One toggle ==

I would like to add, at the top of some pages, a toggle to hide some sentences of the page. So I have two questions.

# Is it possible to place the show/hide toggle at the top of the page?
# Can the toggle hide/show multiple texts?

[[User:Derugon|Derugon]] ([[User talk:Derugon|talk]]) 08:40, 30 April 2017 (UTC)

== Toggle text of collapse/expand for ''custom''toggle? ==

Hi,

I have to use customtoggle because the toggler is always outside the toggle content, and here I found no solution to alter the text of the ''custom''toggle. Is there any official way to go? --[[User:Andreas_Plank|Andreas P.]] [[File:Icon_External_Link_E-Mail.png|link=User_talk:Andreas_Plank]] 13:29, 9 August 2017 (UTC)

== Selected collapsible table rows ==

{| class="wikitable mw-collapsible"
|+ Caption
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

{| class="wikitable mw-collapsible"
|-
! Header row
|-
| This row should always be visible
|- class="mw-collapsible-content"
| This row has optional content and can be hidden
|}

Although it only shows it with <code>div</code> elements, the documentation makes it seem as if <code>mw-collapsible-content</code> could be used on ''any'' child of a <code>mw-collapsible</code> element, but this does not work for table rows. It should – bug report or feature request? — [[:en:User:Crissov|Christoph]] [[:en:User talk:Crissov|Päper]] 13:51, 16 November 2017 (UTC)

== Click on a TOC item which lies within a currently hidden area, nothing will happen ==

If a person clicks on a TOC item which lies within a currently hidden area, nothing will happen.

It should toggle open the area, and jump to the anchor.

Seen with version 1.19.

[[User:Jidanni|Jidanni]] ([[User talk:Jidanni|talk]]) 12:14, 8 February 2018 (UTC)

== not working collapse ==

I have this in a Template, in my old MW 1.25 working fine, after update to 1.30 not working. Ahy ideas?

<includeonly><span class="_togglegroup _toggle_initshow _toggle _toggler toggle-visible" style="display:none;">[Anzeigen]</span><span class="_toggle_inithide _toggle _toggler toggle-hidden" style="display:none;">[Verstecken]</span>
<div class="_toggle_inithide _toggle toggle-hidden">
{{{1}}}</div></includeonly><noinclude>

Topic:T7yqmvlxtyvl210h

2016-07-18T12:58:54Z

213.61.254.68 (talk) commented on "wrong repository with composer" (Hello, the https://packagist.org/packages/mediawiki/vector-skin show a wrong repository. The repository: https://git.wikimedia.org/git/me...)

Skin talk:Vector

2016-07-18T12:58:54Z

213.61.254.68: /* wrong repository with composer */ New section

{{flow imported revision}}

== Undefined method getIndicators()? ==
{{Flow summary|Filed as [[phab:T76132]]}}

Fatal error: Call to undefined method VectorTemplate::getIndicators() in /.../w/skins/Vector/VectorTemplate.php on line 105

The appropriate line: <?php echo $this->getIndicators(); ?>

I can't find this function anywhere else outside of skins, so I have no idea what the function does. Commenting out the echo gives me this:
<span class="mw-default-size">[[File:GetIndicatorsProblem.png|1277x1277px]]</span>

So I'm guessing this line is needed.

Anyone have any idea what is going on? I cloned via git but the directory should be correct. Is there a specific tag I'm supposed to have checked out or is master OK? [[User:Iggyvolz]], but you'll probably find me on [http://c.wikia.com/wiki/User:Iggyvolz Wikia] 15:34, 27 November 2014 (UTC)
:I just removed the line from the file and the page rendered properly. The site was completely broken before that. There's a broken site with the same error listed on Google. This very much seems like an issue of something that's missing in the installation of any normal, minimal OS. I'm not sure how nobody testing 1.24 managed to encounter this bug before they released it, because it's obvious that it's not that uncommon. [[Special:Contributions/24.53.253.165|24.53.253.165]] 18:08, 27 November 2014 (UTC)
::[[phab:T76132]] ("Vector breaks MediaWiki 1.24") has further discussion. Hope that helps. [[User:Quiddity (WMF)|Quiddity (WMF)]] ([[User talk:Quiddity (WMF)|talk]]) 02:26, 28 November 2014 (UTC)
:::Yes, for the moments it appears to solve the problem for the moment.
:::Edit(2014-12-15):
:::In a new installation this did not help. See [https://phabricator.wikimedia.org/T78530?workflow=create here]. A tarball download might help to circumvent the issue for the time being, but this is something I would like to avoid. [[User:Temptuousinsolence|Temptuousinsolence]] ([[User talk:Temptuousinsolence|talk]]) 10:16, 4 December 2014 (UTC)

== MW 1.20 - Move Page/Discussion tabs to left-alignment in Vector skin ==

Hi all,
We have the Vector skin installed with MW 1.20, and the Page/Discussion tabs are in the middle of the page. We'd like to have them left-aligned, like in the current Vector skin on this site. Does anyone know the CSS to add to Mediawiki:Vector.css that would move these tabs to the left?

As it is now, smaller screens cause the Page/Discussion tabs to be covered by the Read/Edit tabs which is causing some problems.

Thanks all!
-Colin [[User:Ctorretta|Ctorretta]] ([[User talk:Ctorretta|talk]]) 20:37, 2 March 2015 (UTC)
:Figured out issue, was caused by custom Vector CSS:
:#left-navigation { margin-left: 10.5em; } [[User:Ctorretta|Ctorretta]] ([[User talk:Ctorretta|talk]]) 22:05, 18 May 2015 (UTC)

== Collapsible Sidebar navigation ==

I am migrating my wiki to a new version. (1.19.1 to 1.24.1) After many attempts to get the Vector extension installed I read that it's been discontinued for newer versions and integrated into the core of the Vector skin.

Unfortunately it appears that the syntax to get a collapsible sidebar navigation has changed.

Modifications to MediaWiki:Sidebar don't have the affect they did before and I no longer find an option for "Enable collapsing of items in the sidebar in Vector skin".

Has this feature been removed or modified? [[User:TDeeming|TDeeming]] ([[User talk:TDeeming|talk]]) 14:28, 26 March 2015 (UTC)
:Yes, this was removed from the Vector skin. There is however the [[Extension:CollapsibleVector|CollapsibleVector]] extension providing this functionality. I will add an info about this to this skin's page. Cheers [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 15:08, 26 March 2015 (UTC)
::Thanks for the tip. I added the CollapsibleVector Extension and now I have a collapsible side bar...
::Unfortunately, my changes to "MediaWiki:Sidebar" do not have any affect on the contents of the side bar. They stay the same, no matter how much I change them. Is there someplace where this needs to be enabled?
::;Update: I just found the problem. In my installation I had '''$wgMainCacheType=CACHE_MEMCACHED;''' If I change to '''CACHE_NONE'''... the changes to "MediaWiki:Sidebar" start working.
:::* This change also fixed the problem I was having to use WikEd as a Gadget.
:::* I'm still trying to figure out why the Access Log returns a blank page. [[User:TDeeming|TDeeming]] ([[User talk:TDeeming|talk]]) 07:33, 27 March 2015 (UTC)
:::Great that you tracked your issue. However it seems to me what you also set [[Manual:$wgEnableSidebarCache|$wgEnableSidebarCache]] to "true". [[User:Kghbln|[[kgh]]]] ([[User talk:Kghbln|talk]]) 16:09, 27 March 2015 (UTC)

== EditWarning ==

The EditWarning (Alert when leaving an edit page without saving) isn't working anymore in version 1.25.1.
In the DefaultSettings.php its activated (useeditwarning).
Does anybody have the same issue, have any idea why it isn't working anymore (1.24 works fine). [[User:Tickihgk|Tickihgk]] ([[User talk:Tickihgk|talk]]) 12:32, 15 June 2015 (UTC)
:'''This is a common problem for all skin.''' [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 22:52, 15 June 2015 (UTC)
::[[phab:T102564]]. [[User:StasR|StasR]] ([[User talk:StasR|talk]]) 10:25, 16 June 2015 (UTC)

== Trailing space when selecting page title ==

Following [https://git.wikimedia.org/commitdiff/mediawiki%2Fskins%2FVector/e0289b7d0ce07de8c6cdc8676e3870493cfbbb2d this change] (look for "h1" in VectorTemplate.php), there is a trailing space in the clipboard result, when I select the page title by dragging the mouse (selection by double-clicking is not affected) then Ctrl+C it. It occurs at least in Firefox. This appears to be ''very'' frustrating, and it's a straightforward one to fix… Many thanks in advance. [[User:Od1n|Od1n]] ([[User talk:Od1n|talk]]) 19:23, 15 June 2015 (UTC)
:[[phab:T102861]] [[User:Matma Rex|Matma Rex]] ([[User talk:Matma Rex|talk]]) 21:43, 17 June 2015 (UTC)

== User customization for background & text color and font ==

Hello, I am trying to find an extension or ways for user to change text and background of their choice instead of having black and white skin.

Is there any extension or alt. ways to do so? [[Special:Contributions/158.57.150.68|158.57.150.68]] 18:30, 1 July 2015 (UTC)
:There is [[Extension:Theme]], but it might be too limited for your use case. [[User:Matma Rex|Matma Rex]] ([[User talk:Matma Rex|talk]]) 18:36, 1 July 2015 (UTC)
::Thank you, looks like you are right....
::"Future versions of this extension will also add fields to Special:Preferences to allow changing the theme on a per-account basis."
::I hope future version comes out soon [[Special:Contributions/158.57.150.68|158.57.150.68]] 18:45, 1 July 2015 (UTC)

== SkinVector not found ==
{{Archive top|status=resolved}}

Hello,

I've just installed MW
1.24.2 and tried to display the main page. Unfortunately there is a
error saying: \mediawiki\skins\Vector/SkinVector.php): failed to open
stream: No such file or directory in '''...\mediawiki\includes\AutoLoader.php''' on line '''1282'''

I checked in the
LocalSettings.php if there is a problem with the path, but the default
skin is set for "vector" and require_once "$IP/skins/Vector/Vector.php";
seems to be alright as well. The path of SkinVector.php seems to be
correct, I couldnt find any typos or similar. I tried to download the
skin separately and paste it into the skins directory, but then it says
its only compatible with MW1.25+.

Any hints what might be the problem? I'm actually still thinking of a path problem, but I just dont know where to look after it. [[User:Mafi9|Mafi9]] ([[User talk:Mafi9|talk]]) 12:52, 27 July 2015 (UTC)
{{Archive bottom}}

== Tag a stable release? ==

Composer complains that there's no stable release [https://packagist.org/packages/mediawiki/vector-skin for this skin]<nowiki>. It is of course actually stable, but without a tag > 1.0 it's a tiny bit longer to install. Am I missing something? Or could a stable tag be added? Thanks! :) ~</nowiki> [[User:Samwilson|Sam]] [[User_talk:Samwilson|Wilson]] 00:37, 27 August 2015 (UTC)
:A 1.0 tag probably wouldn't be useful unless new tags are consistently created, which I doubt they will be...you're probably better off sticking to release branches (dev-REL1_25), they're actually stable, regardless of what packagist thinks. [[User:Legoktm|Legoktm]] ([[User talk:Legoktm|talk]]) 02:07, 27 August 2015 (UTC)
:Yes, that makes sense. It just means every update has to be manually specified in composer.json, but that's ok. [[User:Samwilson|Sam]] [[User_talk:Samwilson|Wilson]] 02:09, 28 August 2015 (UTC)

== How to remove star icon? ==

$wgVectorUseIconWatch = false; It does not seem to work (in localsettings.php) MW1.25.1. Any suggestions? [[User:Abhidevananda|Abhidevananda]] ([[User talk:Abhidevananda|talk]]) 02:33, 20 May 2016 (UTC)

== No Adsense in sidebar ==

Hello.

I have some issue with Vector Skin.

On ma page should be Adsense in sidebar:

http://westeros.com.pl/index.php?title=Strona_g%C5%82%C3%B3wna

Here is the same page but with Bluemoon skin:

http://wiki.westeros.pl/index.php?title=Strona_g%C5%82%C3%B3wna

I used that solution:

https://www.guyrutenberg.com/2014/10/13/displaying-google-adsense-in-mediawiki/

Could You help me? [[Special:Contributions/193.23.61.254|193.23.61.254]] ([[User talk:193.23.61.254|talk]]) 13:56, 22 June 2016 (UTC)

== wrong repository with composer ==

Hello,

the https://packagist.org/packages/mediawiki/vector-skin show a wrong repository.
The repository: https://git.wikimedia.org/git/mediawiki/skins/Vector.git are NOT exist.

And when I use "composer update" they can not find the repository. [[Special:Contributions/213.61.254.68|213.61.254.68]] ([[User talk:213.61.254.68|talk]]) 12:58, 18 July 2016 (UTC)

Talk:VisualEditor/Design/Table editor

2015-08-27T06:31:19Z

213.61.254.68: /* Keyboard interaction to change the focus in the table */

== Hovering on mobile? ==

I like this design, and I think it covers all the basics: change the number of rows and columns, set the top row to gray (or not), etc.

One possible problem: How do you "hover" on a mobile device? Is table editing intended to be impossible for mobile users? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 23:01, 10 July 2014 (UTC)

: {{ping|Whatamidoing (WMF)}} For touch devices, we're expecting to only show the handles if you select in the area (''i.e.'' if you drop a cursor there), which is slightly less quick but works well enough. Does this make sense to you? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 02:43, 11 July 2014 (UTC)

:: I think the hovering is good for advanced editors. But for beginners they will not see that there is an affordance to add or delete tables. I suggest that there be icons for this (similar to the Confluence wiki, I've seen many beginners able to use tables with their icons), and that they be turned on by default. Advanced users can then turn them off. As noted above, please look into how responsive your design is on pads and telephones (although I am old-fashioned and use a laptop, still). --[[User:WiseWoman|WiseWoman]] ([[User talk:WiseWoman|talk]]) 06:17, 11 July 2014 (UTC)

::: {{ping|WiseWoman}} Maybe the design sketches don't make it clear enough – the idea is that on either selection or hover tools would be provided. I'm not sure about whether there's enough space to try to show lots of icons (rather than just a button) given how wikis generally lay out their tables. Also, all of VisualEditor is designed to work on both mobile and desktop devices, worry not. :-) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:35, 11 July 2014 (UTC)

:: I agree. Provide something to click (or touch) to select a row or a column. I prefer option 8 as well - menu drops down when the row or column is selected. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:23, 11 July 2014 (UTC)

::: {{ping|Filceolaire}} Yes, the idea is to how the handles on hover or selection; on mobiles, it will have to be selection-only. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:35, 11 July 2014 (UTC)

== Menu for changing the whole table ==
There should be a button to click to bring up a menu of options that apply to the whole table:
* Make table sortable/unsortable
* select format (lines colours etc.) from a shortlist of preset named options. Each wiki to define what options they want to offer as their style guidelines. Shell may vary the details of these - if you have the 'subdued' shell then colours are toned down, made more pastel; if you have the 'high contrast' shell then everything is tweaked to make it more legible to people with poor eyesight. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 15:06, 11 July 2014 (UTC)

: {{ping|Filceolaire}} That's what the grab handle in the top left would do – click to get a menu for the whole table, drag to move the table elsewhere. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:30, 11 July 2014 (UTC)
: I've now modified the description to make it obvious – thanks for the catch. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:44, 11 July 2014 (UTC)

== merge cells / split cells ==

I notice the desired functionality includes merging and splitting cells. Is this really needed? I know this was used in the good old days as a presentation tool for web pages but I'm pretty sure we don't want to do that. Is this used much on wikipedia? The immediate effect of doing this is that it prevents the table from being sorted and makes it impossible to add or delete rows and columns. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:32, 11 July 2014 (UTC)
:It is used unfortunately often, although on en.wp this is usually handled through complex templates that construct the table for you. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:17, 11 July 2014 (UTC)

== Wikidata integration ==

Wikidata integration is a thing which tables will need to have at some stage in the future. This can come in two ways:
# Import data from multiple wikidata items. In this type of table each row in the table corresponds to one item in wikidata and each column corresponds to a property that may be used in a statement about that item or the qualifier to a property.
# Import data from one wikidata item. For example a sports league table. Each league season will have an item. In that item there will be statements for each team giving all their stats so each row is the object of a "participant" property and each column is a qualifier to the wikidata statements about those participants.

Maybe number 2. should be a bunch of templates? [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:43, 11 July 2014 (UTC)

: {{ping|Filceolaire}} Neither of these issues are in-scope for table editing; those are both kinds of transclusion, and per the Wikidata team we're not rushing to implement them yet. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:36, 11 July 2014 (UTC)
::OK then. Just so long as the software doesn't prevent this being added later. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 19:20, 22 July 2014 (UTC)

::: {{ping|Filceolaire}} Indeed! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:46, 22 July 2014 (UTC)

== Do we want people to set column widths? ==

It is important that wikipedia pages are readable on a wide variety of screen sizes from cheap phones to projections. Sometimes people will want the table to autoadjust to the screen size. This can mean you have really narrow columns - in those cases people will want to side scroll instead. I'm not sure what the solution is but I'm a little wary of having column widths dictated by editors rather than readers.

Row heights should IMHO always autoadjust and should never be preset else you can lose info off the bottom of the cell without even knowing it. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:54, 11 July 2014 (UTC)

:I sometimes want to declare that two-column tables must be evenly split (column width = 50%). Defining an exact number of pixels is not so good in most cases. I've seen a few that use small "columns" basically for color-coding. That might be a reasonable use of pixel-based definitions. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:20, 11 July 2014 (UTC)

:: {{ping|Filceolaire|Whatamidoing (WMF)}} However, maybe we don't want to encourage that? I'm not sure. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:59, 11 July 2014 (UTC)

:::Don't want to encourage pixel-based column sizes, or don't want to encourage any column sizes at all? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 16:59, 14 July 2014 (UTC)

:::: {{ping|Whatamidoing (WMF)}} The latter; sorry for my inclarity. The number of times people want to do certain things may be high, but it's almost always against the intent of the system (in this case, HTML). [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:24, 14 July 2014 (UTC)
:::::What does "encourage" mean in this context? Making it impossible to fix (=at the very least, to remove) a preëxisting column-size problem might be less than desirable. If you take away the ability to set them entirely, then I'll just do it in wikitext—which is fine for me, but not so great for other users. However, I would not want to make it a prominent feature, because usually it shouldn't be done. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 20:07, 14 July 2014 (UTC)

== What is the initial size of 4x4 based on? ==

Did you do some kind of research on table sizes in Wikipedia to get to these figures? If you want a quick and simple solution, it would be ideal if the initial size fits in at least some cases. [[User:Dcutter|Dcutter]] ([[User talk:Dcutter|talk]]) 20:05, 14 July 2014 (UTC)

: {{ping|Dcutter}} Yes; I went through Special:Random on a few wikis hunting for use of tables, and found that four columns seemed to be about the normal (for the relatively rare articles that actually use tables). From a quick spate of Randoms just now, see [[W:Donnie Wahlberg#Film]], [[W:de:Bahnhof Coesfeld (Westf)#Bedienung]] and [[W:es:Chimillas#.C3.9Altimos alcaldes de Chimillas]] for examples. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 20:41, 14 July 2014 (UTC)

== Variation 8 (all actions in menu) ==

This looks really good! Regarding point 8 (variation: all actions shown in menu), I prefer this and think it's generally a good idea if all actions are also available through menus somewhere, not only icons. In my experience, I many users grew up with traditional "menu-driven" software and would not immediately realise that the + icon means "insert row/column" if it isn't spelled out somewhere. [[User:Stephan Matthiesen|Stephan Matthiesen]] ([[User talk:Stephan Matthiesen|talk]]) 09:09, 22 July 2014 (UTC)
: I do agree, I think Variation 8 is more user friendly because it is "classic". I think it is the best solution. [[User:NemesisIII|NemesisIII]] ([[User talk:NemesisIII|talk]]) 22:02, 26 July 2014 (UTC).
==Recommendation from fr.wp==
Hi all, while discussing the current status of tables in VE, where [[:fr:Wikipédia:ÉditeurVisuel/Avis#Cellule_de_tableau_supprim.C3.A9e|actions like hitting Backspace or Del]] can impact both the structure and the content of a table cell, a few users expressed their hopes that this won't be the case when VE will allow complete editing of tables (precisely like hitting Backspace in the first parameter of a template does not harm the template itself). --[[User:Elitre (WMF)|Elitre (WMF)]] ([[User talk:Elitre (WMF)|talk]]) 15:10, 25 August 2014 (UTC)

== RTL ==

Well, I had to chime in with RTL :)

RTL considerations are not very different for tables. The default direction for columns and cells should be the site's direction.

It would be very nice to be able to change the direction of:
* the whole table: in which direction do the columns go
* a column: for example, in a table of the largest cities in the US in a Hebrew Wikipedia article, the table is RTL by default, and most of the data is written in Hebrew, but the column with names of the cities in English should be all LTR.
* a single cell
* a row. This would be useful for articles such as [[:en:List of numbers in various languages]], but if its development is expensive, I'd guess that the priority of this is lower.

There are also the cursor movement considerations. They, again, aren't very special, but during the development it must be tested that if I'm at the end of a cell in an RTL table and I press the left arrow key, I am moving to the next (logical) cell, and so on.

Thanks for the consideration :) --[[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:40, 19 October 2014 (UTC)

: {{ping|Amire80}} Block-level language (and directionality) editing is something that we need to do more widely, and represents a huge amount of design work that is not a high priority; however, you can make a selection and use the inline language tool to set RTL/LTR status and/or language across the whole selection. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 18:21, 20 October 2014 (UTC)

== Ctrl-End ==

I love using the Ctrl-Home and the Ctrl-End keys, which bring the caret to the beginning and the end of the document. (The actual combination may be different on Mac OS.) This already works well in VE.

I also love the little variation to this feature that exists in LibreOffice. If you press Ctrl-End in a table cell, the caret goes to the end of the cell. If you are already at the end of a cell, it goes to the last row of the table. And if you pressing it for the third time, it goes to the end of the document. Comparable logic works for Ctrl-Home. AFAIK, in other word processors, Ctrl-End always goes immediately to the end of the document, but I might be wrong.

It maybe just me, but I find this feature very convenient, and I miss it when I use Google Docs or MS-Word.

Please consider this :) --[[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:58, 19 October 2014 (UTC)

== Feedback - most needed next features ==

Hi team,

I've been playing with the new table editor function and I'm working on a new, Table-heavy, list article that I've wanted to create for ages but until now I never dared start. So - thank you! The 'add new row' feature is the 'killer app' for visual-editor tables as far as I'm concerned - I never wanted to start a big table before out of fear that if I changed my plan for the layout/content then I would have to manually go through and add pipes to each segment manually to add a new line....

With that said, I've been pushing the limits of what the current table editor can do and I find myself switching back and forth between visual and traditional editor to get different things done in the easiest manner. The single most time-consuming thing that I have to do on the traditional editor is what is listed in your "possible features" list as: ''' "Reorder columns (drag sort)" '''. From my personal experience with this version of visual editor, I would strongly suggest that THIS is the most important priority.

The NEXT most important issue, again, in only my own experience with this software as it currently stands, is the fact that currently you have to double-click to activate a cell for editing. This means that, even though you're already in editing mode, you have to constantly swap back off the keyboard to the mouse to double-click a new cell in order to enter content. If it were only a single-click, then this would enable all sorts of keyboard shortcuts to navigate between cells. Most importantly, 'double-click to edit a cell' means that you cant use the Tab or arrow keys to navigate around a table while editing. This greatly slows down data-entry.

Lots more other features could be added of course, and everyone will have their own ideas, but I just wanted to give my feedback based on the current iteration. Great work, keep it up. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 16:08, 27 January 2015 (UTC)

:[[User:Wittylama|Wittylama]], if I said that your comments were thoughtful and wise, you might guess that I have exactly the same POV. Actually, the ability to tab between cells is #1 on my list. Drag-and-drop columns (and rows, I think, but I'm certain about the columns) is definitely in the works. I haven't heard anything about changing the requirement to double-click on table cells, but I'll ask. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:06, 9 February 2015 (UTC)
::Thanks [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]]! I'll try to come to the triaging meeting today and will mention it if I can. I've also noticed another weird thing within the tables when inserting an external link (actually, I'm not sure if it's limited to only adding external links within tables or happens everywhere). I'm working on [https://en.wikipedia.org/wiki/User:Wittylama/SAI an article in a sandbox in en.wp] with a LOT of tables. I'm deliberately trying to push the system to its limits - and it's holding up pretty nicely. It's slowing down a LOT when I load the visual editor, but that's not surprising. I'm also round-tripping a LOT between the two editing styles depending on the functionality I need (they're both better for different things). One thing that does frustrate (other than what I already mentioned as feature requests) that when I insert/edit a new external link it:
::*Frequently inserts an INTERNAL link to the word that I highlighted - even though I pasted in the URL that I wanted to insert as an external link. It seems that if I press the done/insert link button before it has finished thinking, then it simply forgets I had added an external link URL, and makes it an internal link instead. I worked out that I have to wait for a few seconds before it finishes thinking, and THEN press done.
::*When I want to open up and edit in VE an external link that I had already placed in a table previously, I have to double-click the cell to activate it (this sometimes sends me to the very bottom of the page from where I have to scroll back up. Then, with the cell active, I single-click on the link to activate the dialogue to edit it - which will then send me to the very top of the page from where I have to scroll back down.
::Not sure if I can turn those into formal bug reports, but if you've seen something similar (or can replicate that when trying to use the VE on the sandbox article I linked above) please tell me. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 13:43, 11 February 2015 (UTC)
:::[[User:Wittylama|Wittylama]], your first one is already filed as a bug. It happens to me, too.
:::The bad scrolling is probably browser dependent. Are you using Safari? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:22, 20 February 2015 (UTC)
::::Hiya [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] I'm using Chrome on OSX. I've replied in greater detail over on [[w:Wikipedia:VisualEditor/Feedback#Suggestions]] with a more precise way to replicate the behaviour. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 12:07, 27 February 2015 (UTC)

== Keyboard interaction to change the focus in the table ==
I miss some keyboard function...
I like to work with the keyboard, to change the focus to the next field in the table.
I like the intergration like MS Excel.
Here I can select with the cursor field the correct field in the table and can input my text. After I finish to write the text in the field, I can press enter to go to the next field or with cursor left, right, up and down to navigate to my next favorite field.

Talk:VisualEditor/Design/Table editor

2015-08-27T06:30:47Z

213.61.254.68:

== Hovering on mobile? ==

I like this design, and I think it covers all the basics: change the number of rows and columns, set the top row to gray (or not), etc.

One possible problem: How do you "hover" on a mobile device? Is table editing intended to be impossible for mobile users? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 23:01, 10 July 2014 (UTC)

: {{ping|Whatamidoing (WMF)}} For touch devices, we're expecting to only show the handles if you select in the area (''i.e.'' if you drop a cursor there), which is slightly less quick but works well enough. Does this make sense to you? [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 02:43, 11 July 2014 (UTC)

:: I think the hovering is good for advanced editors. But for beginners they will not see that there is an affordance to add or delete tables. I suggest that there be icons for this (similar to the Confluence wiki, I've seen many beginners able to use tables with their icons), and that they be turned on by default. Advanced users can then turn them off. As noted above, please look into how responsive your design is on pads and telephones (although I am old-fashioned and use a laptop, still). --[[User:WiseWoman|WiseWoman]] ([[User talk:WiseWoman|talk]]) 06:17, 11 July 2014 (UTC)

::: {{ping|WiseWoman}} Maybe the design sketches don't make it clear enough – the idea is that on either selection or hover tools would be provided. I'm not sure about whether there's enough space to try to show lots of icons (rather than just a button) given how wikis generally lay out their tables. Also, all of VisualEditor is designed to work on both mobile and desktop devices, worry not. :-) [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:35, 11 July 2014 (UTC)

:: I agree. Provide something to click (or touch) to select a row or a column. I prefer option 8 as well - menu drops down when the row or column is selected. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:23, 11 July 2014 (UTC)

::: {{ping|Filceolaire}} Yes, the idea is to how the handles on hover or selection; on mobiles, it will have to be selection-only. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:35, 11 July 2014 (UTC)

== Menu for changing the whole table ==
There should be a button to click to bring up a menu of options that apply to the whole table:
* Make table sortable/unsortable
* select format (lines colours etc.) from a shortlist of preset named options. Each wiki to define what options they want to offer as their style guidelines. Shell may vary the details of these - if you have the 'subdued' shell then colours are toned down, made more pastel; if you have the 'high contrast' shell then everything is tweaked to make it more legible to people with poor eyesight. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 15:06, 11 July 2014 (UTC)

: {{ping|Filceolaire}} That's what the grab handle in the top left would do – click to get a menu for the whole table, drag to move the table elsewhere. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:30, 11 July 2014 (UTC)
: I've now modified the description to make it obvious – thanks for the catch. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:44, 11 July 2014 (UTC)

== merge cells / split cells ==

I notice the desired functionality includes merging and splitting cells. Is this really needed? I know this was used in the good old days as a presentation tool for web pages but I'm pretty sure we don't want to do that. Is this used much on wikipedia? The immediate effect of doing this is that it prevents the table from being sorted and makes it impossible to add or delete rows and columns. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:32, 11 July 2014 (UTC)
:It is used unfortunately often, although on en.wp this is usually handled through complex templates that construct the table for you. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:17, 11 July 2014 (UTC)

== Wikidata integration ==

Wikidata integration is a thing which tables will need to have at some stage in the future. This can come in two ways:
# Import data from multiple wikidata items. In this type of table each row in the table corresponds to one item in wikidata and each column corresponds to a property that may be used in a statement about that item or the qualifier to a property.
# Import data from one wikidata item. For example a sports league table. Each league season will have an item. In that item there will be statements for each team giving all their stats so each row is the object of a "participant" property and each column is a qualifier to the wikidata statements about those participants.

Maybe number 2. should be a bunch of templates? [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:43, 11 July 2014 (UTC)

: {{ping|Filceolaire}} Neither of these issues are in-scope for table editing; those are both kinds of transclusion, and per the Wikidata team we're not rushing to implement them yet. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:36, 11 July 2014 (UTC)
::OK then. Just so long as the software doesn't prevent this being added later. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 19:20, 22 July 2014 (UTC)

::: {{ping|Filceolaire}} Indeed! [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:46, 22 July 2014 (UTC)

== Do we want people to set column widths? ==

It is important that wikipedia pages are readable on a wide variety of screen sizes from cheap phones to projections. Sometimes people will want the table to autoadjust to the screen size. This can mean you have really narrow columns - in those cases people will want to side scroll instead. I'm not sure what the solution is but I'm a little wary of having column widths dictated by editors rather than readers.

Row heights should IMHO always autoadjust and should never be preset else you can lose info off the bottom of the cell without even knowing it. [[User:Filceolaire|Filceolaire]] ([[User talk:Filceolaire|talk]]) 14:54, 11 July 2014 (UTC)

:I sometimes want to declare that two-column tables must be evenly split (column width = 50%). Defining an exact number of pixels is not so good in most cases. I've seen a few that use small "columns" basically for color-coding. That might be a reasonable use of pixel-based definitions. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 17:20, 11 July 2014 (UTC)

:: {{ping|Filceolaire|Whatamidoing (WMF)}} However, maybe we don't want to encourage that? I'm not sure. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 17:59, 11 July 2014 (UTC)

:::Don't want to encourage pixel-based column sizes, or don't want to encourage any column sizes at all? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 16:59, 14 July 2014 (UTC)

:::: {{ping|Whatamidoing (WMF)}} The latter; sorry for my inclarity. The number of times people want to do certain things may be high, but it's almost always against the intent of the system (in this case, HTML). [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 19:24, 14 July 2014 (UTC)
:::::What does "encourage" mean in this context? Making it impossible to fix (=at the very least, to remove) a preëxisting column-size problem might be less than desirable. If you take away the ability to set them entirely, then I'll just do it in wikitext—which is fine for me, but not so great for other users. However, I would not want to make it a prominent feature, because usually it shouldn't be done. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 20:07, 14 July 2014 (UTC)

== What is the initial size of 4x4 based on? ==

Did you do some kind of research on table sizes in Wikipedia to get to these figures? If you want a quick and simple solution, it would be ideal if the initial size fits in at least some cases. [[User:Dcutter|Dcutter]] ([[User talk:Dcutter|talk]]) 20:05, 14 July 2014 (UTC)

: {{ping|Dcutter}} Yes; I went through Special:Random on a few wikis hunting for use of tables, and found that four columns seemed to be about the normal (for the relatively rare articles that actually use tables). From a quick spate of Randoms just now, see [[W:Donnie Wahlberg#Film]], [[W:de:Bahnhof Coesfeld (Westf)#Bedienung]] and [[W:es:Chimillas#.C3.9Altimos alcaldes de Chimillas]] for examples. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 20:41, 14 July 2014 (UTC)

== Variation 8 (all actions in menu) ==

This looks really good! Regarding point 8 (variation: all actions shown in menu), I prefer this and think it's generally a good idea if all actions are also available through menus somewhere, not only icons. In my experience, I many users grew up with traditional "menu-driven" software and would not immediately realise that the + icon means "insert row/column" if it isn't spelled out somewhere. [[User:Stephan Matthiesen|Stephan Matthiesen]] ([[User talk:Stephan Matthiesen|talk]]) 09:09, 22 July 2014 (UTC)
: I do agree, I think Variation 8 is more user friendly because it is "classic". I think it is the best solution. [[User:NemesisIII|NemesisIII]] ([[User talk:NemesisIII|talk]]) 22:02, 26 July 2014 (UTC).
==Recommendation from fr.wp==
Hi all, while discussing the current status of tables in VE, where [[:fr:Wikipédia:ÉditeurVisuel/Avis#Cellule_de_tableau_supprim.C3.A9e|actions like hitting Backspace or Del]] can impact both the structure and the content of a table cell, a few users expressed their hopes that this won't be the case when VE will allow complete editing of tables (precisely like hitting Backspace in the first parameter of a template does not harm the template itself). --[[User:Elitre (WMF)|Elitre (WMF)]] ([[User talk:Elitre (WMF)|talk]]) 15:10, 25 August 2014 (UTC)

== RTL ==

Well, I had to chime in with RTL :)

RTL considerations are not very different for tables. The default direction for columns and cells should be the site's direction.

It would be very nice to be able to change the direction of:
* the whole table: in which direction do the columns go
* a column: for example, in a table of the largest cities in the US in a Hebrew Wikipedia article, the table is RTL by default, and most of the data is written in Hebrew, but the column with names of the cities in English should be all LTR.
* a single cell
* a row. This would be useful for articles such as [[:en:List of numbers in various languages]], but if its development is expensive, I'd guess that the priority of this is lower.

There are also the cursor movement considerations. They, again, aren't very special, but during the development it must be tested that if I'm at the end of a cell in an RTL table and I press the left arrow key, I am moving to the next (logical) cell, and so on.

Thanks for the consideration :) --[[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:40, 19 October 2014 (UTC)

: {{ping|Amire80}} Block-level language (and directionality) editing is something that we need to do more widely, and represents a huge amount of design work that is not a high priority; however, you can make a selection and use the inline language tool to set RTL/LTR status and/or language across the whole selection. [[User:Jdforrester (WMF)|Jdforrester (WMF)]] ([[User talk:Jdforrester (WMF)|talk]]) 18:21, 20 October 2014 (UTC)

== Ctrl-End ==

I love using the Ctrl-Home and the Ctrl-End keys, which bring the caret to the beginning and the end of the document. (The actual combination may be different on Mac OS.) This already works well in VE.

I also love the little variation to this feature that exists in LibreOffice. If you press Ctrl-End in a table cell, the caret goes to the end of the cell. If you are already at the end of a cell, it goes to the last row of the table. And if you pressing it for the third time, it goes to the end of the document. Comparable logic works for Ctrl-Home. AFAIK, in other word processors, Ctrl-End always goes immediately to the end of the document, but I might be wrong.

It maybe just me, but I find this feature very convenient, and I miss it when I use Google Docs or MS-Word.

Please consider this :) --[[User:Amire80|Amir E. Aharoni]] ([[User talk:Amire80|talk]]) 13:58, 19 October 2014 (UTC)

== Feedback - most needed next features ==

Hi team,

I've been playing with the new table editor function and I'm working on a new, Table-heavy, list article that I've wanted to create for ages but until now I never dared start. So - thank you! The 'add new row' feature is the 'killer app' for visual-editor tables as far as I'm concerned - I never wanted to start a big table before out of fear that if I changed my plan for the layout/content then I would have to manually go through and add pipes to each segment manually to add a new line....

With that said, I've been pushing the limits of what the current table editor can do and I find myself switching back and forth between visual and traditional editor to get different things done in the easiest manner. The single most time-consuming thing that I have to do on the traditional editor is what is listed in your "possible features" list as: ''' "Reorder columns (drag sort)" '''. From my personal experience with this version of visual editor, I would strongly suggest that THIS is the most important priority.

The NEXT most important issue, again, in only my own experience with this software as it currently stands, is the fact that currently you have to double-click to activate a cell for editing. This means that, even though you're already in editing mode, you have to constantly swap back off the keyboard to the mouse to double-click a new cell in order to enter content. If it were only a single-click, then this would enable all sorts of keyboard shortcuts to navigate between cells. Most importantly, 'double-click to edit a cell' means that you cant use the Tab or arrow keys to navigate around a table while editing. This greatly slows down data-entry.

Lots more other features could be added of course, and everyone will have their own ideas, but I just wanted to give my feedback based on the current iteration. Great work, keep it up. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 16:08, 27 January 2015 (UTC)

:[[User:Wittylama|Wittylama]], if I said that your comments were thoughtful and wise, you might guess that I have exactly the same POV. Actually, the ability to tab between cells is #1 on my list. Drag-and-drop columns (and rows, I think, but I'm certain about the columns) is definitely in the works. I haven't heard anything about changing the requirement to double-click on table cells, but I'll ask. [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 22:06, 9 February 2015 (UTC)
::Thanks [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]]! I'll try to come to the triaging meeting today and will mention it if I can. I've also noticed another weird thing within the tables when inserting an external link (actually, I'm not sure if it's limited to only adding external links within tables or happens everywhere). I'm working on [https://en.wikipedia.org/wiki/User:Wittylama/SAI an article in a sandbox in en.wp] with a LOT of tables. I'm deliberately trying to push the system to its limits - and it's holding up pretty nicely. It's slowing down a LOT when I load the visual editor, but that's not surprising. I'm also round-tripping a LOT between the two editing styles depending on the functionality I need (they're both better for different things). One thing that does frustrate (other than what I already mentioned as feature requests) that when I insert/edit a new external link it:
::*Frequently inserts an INTERNAL link to the word that I highlighted - even though I pasted in the URL that I wanted to insert as an external link. It seems that if I press the done/insert link button before it has finished thinking, then it simply forgets I had added an external link URL, and makes it an internal link instead. I worked out that I have to wait for a few seconds before it finishes thinking, and THEN press done.
::*When I want to open up and edit in VE an external link that I had already placed in a table previously, I have to double-click the cell to activate it (this sometimes sends me to the very bottom of the page from where I have to scroll back up. Then, with the cell active, I single-click on the link to activate the dialogue to edit it - which will then send me to the very top of the page from where I have to scroll back down.
::Not sure if I can turn those into formal bug reports, but if you've seen something similar (or can replicate that when trying to use the VE on the sandbox article I linked above) please tell me. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 13:43, 11 February 2015 (UTC)
:::[[User:Wittylama|Wittylama]], your first one is already filed as a bug. It happens to me, too.
:::The bad scrolling is probably browser dependent. Are you using Safari? [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] ([[User talk:Whatamidoing (WMF)|talk]]) 18:22, 20 February 2015 (UTC)
::::Hiya [[User:Whatamidoing (WMF)|Whatamidoing (WMF)]] I'm using Chrome on OSX. I've replied in greater detail over on [[w:Wikipedia:VisualEditor/Feedback#Suggestions]] with a more precise way to replicate the behaviour. [[User:Wittylama|Wittylama]] ([[User talk:Wittylama|talk]]) 12:07, 27 February 2015 (UTC)

== Keyboard interaction to change the focus in the table ==
I miss some keyboard function...
I like to work with the keyboard, to change the focus to the next field in the table.
I like the intergration like MS Excel.
Here I can select with the cursor field the correct field in the table an can input my text. After I finish to write the text in the field, I can press enter to go to the next field or with cursor left, right, up and down to navigate to my next favorite field.