At 04:19 23/10/2014, K. Peachey wrote:
>Is there any reason you can't use the pre-existing install methods?
I need to automate and centralise all this. The need is for thousands
of specialized/private wikis. Installation is just a part of a
comprehensive management.
Thank you.
jefsey
>On 23 October 2014 03:08, JFC Morfin <jefsey(a)jefsey.com> wrote:
>
> > I wish to write a complete script set to install and manage small
> > specialized wikis under SQLite and using the same MediaWiki code. I know
> > how to create the symbolink links. I know how to generate the
> > LocalSettings.php file I want. What I am missing is the script to generate
> > the SQLite database and the Sysops access. Is there somewhere a model I
> > could copy?
> > Thanks to anyone who could help!
> > Jefsey
>
>
> > _______________________________________________
> > MediaWiki-l mailing list
> > To unsubscribe, go to:
> > https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>_______________________________________________
>MediaWiki-l mailing list
>To unsubscribe, go to:
>https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Is there any reason you can't use the pre-existing install methods?
On 23 October 2014 03:08, JFC Morfin <jefsey(a)jefsey.com> wrote:
> I wish to write a complete script set to install and manage small
> specialized wikis under SQLite and using the same MediaWiki code. I know
> how to create the symbolink links. I know how to generate the
> LocalSettings.php file I want. What I am missing is the script to generate
> the SQLite database and the Sysops access. Is there somewhere a model I
> could copy?
> Thanks to anyone who could help!
> Jefsey
>
>
> _______________________________________________
> MediaWiki-l mailing list
> To unsubscribe, go to:
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
I wish to write a complete script set to install and manage small
specialized wikis under SQLite and using the same MediaWiki code. I
know how to create the symbolink links. I know how to generate the
LocalSettings.php file I want. What I am missing is the script to
generate the SQLite database and the Sysops access. Is there
somewhere a model I could copy?
Thanks to anyone who could help!
Jefsey
Hi everybody,
I'm working my way through the update-process and have arrived at the moment
where I'm looking at my own wiki-pages again. <Hurray!!!>
Now I'm trying to eliminate the error-messages mediawiki is throwing at me one
by one, but this one has me baffled:
PHP Warning: preg_replace_callback(): Requires argument 2,
'Sanitizer::cleanUrlCallback', to be a valid callback in
/opt/lampp/htdocs/_fhbwiki/includes/Sanitizer.php on line 1477
This has me baffled because I just cleaned up the cleanUrl-function in order to
clear this error-message:
PHP Deprecated: preg_replace(): The /e modifier is deprecated, use
preg_replace_callback instead in
/opt/lampp/htdocs/_fhbwiki/includes/Sanitizer.php on line 1477
and in order to do that I replaced this line of code:
$url = preg_replace( '/[\][<>"\\x00-\\x20\\x7F]/e', "urlencode('\\0')", $url );
with this line from the master-source-code:
$url = preg_replace_callback( '/[\][<>"\\x00-\\x20\\x7F\|]/',array( __CLASS__,
'cleanUrlCallback' ), $url );
I'm no PHP-programmer but I thought that the master-source-code would be
proof-read at least and not bringing new error-messages with it... :-(
Now I don't know what to do. Google isn't really helpful either.
Can anybody here point me in the right direction?
Kate
The Engineering Community team has opened a new position for a Technical
writer. The right candidate could be subscribed to this list, or they could
be a brave friend of yours.
http://grnh.se/luq7bd
Of you have any questions, just ask me!
----
End forward of Quim's
https://lists.wikimedia.org/pipermail/wikitech-l/2014-October/079050.html
I tend to believe about 95 % of people caring about docs are on
mediawiki-l. :)
Nemo
Hi again,
before I can move my wikis to the new server I need to upgrade them to the
current version (or at least it says so in every how-to I've found so far).
The wiki is currently running under version 1.16.2 and I want to get to 1.23.5
And now I'm encountering the following problems:
Creating user_properties table...Es gab einen Syntaxfehler in der Datenbankabfrage.
Die letzte Datenbankabfrage lautete: âCREATE TABLE `user_properties`(
up_user int not null,
up_property varbinary(32) not null,
up_value blob
) ENGINE=InnoDB, DEFAULT CHARSET=binary
â aus der Funktion â<tt>DatabaseBase::sourceStream</tt>â.
Die Datenbank meldete den Fehler: â<tt>1146: Table '_fhbwiki.user_properties'
doesn't exist (localhost)</tt>â.
Any hints and tipps appreciated.
Kate
Hello everybody,
I've been set the task to merge two existing wikis in a wiki-farm in order to
consolidate the two separate virtual servers the wikis live on at the moment
into one single virtual server.
Now I'm not sure whether this idea is even feasible and if it were, which kind
of wiki-family would be the best way to get the two wikis together...
I've had a look at http://www.mediawiki.org/wiki/Manual:Wiki_family but I have
to admit that I am rather baffled at the different scenarios presented and when
I take a look at the discussions-page I get downright frightend.
I'm not a complete newbie, but I rather need a newbie-proof easy to understand
how-to in order to get a handle on such a project... :-(
So any hints and tips are more than welcome!
Kate
I have it installed and the "version" page shows it installed. However
after restarting apache & updating my system. The toggle button for code
editor is not showing up in the advanced toolbar. Any ideas.
Thanks!
John
I suspect the problem is somewhere in MediaWiki. If knew where I'd be
posting it here.
- I've stripped away other things on the server. Pretty much the only
thing left is the most recent version of MediaWiki (1.23.3) and Debian
(stable) packages.
- I ran 'debsums' to check whether any of the Debian packages are corrupt.
- I am not aware of any LAMP bugs in Debian.
The MediaWiki install is near fresh. I did a manual upgrade for
version 1.23.1 and then used the patches to get to 1.23.3. The
upgrade from 1.23.1 to 1.23.2 had a bug in it-- but I think that was
inconsequential. In any case, that upgrade was done July 30, several
weeks preceding the problems.
Here is a snippet from 'ps aux':
-----
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
...
www-data 10518 0.0 2.8 291376 57052 ? S 20:39 0:03
/usr/sbin/apache2 -k start
www-data 10567 0.0 2.5 288076 51480 ? S 20:42 0:02
/usr/sbin/apache2 -k start
www-data 10568 0.0 2.6 290496 54140 ? S 20:42 0:04
/usr/sbin/apache2 -k start
www-data 10569 0.0 2.5 288820 51840 ? S 20:42 0:02
/usr/sbin/apache2 -k start
www-data 10570 0.0 2.6 291384 53036 ? S 20:42 0:02
/usr/sbin/apache2 -k start
www-data 10571 0.0 2.9 293316 58812 ? S 20:42 0:05
/usr/sbin/apache2 -k start
www-data 10572 0.0 2.7 290976 55360 ? S 20:42 0:04
/usr/sbin/apache2 -k start
www-data 10573 0.0 2.7 290888 55820 ? S 20:42 0:05
/usr/sbin/apache2 -k start
www-data 10649 0.0 2.7 290728 54860 ? S 20:53 0:05
/usr/sbin/apache2 -k start
www-data 10650 0.0 2.7 293000 55924 ? S 20:53 0:04
/usr/sbin/apache2 -k start
...
-----
The memory seems to be going into apache2.
Earlier this morning I rebooted the server. About three hours later the
images were gone again. After rebooting this morning... the server has
been working okay (so far about 13 hours). I don't understand the cycle:
why it breaks in 3 hours... or goes for more than 12.
Some ideas I have:
1. Running a 'diff' of my active server against the tarball for the
most recent MediaWiki-- to look for corrupted files.
2. At this point I am thinking about the extensions and doing a fresh
install of MediaWiki... with the hope that will resolve things.
3. I have bimonthly images going back a year-- I can dump the database,
rollback and grab the latest database changes.
My inclination is to try #2. It isn't that hard to do... if
it works I can be pretty sure it was MediaWiki... and it solves the problem
I have at the moment.
Any thoughts/ideas are welcome.
Michael
MediaWiki 1.25.0 (planned release 2015-05-27) will use the "enhanced
recent changes" and "extended watchlist" options by default. The change
doesn't affect Wikimedia wikis.
Explanation at
https://www.mediawiki.org/wiki/MediaWiki_1.25#Enhanced_recent_changes ;
I'd particularly appreciate help in
* updating docs around (with appropriate {{MW version}}),
* adding a quick gif to show the (un)collapsing of one row on a
representative Special:Watchlist view,
* (ideally) re-writing the Meta-Wiki help page from scratch on
mediawiki.org so that it can be translated.
Nemo
P.s.: I copy the current text from the page here as well.
MediaWiki now uses by default the extended watchlist and so called
enhanced recent chances (preference "Group changes by page in recent
changes and watchlist"), which received several improvements in
MediaWiki 1.25.
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 then 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.