I upgraded mediaWiki from 1.12 to mediaWiki 1.22.3
I upgrade the extension Calendar and other extensions using this URL http://www.mediawiki.org/wiki/Special:ExtensionDistributor
I ran $php maintenance/update.php.
The mediaWiki is working good but the Calendar didn't displayed , I cannot see the calendar.
Please any help.
Thank you.
Hello,
I'm having a little trouble getting a custom hook to perform the actions I
want
it to after upgrading from PHP 5.3 / MW 1.19.2 to PHP 5.4 / MW 1.22.3.
I am hacking an existing extension, ProcessCite, that integrates into the
Cite
extension by adding a custom hook to one of Cite's functions:
# from Cite_body.php
function stack( $str, $key = null, $group, $follow, $call ) {
# add the call to the CiteBeforeStackEntry hook
wfRunHooks( 'CiteBeforeStackEntry', array( &$str, &$call ) );
ProcessCite runs code that creates a value for $str based on the contents of
$call. Here are the relevant parts of ProcessCite:
# Declare the hook:
$wgHooks['CiteBeforeStackEntry'][] = 'wfProcessCite';
# the function itself
function wfProcessCite($str, $argv){
# process $argv and $str to create a new version of $str
# $argv remains unchanged, $str is set to new value
$str = "new string";
return true;
}
Debug statements reveal that wfProcessCite is creating the correct value for
$str, but the value is not altered when wfProcessCite finishes. I am not
sure
if I am calling the hook in the wrong way, given that I want to alter the
value of $str.
The MW manual page on hooks (http://www.mediawiki.org/wiki/Manual:Hooks) is
somewhat confusing -- what is the difference between passing $someData to a
function versus passing a set of parameters?!
Any help would be appreciated!
Thank you,
Amelia.
--
Amelia Ireland
GMOD Community Support
Generic Model Organism Database project
http://gmod.org || @gmodproject
Whenever I try to enter Special Gadgets on my localhost wiki, I get the following messages:
[d6ed31cf] /allthetropes/index.php/Special:Gadgets Exception from line 376 of C:\xampp\htdocs\allthetropes\includes\SpecialPage.php: Call to undefined method SpecialGadgets::getPageTitle
Backtrace:
#0 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(98): SpecialPage->__call(string, array)
#1 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(98): SpecialGadgets->getPageTitle(string)
#2 C:\xampp\htdocs\allthetropes\extensions\Gadgets\SpecialGadgets.php(30): SpecialGadgets->showMainForm()
#3 C:\xampp\htdocs\allthetropes\includes\SpecialPage.php(631): SpecialGadgets->execute(NULL)
#4 C:\xampp\htdocs\allthetropes\includes\SpecialPageFactory.php(488): SpecialPage->run(NULL)
#5 C:\xampp\htdocs\allthetropes\includes\Wiki.php(298): SpecialPageFactory::executePath(Title, RequestContext)
#6 C:\xampp\htdocs\allthetropes\includes\Wiki.php(602): MediaWiki->performRequest()
#7 C:\xampp\htdocs\allthetropes\includes\Wiki.php(467): MediaWiki->main()
#8 C:\xampp\htdocs\allthetropes\index.php(49): MediaWiki->run()
#9 {main}
Notice: Uncommitted DB writes (transaction from DatabaseBase::query (User::loadFromDatabase)). in C:\xampp\htdocs\allthetropes\includes\db\Database.php on line 3944
Gadgets themseves work fine, and I can manually edit the CSS/JS files for them without a, I just can't access the special page for them at all and have no idea why.
Hello,
we are running Mediawiki with some small modifications (e.g. the Vector.php skin).
My plan was to checkout a specific branch (e.g. 1.21.1).
Then I committed some local modifications to the code. The local repo is now ahead of e.g. 1 commit of origin.
Minor version upgrades (1.21.2) can be merged without any trouble.
My question is now, how an major upgrade (1.21 to 1.22) preserving my local commits can be accomplished using GIT.
The only way I found so far was using cherry-pick to transfer the local commits to the new branch.
Any ideas?
The MW guide recommends to make a fresh clone and copy the config file, images...
http://www.mediawiki.org/wiki/Manual:Upgrading#Using_Git
Thank you,
Christoph
I have not seen this before & a quick web search doesn't seem to find
much.
Any ideas or tips. This site is recently moved from one server to
another along with a Mediawiki version update to current stable.
Could not create directory "mwstore://local-backend/local-public/5/55".
Of course the file does not get processed.
Any Ideas!
Thanks!
John
This conversation would IMHO be more appropriate on mediawiki-l because
it affects mainly third parties who care about the higher privacy
standards of EU, but thanks for starting it.
On asking WMF legals, no worries, they were already pointed to the
possibility of an issue with 2009/136/EC / "EU cookie law" / revised
ePrivacy Directive on Fri, 16 Aug 2013 11:18:32 +0200 (no reply
received, but I was merely giving a pointer and not interested in
following up).
Some fines were levied just few days ago, as a quick search reveals:
<http://www.bna.com/spanish-dpa-levies-n17179882151/>.
As for Wikimedia projects, relevant links are
* stub https://meta.wikimedia.org/wiki/Cookie_jar
* draft
<https://meta.wikimedia.org/wiki/Privacy_policy/FAQ#Can_you_give_me_some_exa…>
*
<https://www.mediawiki.org/wiki/Requests_for_comment/Performance_standards_f…>
I believe most issues with cookies are currently/usually caused by some
extensions which unconditionally add one or more. The biggest drive for
their removal, so far, has been performance. Sometimes they are replaced
with localStorage, which is better for performance, but I have no idea
how better for privacy.
Nemo
Hi,
I thought I would ping you all for suggestions since some of you may have already gone through something similar.
Wiki categories seem like a natural and synonymous fit for the typical "tag" functionality for content, like stackoverflow uses. However, we have an external application that will use the wiki API to pull content out for use and will need to work with tags/categories. I'm just wondering before I go down this road if there are any advantages to implementing my own custom tags using semantic properties (the wiki already uses SMW/Forms extensively) or if using wiki categories would be better. Of course, if I forgo categories for semantic properties, then the users will not be able to use the wiki categories pages for browsing articles, but maybe I could create new pages based on semantic queries/concepts to replace them. At this point I have no idea which way to go.
Thanks for your comments/suggestions,
Al
> in my web site, where Mediawiki software is installed, the Chrome
> browser shows a problem:
> the navigation section in left side of the page, the expected result
> should be the navigation section is
>
> just close to the logo on top left, what happens instead is there's a
> empty area on the page between the logo
>
> and the navigation
> section.
What version of MW do you have?
I have seen this in older versions, but when I updated to 1.19, it went away.
:::: Never invest your money in anything that eats or needs painting. -- Billy Rose
:::: Jan Steinman, EcoReality Co-op ::::
hi,
in my web site, where Mediawiki software is installed, the Chrome
browser shows a problem:
the navigation section in left side of the page, the expected result
should be the navigation section is
just close to the logo on top left, what happens instead is there's a
empty area on the page between the logo
and the navigation
section.
Any suggestions are greatly appreciated...
thanks
Pina