Upgrading work wikis from 1.19 to 1.23 with slight trepidation. It
went like this:
* Back up htdocs and database, unzip tarball into place
* php maintenance/update.php
* and you're done.
My goodness that was simple. Thank you for something that Just Works that well!
- d.
I am trying, actually it seems to be working, to import a large site
dump into a new Mediawiki 1.25.1 site. The error below is showing up and
I'm wondering if this is a bug, since this is a new version of mediawiki.
PHP Notice: Undefined offset: 1 in
/var/www/includes/title/NamespaceAwareForeignTitleFactory.php on line 127
--
John Foster
JW Foster & Associates
Dear users, developers and all people interested in semantic wikis,
We are happy to announce SMWCon Fall 2015 - the 12th Semantic MediaWiki
Conference:
* Dates: October 28th to October 30th 2015 (Wednesday to Friday)
* Location: Fabra i Coats, Art Factory. Carrer Sant Adrià 20 (Sant
Andreu), Barcelona.
* Conference wikipage:
https://semantic-mediawiki.org/wiki/SMWCon_Fall_2015
* Participants: Everybody interested in semantic wikis, especially in
Semantic MediaWiki, e.g., users, developers, consultants, business
representatives, researchers.
SMWCon Fall 2015 will be supported by Institut de Cultura de Barcelona
(http://lameva.barcelona.cat/barcelonacultura/en/), Amical Wikimedia
(https://www.wikimedia.cat) and Open Semantic Data Association e. V.
(https://opensemanticdata.org/).
Following the success of this format the SMWCon will have one tutorial
day preceeding two conference days.
Participating in the conference: To help us planning, you can already
informally register on the wikipage, although a firm registration will
later be needed.
Contributing to the conference: If you want to present your work in the
conference please go to the conference wikipage and add your talk there.
To create an attractive program for the conference, we will later ask
you to give further information about your proposals. Tutorials and
presentations will be video and audio recorded and will be made
available for others after the conference.
Among others, we encourage contributions on the following topics:
Applications of semantic wikis:
* Semantic wikis for enterprise workflows and business intelligence
* Semantic wikis for corporate or personal knowledge management
* Exchange on business models with semantic wikis
* Lessons learned (best/worst practices) from using semantic wikis or
their extensions
* Semantic wikis in e-science, e-learning, e-health, e-government
* Semantic wikis for finding a common vocabulary among a group of people
* Semantic wikis for teaching students about the Semantic Web
* Offering incentives for users of semantic wikis
* Challenges and obstacles for Semantic Wikis in business environments
Development of semantic wikis:
* Semantic wikis as knowledge base backends / data integration platforms
* Comparisons of semantic wiki concepts and technologies
* Community building, feature wishlists, roadmapping of Semantic MediaWiki
* Improving user experience in a semantic wiki
* Speeding up semantic wikis
* Integrations and interoperability of semantic wikis with other
applications and mashups
* Modeling of complex domains in semantic wikis, using rules, formulas
etc.
* Access control and security aspects in semantic wikis
* Multilingual semantic wikis
For any other question and sponsorship opportunities, please do not
hesitate to contact Toni Hermoso <toniher at cau.cat>
Hope to see you in Barcelona!
Lia Veja, Karsten Hoffmeyer
(Program Board
I need to move a mediawiki site from a drive on my server that is
running Linux Mint LMDE flavor: to a drive on that same sever that is
running Ubuntu Enterprise server. Both are latest versions. I exported
the database (MySqlDump) and have it "backed Up" as well from Webmin.
No issues there as I got the exact same size file after exporting it 2
times, 4.1Gb. I tried to do a standard upgrade after installing the new
mediawiki 1.24.2 to the ubuntu server. i.e. following the instructions
from mediawiki. it said I was successful, but I was never able to get
the site to open, just a blank page. i tried stripping down the site and
removing most of the extensions so that is not the issue. I finally
decide the installl was somehow corrupted and put up a brand new site
from scratch and it is running fine. So I tried using the imported data
base by simply changing the name of the datsbase in LocalSettings.php.
that seems to have worked sort of, but the graphics and several main
page links are missing.
So here is my question. How can I fix this. Any tips or ideas are
greatly appreciated.
Thanks!
--
John Foster
JW Foster & Associates
Hi all,
I'm just looking at upgrading to MW 1.25.1 but I'm getting an error
when running update.php for the ConfirmEdit extension, run in ReCaptcha
mode:
PHP Warning: require_once(ReCaptcha/recaptchalib.php): failed to open
stream: No such file or directory
in /srv/web/.../mediawiki-1.25.1/extensions/ConfirmEdit/includes/ConfirmEditHooks.php
on line 147
PHP Fatal error: require_once(): Failed opening required
'ReCaptcha/recaptchalib.php' (include_path='.:/usr/share/php:/usr/share/pear')
in /srv/web/.../mediawiki-1.25.1/extensions/ConfirmEdit/includes/ConfirmEditHooks.php
on line 147
Line 147 in ConfirmEditHooks.php is the require_once line in this
function:
/**
* Callback for extension.json of ReCaptcha to require the recaptcha library php file.
* FIXME: This should be done in a better way, e.g. only load the libraray, if really needed.
*/
public static function onReCaptchaSetup() {
require_once( "ReCaptcha/recaptchalib.php" );
}
Which looks like an include path problem. Is this a bug in the new
ConfirmEdit or is there some other option I need to set when
upgrading from 1.24.1 to 1.25.1?
I'm loading the extension from my old LocalSettings.php like this:
require_once("${IP}/extensions/ConfirmEdit/ReCaptcha.php");
$wgCaptchaClass = 'ReCaptcha';
$wgReCaptchaPublicKey = 'xxx';
$wgReCaptchaPrivateKey = 'xxx';
Many thanks,
Adam.
Hi,
With the release of MediaWiki 1.25, the lifetime of MediaWiki version 1.19.x
LTS ends.
Users still using MediaWiki 1.19.x are advised to upgrade to version 1.25.0
(latest stable) or 1.23.x (legacy and LTS version).
-Chad Horohoe, MW Release Manager
_______________________________________________
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Hello everyone,
I am happy to announce the availability of the first stable release of the
new MediaWiki 1.25 series.
MediaWiki 1.25 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.25 file for the full list of changes in this
version.
Our thanks to everyone who helped to improve MediaWiki by testing the
release candidates and submitting bug reports.
== What's new for users? ==
MediaWiki 1.25 includes all changes released in the smaller 1.25wmf*
software deployments to Wikimedia sites over six months, totaling
approximately 2200 changes.
* Indicators – Templates that add icons to the top right corner of the page
(and more) can be updated to use the new page status indicators feature.
* Enhanced recent changes – MediaWiki now uses by default the extended
watchlist and so called enhanced recent changes (preference "Group changes
by page in recent changes and watchlist"), which also received several
improvements in MediaWiki 1.24 and 1.25 (task 37785). This means that
Special:RecentChanges and Special:Watchlist show all the changes to each
page in a given day, sorted by page rather than chronologically. Changes to
each page are collapsed by default and a compact overview is shown, with
links to collated diffs and counts of each user's actions. Full activity
for an individual page can then be shown with a single click. Users will no
longer need to know in detail how a single change was chosen for display in
order to figure out what else may have happened to the page that day, nor
to scan a long list of non-contiguous lines on the screen in order to get a
complete picture. The change is part of MediaWiki's evolution towards an
interface which is more discoverable and less cluttered by default, while
equally easy to quickly access in full, with the help of JavaScript.
However, the (grouped) layout is an improvement for non-JavaScript users as
well.
* Live preview – While editing, you're not sure what a wikitext syntax will
produce? That's no longer a problem, now that live preview is no longer
experimental. By enabling the feature in your preferences, MediaWiki will
display the effect of your edits without fully reloading the page, so that
you can quickly correct any mistake.
* Import – The import tool is now much easier to use on content from a wiki
which has different namespaces than yours (e.g. because it's in another
language).
* Internationalization – In logging and gender support, continuing the work
in MediaWiki 1.18 and 1.19, multiple log types of Special:Log have been
migrated to the new logging system, which allows full internationalization
including word order and grammatical gender. The migration continues. See
task T26620 for a list.
Locales – The following locales have been added: अवधी, بلوچی رخشانی and
Koyraboro Senni.
* API documentation is localized and easier to access through
Special:ApiHelp.
== What's new for system administrators? ==
* PHP 5.3.3 is now required (from 5.3.2)
* Extensions and skins are now loaded through a new registration system
* Profiling was completely overhauled to use the xhprof module.
Full release notes:
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_25/RELEASE-NOTES…https://www.mediawiki.org/wiki/Release_notes/1.25
**********************************************************************
Download:
http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0.tar.gzhttp://download.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0.tar.gz
GPG signatures:
http://download.wikimedia.org/mediawiki/1.25/mediawiki-core-1.25.0.tar.gz.s…http://download.wikimedia.org/mediawiki/1.25/mediawiki-1.25.0.tar.gz.sig
Public keys:
https://www.mediawiki.org/keys/keys.html
-Chad Horohoe, MW Release Manager
_______________________________________________
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
I have a number of related questions regarding MediaWiki's caching
mechanism. I would be grateful if one could answer these please. The
assumption here is that a wiki is configured using the exact same caching
methods that Wikimedia uses.
Please feel free to provide links to https://www.mediawiki.org as well as
https://noc.wikimedia.org when specifying configuration variables in your
answers as I am sure this would benefit future readers of this thread as
well.
Q1: Page [[foo]] contains template {{bar}}. I edit that template, but the
page is not immediately updated. If I don't manually purge the cache of
that page, how long would it take for the page cache to be updated? Which
variable sets that time? And what is the value of that variable currently
at Wikimedia wikis?
Q2: Page [[foo]] contains template {{bar}}, and that template provides a
link to page [[norf]]. I edit the template such that it instead links to
page [[qux]]. However, when I go to Special:WhatLinksHere/norf I still see
[[foo]] listed. Even if I try ?action=purge on [[foo]], that behavior
doesn't change. The only way to change it is either to edit [[foo]] and
change its content, or to simply go to the edit page of [[foo]] and save
without changes.
Q2.A: If I don't do that null edit, how long would it take for the page
cache to be updated? Which variable sets that time? And what is the value
of that variable currently at Wikimedia wikis?
Q2.B: Why is it that ?action=purge doesn't update the pagelinks table?
Q2.C: Why is it that saving a page without any edits triggers any update
mechanism? (I would assume it'd be less costly overall to say "if diff is
null, don't do anything at all"; this question is more philosophical: why
would we not like the quoted behavior?
Q2.D: Does the Special:WhatLinksHere results come from a cache? In other
words, if I query the database directly right after I change the template
(as mentioned in Q2) but before I do any null edits, would it still show
the old page link from [[foo]] to [[norf]]? Or would it show the correct
link from [[foo]] to [[qux]] while Special:WhatLinksHere is still showing
the old link?
Q2.E: Is it possible to induce the same "resolution" through API? That is,
is it possible to try to save a page without any changes to its content via
API, and thereby forcefully update the page links entries for that page?
Q3: Assume that 100 pages contain template {{bar}}, and that template
provides a link to page [[norf]]. I edit the template such that it instead
links to page [[qux]]. Would that add any jobs to the job queue? If yes,
how many? Should I expect 100 new jobs to be added, because 100 page
cache's need updating?
Thanks in advance,
Huji