Hi all,
I would like to change my Vector Skin look, I managed to do some modifications but I didn't succeed in changing the CSS of the left SideBar (left menu).
Does Anyone know what is the class or id controlling the CSS of the links appearing in left menu Sidebar?
(I tried #p-personal, #p-cactions, #pBody, .portlet, ... without success, I want to change the color of the links, for example : a.portlet { color:#735885;} ).
However, I have succeed to change the color of other links in the the articles by : a { color:#735885;} but the links in SideBar remain still blue.
Thank you.
Cordialement,
Mehdi CHOUIREF
IT-CE - Groupe BPCE
Assistant Ingénieur Méthodes & Qualité
Direction Edition - Pilotage transverse - Support au Pilotage des Projet - EDT - PIL - SPP
430, rue Pierre Simon Laplace - BP 442
Pichaury 4 - 1er étage - bureau 1.024
13 592 Aix en Provence Cedex 3
Tel : + 33 4 42 12 79 48 (soit le poste 4 79 48)
mehdi.chouiref(a)it-ce.fr<mailto:mehdi.chouiref@it-ce.fr>
Ce message et toutes les pièces jointes (ci-après le 'message') sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. BPCE et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié.
This message and any attachments (the 'message') are confidential and intended solely for the addressee(s). Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither BPCE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified.
Ce message et toutes les pièces jointes (ci-après le 'message') sont confidentiels et établis à l'intention exclusive de ses destinataires. Si vous n'êtes pas destinataire de ce message, merci de le détruire et d'en avertir immédiatement l'expéditeur.
Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération.
IT-CE décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié.
This message and any attachments (the 'message') are confidential and intended solely for the addressee(s). If you receive this message in error, please delete it and immediately notify the sender. Any unauthorised use or dissemination is prohibited. E-mails are susceptible to alteration. Neither « IT-CE » will not be liable for the message if altered, changed or falsified.
Hello all,
I was wondering if there's a clean way within the Wiki codebase to
generate a history entry for an article without actually modifying the
content. Essentially I'd like to treat the history as a logfile for
specific events related to the article that don't actually modify the
article.
Thanks,
Rob.
--
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.
> Install the Nuke extension and go to town.
I will check it out - Thanks for the pointer.
> If you had a backup of your database, you could just restore it.
The corruption was discovered months after it happened, with multiple
backups in between.
> The titles seem to have invalid UTF-8 sequences in them. I'm not sure
> how it's possible to create such titles, in any version of MediaWiki.
This happened a couple of upgrades back, while the site wasn't being
used. I have no
idea what version was running at the time.
> cleanupTitles.php will rename all the pages to valid titles. You
> can then use deleteBatch.php to delete them.
I now know what is on my schedule for this weekend. :)
Thanks to both of you.
Not sure how to check that. Here is what is in the LocalSettings.php file:
$wgExtraNamespaces[506] = "DBA";
$wgExtraNamespaces[507] = "DBA_talk";
$wgContentNamespaces[] = array( NS_MAIN, NS_TALK, NS_DBA, NS_DBA_talk );
$wgNamespacesToBeSearchedDefault = array(
NS_MAIN => true,
NS_CATEGORY => true,
NS_IMAGE => true,
NS_DBA => true,
);
----------------------------------------------
> From: Benjamin Lees <emufarmers(a)gmail.com<mailto:emufarmers@gmail.com>>
> My guess is that you didn't define the namespace constant NS_DBA.
-------------------------------------------------
On Thu, Mar 8, 2012 at 12:10 PM, Shaffer, Kurt <Kurt_Shaffer(a)steris.com<mailto:Kurt_Shaffer@steris.com>> wrote:
> Hi all,
> New to the list so if asked please excuse me.
>
> I am trying to get the default search to search a new Namespace, I've added it to the LocalSettings.php file as shown:
>
> #Set default searching
> $wgNamespacesToBeSearchedDefault = array(
> ? ? ? ?NS_MAIN => ? ? ? ? ? true,
> ? ? ? ?NS_FILE => ? ? ? ? ? true,
> ? ? ? ?NS_DBA => ? ? ? ? ? ?true,
> );
>
> When not logged in only main and file are checked and searched. ?I did a modification to the database as recommended in some documentation adding the namespace to all users options. ?When a user is logged in it searches the new namespace by default.
>
> How can I get it to include the namespace for searches when not logged in?
>
> Thankx.
> Kurt
>
Hi all,
New to the list so if asked please excuse me.
I am trying to get the default search to search a new Namespace, I've added it to the LocalSettings.php file as shown:
#Set default searching
$wgNamespacesToBeSearchedDefault = array(
NS_MAIN => true,
NS_FILE => true,
NS_DBA => true,
);
When not logged in only main and file are checked and searched. I did a modification to the database as recommended in some documentation adding the namespace to all users options. When a user is logged in it searches the new namespace by default.
How can I get it to include the namespace for searches when not logged in?
Thankx.
Kurt
Bonjour,
Je suis en train d'installer un site utilisant mediawiki.
Je voudrais qu'il fonctionne pour des utilisateurs français et anglais, principalement.
Je voudrais que pour chaque article paru, il soit possible de traduire l'article dans l'autre langue, et d'indiquer sur la page de l'article, un lien vers sa traduction.
J'ai bien compris que le fait de créer une page en ajoutant un "slash" et le code de la langue, permet de réaliser la traduction de l'article.
Exemple: Si la langue par défaut est l'anglais, alors Page1/fr permet de créer la traduction en français de Page1 écrite en anglais.
J'ai bien compris qu'en plaçant manuellement un lien vers la page traduite, cela permet de cliquer sur ce lien et d'arriver sur la traduction de la page.
Mais comment faire pour l'automatiser ? Est-il possible de récupérer les façons de faire du site meta-wiki ou du site mediawiki dans ce domaine du multilinguisme ? Et comment faire ?
Les articles que j'ai lu là dessus, ne m'ont pas éclairé. Je ne comprends rien.
L'installation de "translate" a échoué. Et je n'arrive pas à savoir quoi faire.
Je ne comprends pas du tout les logiques "wiki farm" qui semblent pouvoir aider dans le domaine du multilinguisme.
Bref, je suis perdu !
I have a hobby site that was attacked by Chinese language spammers awhile
back.
MediaWiki: 1.18.0, PHP: 5.2.17 (cgi-fcgi), MySQL: 5.1.56, Apache: 2.2.x,
CentOS
http://gz.equoria.net/index.php?title=Main_Page
They left behind hundreds of pages with corrupt titles;
http://gz.equoria.net/index.php?title=Special:UncategorizedPages
The MediaWiki delete function can't work on pages that can't be accessed,
so how can I clean up this mess?
Will cleanupTitles.php<http://www.mediawiki.org/wiki/Manual:CleanupTitles.php>
help?
How about using *phpMyAdmin*? I looked at the *page *table. Starting
around *page_id 442* you see hundreds of page titles that are massively
long numbers. I could delete each record, but am concerned that would
leave pointers and corrupt the database.
Any pointers would be appreciated.
Thanks in advance.
Sakshale
I'm happy to announce the availability of the first beta release of the new
MediaWiki
1.19 release series.
Please try it out and let us know what you think. Don't run it on any wikis
that you really
care about, unless you are both very brave and very confident in your
MediaWiki
administration skills.
MediaWiki 1.19 is a large release that contains many new features and bug
fixes. This is a
summary of the major changes of interest to users. You can consult the
RELEASE-NOTES-1.19 file for the full list of changes in this version.
*********************************************************************
What's new?
*********************************************************************
MediaWiki 1.19 brings the usual host of various bugfixes and new features.
Comprehensive list of what's new is in the release notes.
* Bumped MySQL version requirement to 5.0.2.
* Disable the partial HTML and MathML rendering options for Math,
and render as PNG by default.
* MathML mode was so incomplete most people thought it simply didn't work.
* New skins/common/*.css files usable by skins instead of having to copy
piles of
generic styles from MonoBook or Vector's css.
* The default user signature now contains a talk link in addition to the
user link.
* Searching blocked usernames in block log is now clearer.
* Better timezone recognition in user preferences.
* Extensions can now participate in the extraction of titles from URL paths.
* The command-line installer supports various RDBMSes better.
* The interwiki links table can now be accessed also when the interwiki
cache
is used (used in the API and the Interwiki extension).
Internationalization
- --------------------
* More gender support (for instance in user lists).
* Add languages: Canadian English.
* Language converter improved, e.g. it now works depending on the page
content language.
* Time and number-formatting magic words also now depend on the page
content language.
* Bidirectional support further improved after 1.18.
Release notes
- -------------
Full release notes:
https://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_19_0beta1/phase3/RELEA
SE-NOTES-1.19
https://www.mediawiki.org/wiki/Release_notes/1.19
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta1.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.19/mediawiki-1.19.0beta1.tar.gz.si
g
Public keys:
https://secure.wikimedia.org/keys.html
In our MediaWiki 1.18.1 system, user skin preferences are mysteriously changing. Any advice?
Our admins set everybody to use the Vector skin and hid all the other skins in LocalSettings.php, like so:
$wgDefaultSkin = 'vector';
// We want the Vector JavaScript & CSS page links to show up in My Preferences,
// so don't use $wgHiddenPrefs[] = 'skin'. Hide skins individually.
$mySkipSkins = array(
'chick',
'standard',
'cologneblue',
'modern',
'monobook',
'myskin',
'nostalgia',
'simple',
);
$wgSkipSkins = array_merge($wgSkipSkins, $mySkipSkins);
We also removed all "skin" rows from the user_properties table by database delete command. Nevertheless, some users get the monobook skin sometimes, and we are seeing rows created in user_properties, sometimes blank, and sometimes with up_value = 'monobook'.
mysql> select * from wp_user_properties where up_property = 'skin';
+---------+-------------+----------+
| up_user | up_property | up_value |
+---------+-------------+----------+
| 537 | skin | |
| 1341 | skin | |
| 559 | skin | |
| 1327 | skin | |
| 659 | skin | |
+---------+-------------+----------+
Users are not setting their skin on purpose to cause this -- something is happening behind their backs. Does anybody have any idea why this is happening, and how to prevent anyone from getting other skins applied? Thanks.
DanB