Dear Mediawiki Experts,
some weeks ago I moved our mediawik from one Debian server to another and
updated from mediawiki 1.31.14 to 1.33.4. On new instance vector skin is not
displayed as familiar as in the old instance.
Sidebar which was before on the left hand side is now on the bottom of the
site. All logos are not shown. Font is different.
Can some one give me a hint to fix this?
Thanks in advance.
Best regards
Sancho HGH
When I last tried semantic mediawiki (years ago), it permitted (perhaps
even emphasized) generating structured data through writing that contained
typed links. The "type" was a predicate that explained the relationship
between two pages. I think it was also possible to store a tuple of data
inside the link, which may convey the strength of the predicate (for
example) when such information was important and ignore it when it was not
important (I may be confusing this functionality with another extension)
Is any of this inline schema building possible with Cargo or are all typed
links made in the form data fields? For example, in the common AUTHORS and
BOOKS example, what happens if the AUTHOR is actually unknown but there are
several *likely* AUTHORS? One option may be to add a whole field to BOOKS
for LIKELY AUTHORS. Another way might be to create an intermediate page
AUTHORSHIP that ties AUTHOR to BOOK with a field that explains the
relationship in more detail. But, perhaps there is a way to add more nuance
to the AUTHOR assignment itself? Could this information be conveyed in the
AUTHORS field through an additional piece of information placed in
parentheses?
-david
I'm trying to query the cargo database. In PageSchemas, the table is
called simply "Place". Here is the query:
{{#cargo_query:
table=Place
|fields=Place._pageName, Type
|where=Place.Type="Planet"
|format=dynamic table
}}
The code above produces "Error: Table Place not found." as does prepending
the table name with "cargo__" or "cargo_". What am I doing wrong?
-david
Hi folks,
I'm working with Cargo, PageForms, and PageSchemas. I'm trying to define a
hierarchy of places (all assigned to category "Place"). I'm probably doing
several things wrong. The hierarchy is roughly:
SolarSytem- -> Planet --> Continent --> Nation --> SubRegion --> City -->
Neighborhood
I used PageSchemas to generate a "Place" Cargo table, Form, and Template.
It has two fields right now. (1) The "Type" Cargo field is a Page with a
list of possible inputs from the hierarchy above. The "Type" Template is
text with autocomplete. (2) The "PartOf" field is identical except it has
no list of possible inputs since I was hoping it would draw from page
instances.
When I choose a Place "Type" from the list, the selection is displayed as
static text, not as a link (even if I manually create a page with the same
name). When I try to choose a Place "PartOf", autocomplete never finds the
places I've already generated.
What is the proper way to create such a hierarchy? My approach does not
generate real subcategories like Place:SolarSystem and Place:Planet. Is
that what I should be doing? Does that require each subcategory to have its
own schema, form, and template?
Thanks for your guidance,
-david
Hi folks,
If I create a new class with Special:CreateClass, what is the procedure for
later editing the class? Do I need to edit the template and form separately
after their initial creation? Ideally, I'd like to develop my data model
iteratively. Any instances of a class would just have empty values for
parameters added later to the class. Is that possible? My classes look like
-david
I want to be able to stay logged in for 12 hours with the "keep me logged in" box unchecked and be logged in for 7 days with the "keep me logged in" box checked. I have tried $wgObjectCacheSessionExpiry = 43200 and it doesn't seem to work. Does anybody have a suggestion on how to get this going? Thanks
wiki = version 1.35
iis = 10
php = 7.23
Hi,
I've been trying to get rid of the ESLint warnings for the JavaScript code
in some of my extensions, when they go through Jenkins validation. One
warning that appears fairly often is this one:
Where possible, maintain application state in JS to avoid slower DOM queries
no-jquery/no-class-state
I'm not sure if this is a warning that's specific to Wikimedia code, but
doing a web search on it brings up this Wikimedia help page as the only
real result:
https://github.com/wikimedia/eslint-plugin-no-jquery/blob/master/docs/rules…
This page is rather confusing. It says that the warning comes when calling
either hasClass() or toggleClass() on a jQuery element. That part makes
sense, but then the suggested alternatives are strange. The page says that
the following are some examples of bad code:
$( 'div' ).hasClass();
$div.hasClass();
In their place, it suggests the following:
hasClass();
[].hasClass();
div.hasClass();
Can anyone explain this? As far as I'm aware, hasClass() is only defined in
jQuery - and there, only as a method for variables representing jQuery
elements. So what do those "recommended" lines mean? And in general, what
is the best way to determine whether some element on the page has a certain
class?
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Hello,
I set up a test instance of MediaWiki at our site and am trying to get it
configured for LDAP authentication. Per the documentation I could find, I
installed and configured the following extensions:
- LDAPAuthentication2
- LDAPAuthorization
- LDAPProvider
- PluggableAuth
Without LDAPAuthorization enabled, basic LDAP authentication works fine.
However, when I enable LDAPAuthorization and try to filter access by
membership in a specific group, authentication fails every time with an
error saying the user is not authorized.
More specifically, I created a group in our LDAP system called wiki-users
and added myself as a member. I then added an authorization block to the
json file and specified the full DN of this group as a required group. I'm
using plaintext LDAP so I can run packet captures and see the traffic.
When I capture the LDAP traffic, I can see that it's authenticating the
bind user and then my own user, but at no point does it query for this
group.
A sanitized version of my json file is pasted below. Any help is greatly
appreciated!
{
"LDAP": {
"connection": {
"server": "my-LDAP-server.utica.edu",
"port": "389",
"enctype": "clear",
"user": "cn=my-bind-user,dc=utica,dc=edu",
"pass": "xxxxxxxxxxxx",
"options": {
"LDAP_OPT_DEREF": 1
},
"basedn": "dc=utica,dc=edu",
"groupbasedn": "ou=groups,o=utica.edu,dc=utica,dc=edu",
"userbasedn": "ou=people,o=utica.edu,dc=utica,dc=edu",
"searchattribute": "uid",
"searchstring": "uid=USER-NAME,ou=people,o=utica.edu,dc=utica,dc=edu",
"usernameattribute": "uid",
"realnameattribute": "ucPreferredName",
"emailattribute": "mail"
},
"authorization": {
"rules": {
"groups": {
"required": ["cn=wiki-users,ou=groups,o=utica.edu
,dc=utica,dc=edu"]
}
}
},
"groupsync": {
"mechanism": "mappedgroups",
"mapping": {
"sysop": "cn=wiki-admins,ou=groups,o=utica.edu,dc=utica,dc=edu",
"users": "cn=wiki-users,ou=groups,o=utica.edu,dc=utica,dc=edu"
}
},
"userinfo": {
"email": "mail",
"realname": "ucPreferredName"
}
}
}
--
Dave Parker '11
Database & Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
Hi everyone,
A new episode is out of the MediaWiki podcast "Between the Brackets", and I
somehow neglected to send an email about the previous two, so let me
happily announce all three now.
First, about a month ago was the episode with Ilana Fried, who is the
product manager for the Campaigns team at the Wikimedia Foundation, and
also runs the women's health wiki Gynopedia:
https://betweenthebrackets.libsyn.com/episode-90-ilana-fried
Next, I talked to Peter Meyer, who is a research economist at the U.S.
Bureau of Labor Statistics, a member of the Board of Directors of the
Wikimedia DC chapter, and also one of the organizers of the upcoming
WikiConference North America 2021:
https://betweenthebrackets.libsyn.com/episode-91-peter-meyer
And finally, in the episode just released today, I talked to Daisy Chen, a
senior UX researcher at the Wikimedia Foundation, about the research and
user testing that is done by the WMF. You can listen to the episode here:
https://betweenthebrackets.libsyn.com/episode-92-daisy-chen
I hope people listen to all three episodes - they were all very interesting
conversations.
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2021.07. This bundle is compatible with MediaWiki 1.35 or above
and requires PHP 7.2 or above.
Next MLEB is expected to be released in 3 months. If there are very
important bug fixes, we will do an intermediate release. Please give
us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar…
* sha256sum: f7cd8113c095375be51464429dff04c8fa5bb88bc22ba3d780bf5698668e52c5
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.07.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/project/view/1464/
Release notes for each extension are below.
-- Kartik Mistry
== Babel, cldr, CleanChanges and LocalisationUpdate ==
* Localisation and maintenance updates.
== Translate ==
* '''BREAKING CHANGE''': Translate extension now requires MediaWiki
1.35 or above.
* When translating in Page mode, modifying and publishing a message
causes its to become empty ({{phab|T270819}})
* '''SECURITY''': Enhance validation and logging for AggregateGroups
API deletions ({{phab|T282932}})
* Make Special:PageTranslation work with ONLY_FULL_GROUP_BY ({{gerrit|701871}})
* '''BREAKING CHANGE''': Remove TranslateMessageGroupPathVariables
hook ({{gerrit|701678}})
* GettextFFS: Only allow pot mode for source language ({{phab|T230361}})
* Translation page deletion should not clear metadata ({{gerrit|694306}})
* Added content model and handler for translatable modules
({{gerrit|638528}}, {{phab|T271406}})
* Allow showing yearly stats in Special:TranslationStats ({{phab|T281244}})
* '''BREAKING CHANGE''': Remove Validator and LegacyValidatorAdapter
({{gerrit|685438}})
* Improve display of very long insertables ({{gerrit|685805}})
* Fix "Translation units to be deleted appear with unit ID -1 on
Special:PageTranslation" ({{phab|T283971}})
* Localisation updates.
=== Configuration variable changes ===
To address voice and tone issues in the Translate extension
({{phab|T277965}}) the following configuration variable names have
been renamed:
* <code>TranslateBlacklist</code> →
<code>TranslateDisabledTargetLanguages</code>
* <code>TranslateAuthorBlacklist</code> →
<code>TranslateAuthorExclusionList</code>
* <code>TranslateCheckBlacklist</code> →
<code>TranslateValidationExclusionFile</code>
''The old variables will be supported for MLEB 2021.07 release but
removed in the MLEB 2021.10 release.''
If you have defined
[[Help:Extension:Translate/Group_configuration|message groups]]
defined with <code>LANGUAGE</code> attributes,
<code>whitelist/blacklist</code> have been changed to
<code>include/exclude</code>
== UniversalLanguageSelector ==
* '''BREAKING CHANGE''': UniversalLanguageSelector extension now
requires MediaWiki 1.35 or above.
* MODERN VECTOR: Position language menu below language button ({{phab|T276248}})
* Update jquery.uls and jquery.ime from upstream
* Fix "Suggested language list not available for ULS version in new
language button". ({{phab|T282037}})
* MODERN VECTOR: Fix "ULS settings window can’t be opened with the
preferences link on new Vector". ({{phab|T282956}})
* Fix "ULS preferences tool link cannot be opened when compact
languages disabled" ({{phab|T286574}})
* Localisation updates.
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com