I just started getting this message during my automated backup sessions
of all my mysql data bases. All except my mediawiki are fine.
mysqldump: Got error: 144: Table './mywiki/searchindex' is marked as
crashed and last (automatic?) repair failed when using LOCK TABLES
Any ideas of what to do.
thnaks
John
Hi gang,
Does anyone have any experience with nginx running mediawiki?
I've just migrated my sites from apache2 to nginx -- a WordPress site,
a static site, and a mediawiki site are all running great from their
own URLs.
The problem child is a mediawiki install I have in a subfolder of a
WordPress installation. Trying to get to the mediawiki brings me
right back to the root URL (the WordPress home page).
The directory structure is:
-wordpress site
--subdirectory
---mediawiki install
Or, in other words:
wordpress.site/sub/mediawiki
Everything was running fine before the switch and I *suspect* I need
to set something in an nginx.conf file... but... what?
Any help available will be REALLY appreciated.
Thanks!
--
Matthew Wayne Selznick
Author, Creator and Creative Services Provider
http://www.mattselznick.com
Get a Free Sampler of My Short Stories, Novels, and Non-Fiction:
http://www.mattselznick.com/free-ebook
Como puedo pedir permiso de copia hay en wiksource me dicce que tengo que
llenar el formato que me dan de ejemplo pero no veo en donde tengo que
enviar ese formato por favor espero su pronta respuesta Gracias...
Hello,
I am extremely new to MediaWiki and have set up an internal server for my
team. I would like to have a set of pages on one topic for starters but
with the ability to continue to add topics as we decide whether we like
leveraging this as a knowledge base.
Can I set something up like this?
www.mywiki.internal/wiki/index.php/TOPIC1 <- page showing all the pages
under TOPIC1 sorted by date
www.mywiki.internal/wiki/index.php/TOPIC1/STUFF1 <- a page tied to a
template with sections defined.
Any page under TOPIC1 would start with a template of sections: Executive
Summary, Details, NextSection, etc.
Can anyone help me understand how to set this up in this manner (and if its
possible to do so)?
Thank you for your help.
Kevin
I have been trying for 2 weeks to figure out how to get Mediawiki 1.22.5
to properly handle images: still no real progress; Here is the message
I'm getting now. I think these are all related to some permissions
issue, but I have tried everything I know of & I have researched the web
extensively & tried many 'possible' solutions. Here is the situation:
/var/www/ is owned by root:root permissions 0755
/var/www/mywiki is owned by myusername:myusername permissions 0755
/var/www/mywiki/images is owned by myusername:myusername permissions
0777
I am currently running this on Debian linux stable; when I load up a
webpage I get a mixed array of images issues: as in some images load and
display and others don't.
error message from web page:
> Error creating thumbnail: convert.im6: no decode delegate for this
> image format `/tmp/magick-3PI8Zdf7' @
> error/constitute.c/ReadImage/544.
> convert.im6: no images defined
> `/var/www/mywiki/images/tmp/transform_4a98a4281d46-1.png' @
> error/convert.c/ConvertImageCommand/3044.
error message from Apache2 error.log:
[Mon Apr 21 20:19:39 2014] [crit] [client 127.0.0.1] (13)Permission denied: /var/www/mywiki/images/thumb/2/2e/Engineered_monoclonal_antibodies.svg/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.physicswiki.net/index.php?title=Bispecific_monoclonal_antibody
[Mon Apr 21 20:19:39 2014] [crit] [client 127.0.0.1] (13)Permission denied: /var/www/mywiki/images/thumb/2/2e/Engineered_monoclonal_antibodies.svg/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.physicswiki.net/index.php?title=Bispecific_monoclonal_antibody
[Mon Apr 21 20:19:39 2014] [crit] [client 127.0.0.1] (13)Permission denied: /var/www/mywiki/images/thumb/2/2e/Engineered_monoclonal_antibodies.svg/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.physicswiki.net/index.php?title=Bispecific_monoclonal_antibody
[Mon Apr 21 20:19:39 2014] [crit] [client 127.0.0.1] (13)Permission denied: /var/www/mywiki/images/thumb/2/2e/Engineered_monoclonal_antibodies.svg/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.physicswiki.net/index.php?title=Bispecific_monoclonal_antibody
the .htaccess file mentioned has this content; & is permission 0777
> # Protect against bug 28235
> <IfModule rewrite_module>
> RewriteEngine On
> RewriteCond %{QUERY_STRING} \.[^\\/:*?\x22<>|%]+(#|\?|$) [nocase]
> RewriteRule . - [forbidden]
> </IfModule>
>
The file in question is on wikimedia commons & I have InstantCommons = true;
in my LocalSettings.php file
thanks
john
For a current project, I have found that Auth_remoteuser can take care
of a lot of the grunt work, but I felt the need to update it a little.
I have the feeling (wrong?) that this extension is one that is used in a
lot of places but it hasn't been touched for a couple of years.
Could I get people to test out the modifications I want to contribute back?
https://gerrit.wikimedia.org/r/127405 -- mostly just formatting
https://gerrit.wikimedia.org/r/127406 -- refactoring
https://gerrit.wikimedia.org/r/127407 -- changing invocation
I've made some effort to keep this compatible with the previous version.
If you want to try this out as a drop-in replacement for your current
Auth_remoteuser, you can use
http://mah.everybody.org/Auth_remoteuser.php.txt -- but please report
back any problems you have.
Thanks,
Mark.
--
Mark A. Hershberger
NicheWork LLC
717-271-1084
> From: "Scheid, Bernhard" <Bernhard.Scheid(a)oeaw.ac.at>
>
> For unknown reasons, google sometimes refers to my wiki-pages by using https instead of http. The result is that the page is displayed, but without css. Any advice how to prevent this?
I doubt Google is making this up.
That means that there are links out there that refer to your site with https. Hunt them down and kill them.
Otherwise, if you have control of your server, you can simply enable https as well as http. It isn't terribly difficult.
:::: I suggest you locate your hot tub outside your house, so it won't do too much damage if it catches fire or explodes. First you decide which direction your hot tub should face for maximum solar energy. After much trial and error, I have found that the best direction for a hot tub to face is up. -- Dave Barry
:::: Jan Steinman, EcoReality Co-op ::::
I have a number of persistant issues with Mediawiki 1.22.4.
These have persisted since I upgraded from 1.22.2 a few weeks ago.
I "THINK" these are all related to some kind of permissions issues with
the server. these are a section of the relevant lines from
LocalSettings.php
<?php
# Protect against web entry
if ( !defined( 'MEDIAWIKI' ) ) {
exit;
}
## Uncomment this to disable output compression
# $wgDisableOutputCompression = true;snipet
$wgSitename = "PhysicsWiki";
## The URL base path to the directory containing the wiki;
## defaults for all runtime URL paths are based off of this.
## For more information on customizing the URLs
## (like /w/index.php/Page_title to /wiki/Page_title) please see:
## http://www.mediawiki.org/wiki/Manual:Short_URL
$wgScriptPath = "";
$wgScriptExtension = ".php";
## The protocol and server name to use in fully-qualified URLs
$wgServer = "http://www.physicswiki.net";
$wgCanonicalServer = 'http://www.physicswiki.net';
## The relative URL path to the skins directory
$wgStylePath = "$wgScriptPath/skins";
## UPO means: this is also a user preference option
$wgEnableEmail = true;
$wgEnableUserEmail = true; # UPOsnipet
$wgEmergencyContact = "frosty(a)physicswiki.net";
$wgPasswordSender = "frosty(a)physicswiki.net";
$wgEnotifUserTalk = true; # UPO
$wgEnotifWatchlist = true; # UPO
$wgEmailAuthentication = true;
## Database settings
$wgDBtype = "mysql";
$wgDBserver = "localhost";
$wgDBname = "pw";
$wgDBuser = "myusername";
$wgDBpassword = "mypassword";
# MySQL specific settings
$wgDBprefix = "";
# MySQL table options to use during installation or update
$wgDBTableOptions = "ENGINE=InnoDB, DEFAULT CHARSET=binary";
# Experimental charset support for MySQL 5.0.
$wgDBmysql5 = false;
## To enable image uploads, make sure the 'images' directory
## is writable, then set this to true:
$wgEnableUploads = true;
$wgUseImageMagick = true;
$wgUseImageResize = true;
$wgImageMagickConvertCommand = "/usr/bin/convert";
require_once( "$IP/extensions/NativeSvgHandler/NativeSvgHandler.php" );
$wgSVGConverter = 'ImageMagick';
$wgSVGConverterPath = "/usr/bin/";
snipet
$wgSVGConverters = array(
'ImageMagick' => '$path/convert -background white -thumbnail $widthx
$height\! $input PNG:$output',
# 'inkscape' => '$path/inkscape -z -w $width -f $input -e $output',
# 'rsvg' => '$path/rsvg -w $width -h $height $input $output',
$wgTmpDirectory = "$IP/images/temp";
$wgUploadPath = "$wgScriptPath/images";
$wgUploadDirectory = "$IP/images";
# InstantCommons allows wiki to use images from
http://commons.wikimedia.org
$wgUseInstantCommons = true;
## If you use ImageMagick (or any other shell command) on asnipet
## Linux server, this will need to be set to the name of an
## available UTF-8 locale
$wgShellLocale = "en_US.utf8";
## If you want to use image uploads under safe mode,
## create the directories images/archive, images/thumb and
## images/temp, and make them all writable. Then uncomment
## this, if it's not already uncommented:
#$wgHashedUploadDirectory = false;
## Set $wgCacheDirectory to a writable directory on the web server
## to make your wiki go slightly faster. The directory should not
## be publically accessible from the web.
$wgCacheDirectory = "$IP/cache";
Any one interested. Please look over these settings & send any ideas for
correcting them to something that works with all images. The issues
seems to also affect $wgInstantCommons usage as well.
Real path to the wiki is /var/www/pw
I have set the /var/www/pw/images directory and all its recursives to
mode 777 just as a temporary situation; I think that they should be set
to 0775 or 0755.
Entire site is owned by "myusername" not www-data or root
Thanks for any assist.
john
> Import the dump into MySQL if you haven't already.
Ok, something like this (?):
mysql -u root -p WIKIdb < dump-of-old-WIKIdb.sql
> Tweak your mysql config to point to the database with the dump.
How, where? Sorry, I am a complete noob.
Thanks for your help
Matthias
----
Matthias Brennwald
Eawag, CH-8600 Dübendorf
Office Eawag BU-D13: +41 58 765 53 05
Lab Eawag LA-C76: +41 58 765 53 06
Lab ETHZ CLA A31.6: +41 44 632 09 36/39
matthias.brennwald(a)eawag.ch
http://homepages.eawag.ch/~brennmat