Hi,
I'm wondering if anyone can point me into the right direction of how to edit the 'Vector' skin?
Basically since I'm really new to Mediawiki I just made a copy of the skin folder and php file called vectorx in both cases:
folder: vectorx
php file: VectorX.php
so far I've been following these pages on the Mediawiki site:
http://www.mediawiki.org/wiki/Manual:Skinning/Tutorialhttp://www.mediawiki.org/wiki/Manual:Skinning/Vectorhttp://www.mediawiki.org/wiki/Manual:Skinning/Vector/Example
however, the last two links are the best though unfortunately they're for up to Mediawiki 1.19.
My setup is running Mediawiki 1.22 installed from the Archlinux repos.
Since this is a really basic test setup I'm using, I have elected to go for nginx and sqlite. The wiki is accessible and everything is fine.
Using the modifications described in the links above the new skin shows up as VectorX however, the menus aren't shown??
Just everything from "Main Page" down... with no formatting.
Having no experience with Mediawiki prior to this but reading the man/faq/wiki pages it seems that the 'Vector' skin is now integrated into the core of the wiki. How does this affect editing and replication?
At the moment all I would like to do is replicate 'vector' in 'vectorx' in order to learn how to modify it in terms of menus, backgrounds and other bits and pieces.
Regards,
Kaya
Hi All,
I installed mediawiki on debian wheezy and set postgresql database as
database for mediawiki. It installed nicely and working, I can create new
pages, users etc.
But when I tried to delete a user through postgresql database, I tried to
access the wikidb database in postgresql, I found that it was empty. There
was no table in database.
While it is working fine and It have entries of postgresql databse in
Localsetting.php file. I want to know where is database getting save and
how can I take the backup of that database.
Or please tell me how can I sync it with my postgresql database. My
postgresql database version is 9.1. I installed mediawiki from debian
wheezy repository.
Thanks & Regards
Amit Bondwal
I am out of the office until 12/23/2013.
Thank you for your email, I will be out of the office on 12/20/2013 and
returning to the office 12/23. Please contact BT-MMS-MiddlewareEngineering
for any emergencies.
Happy Holidays
Thank you,
Best Regards,
Robert L. Garritano | Discover Financial Services
MMS - Middleware Engineering
2500 Lake Cook Road, Riverwoods, IL 60015
( Office (224) 405-1621
RobertGarritano(a)discover.com
Note: This is an automated response to your message "[MediaWiki-l] Fwd:
Draft for Bugzilla etiquette guidelines (last call)" sent on 12/20/2013
2:23:07.
This is the only notification you will receive while this person is away.
Please consider the environment before printing this email.
I want to be able to take a list of pages & delete them in a fashion
similar to the Export Pages function. Just toss the list in and wipe
them. This would be extremely handy while the site is in early
development phases.
Any ideas??
Thanks!
John
I am currently upgrading our intranet Wiki installation to 1.21 (yes, we are one version behind), and I have faced the problem with deprecated message functions, as outlined at mediawiki.org<http://www.mediawiki.org/wiki/Manual:Messages_API#Deprecated_wfMsg.2A_funct…>. For instance:
Instead of:
wfMsg( 'key' );
Do:
wfMessage( 'key' )->text();
The problem of course is that the parametrized messages can have arbitrary parameters which can be themselves function calls, making simple regexp substitution infeasible. Well, I figured out that Perl can be used to solve this problem, because Perl allows arbitrary recursive regexps, which are conveniently accessible via the Regexp::Common module. Something like this does the trick:
use Regexp::Common;
# Convert 'wfMsg->(...)' to 'wfMessage(...)->text()'
sub fix_wfMsg ($) {
(my $string = shift) =~ s/wfMsg\s*($RE{balanced}{-parens=>'()'})/wfMessage$1->text()/g;
return $string;
}
This method would take the string you provide (should be the entire file contents, to account for multi-line wfMsg calls), and do the appropriate string substitution to replace the deprecated call with the correct one, accounting for nested recursive parentheses. As far as I can tell, the only thing it can get wrong in unbalanced parentheses in comments, e.g. if your line ends in '// unbalanced paren (' type of comment.
I hope this helps someone.
I tried a footer extension to add a Wiki-editable footer on all pages of a
site but it adds it before the categories.
Does anyone know of an extension which adds a footer in the same area, as
the Copyright/about stuff?
I want to create a multiple choice Question/Answer structure that visitors
can browse. Depending on what answer they choose, they're taking to the
next question. Thus they can browse this tree of multiple choice
question/answers. The administrators can edit the questions and answers in
regular wiki format. There can be links or images in the questions or
answers.
Is there any way to do this or has anyone seen this anywhere? Maybe some
feature of Semantic wiki?
Dan
Hi,
I have updated my Intranet Wiki from Version 1.19 to Version 1.21.
After Update links in Mediawiki to Intranet Filesystem doesn’t work.
For example this link [file://intranet\foldera\folderb\folderc\Dokuments MyDocuments] works fine in 1.19, after klick it, Windows Explorer open and show the folder.
In Version 1.21 nothing happens.
I have my 1.19 as Backup in different folder, so I can test difference between these versions.
When updating I use my old localsettings.php and don’t make any changes to the configuration.
Any Ideas?
Thanks
Tom