Hello,
> Special:Sidebar should do the trick though; what exactly doesn't work?
Sorry, my bad; it's MediaWiki:Sidebar...
Thanks. I could not access the page MediaWiki:Sidebar, even when I searched for it.
It only asked me if I wanted to create the page.
Now if I create a new page, wouldn't my new configuration affect the former configuration?
Ime
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
February 20, 2007
MediaWiki 1.9.3 is a security and bug-fix update to the Winter 2007
quarterly release. Minor compatibility fixes for IIS and PostgreSQL are
included.
An XSS injection vulnerability based on Microsoft Internet Explorer's
UTF-7 charset autodetection was located in the AJAX support module,
affecting MSIE users on MediaWiki 1.6.x and up when the optional setting
$wgUseAjax is enabled.
If you are using an extension based on the optional Ajax module,
either disable it or upgrade to a version containing the fix:
* 1.9: fixed in 1.9.3
* 1.8: fixed in 1.8.4
* 1.7: fixed in 1.7.3
* 1.6: fixed in 1.6.10
There is no known danger in the default configuration, with $wgUseAjax off.
* (bug 8992) Fix a remaining raw use of REQUEST_URI in history
* (bug 8984) Fix a database error in Special:Recentchangeslinked
when using the PostgreSQL database.
* Add 'charset' to Content-Type headers on various HTTP error responses
to forestall additional UTF-7-autodetect XSS issues. PHP sends only
'text/html' by default when the script didn't specify more details,
which some inconsiderate browsers consider a license to autodetect
the deadly, hard-to-escape UTF-7.
This fixes an issue with the Ajax interface error message on MSIE
when $wgUseAjax is enabled (not default configuration); this UTF-7
variant on a previously fixed attack vector was discovered by Moshe BA
from BugSec: http://www.bugsec.com/articles.php?Security=24
* Trackback responses now specify XML content type
Full release notes:
http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_9_3/phase3/RELEASE-NOT…
Download:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.3.tar.gz
Patch against 1.9.2:
http://download.wikimedia.org/mediawiki/1.9/mediawiki-1.9.3.patch
Downloads, checksums, and GPG signatures for all versions:
http://download.wikimedia.org/mediawiki/1.9/http://download.wikimedia.org/mediawiki/1.8/http://download.wikimedia.org/mediawiki/1.7/http://download.wikimedia.org/mediawiki/1.6/
Before asking for help, try the FAQ:
http://www.mediawiki.org/wiki/Manual:FAQ
Low-traffic release announcements mailing list:
(Please subscribe to receive announcements of security updates.)
http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
Wiki admin help mailing list:
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Bug report system:
http://bugzilla.wikimedia.org/
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF27NDwRnhpk1wk44RAhmmAKCVZNGTidpNmCJUwUs5JA1CIJL3OwCfUsxy
uny25mn0vihjgNoDxl2ZDiw=
=bvTp
-----END PGP SIGNATURE-----
Hi all,
I'm a long-time user of MediaWiki software, and recently ventured into
writing extensions and code modifications. I noticed when perusing the
code files that there are a number of debugging messages scattered
throughout with phrases calling wfDebug. It appears that these messages
are turned off in the production releases of MediaWiki.
Can anyone tell me where the "switch" resides that will turn on these
messages? I have three versions of MediaWiki installed on a development
machine and would like to turn these on when developing extensions to
make sure there are no conflicts, especially since I'm using some
"include" statements that pull MediaWiki base code files into some of
the extension so I can access the functions in those files.
I have error messages enabled in both MySQL and PHP for my development
computer.
Any assistance here would be greatly appreciated.
Thanks!
Lisa
It seems as if the Blahtex package is no longer being developed.
Is anyone working on MathML support at this point?
--
Daniel M. Israel
dmi1(a)cornell.edu
> From: Paul Coghlan <pcoghlan(a)usa.net>
>
> I am building a large Mediwiki site which will consist of about 40k
> pages,
> all related through location.
>
> The pages are structured/related and I have the source for the wiki
> 'skeleton' or schema and can massage it in Access/Excel/MySQL into any
> required format for an import into Mediawiki.
>
> For example:
>
> Florida
> +Miami
> ++South Beach
> +++Restaurants
> ++++MyRestaurant
> +++Bars
> ++++MyBar
> +++Shopping
> ++++MyShop
> ++North Miami
> +Fort Lauderdale
> +Palm Beach
> Georgia
> +Atlanta
>
> I think you get the idea!
Keep in mind that wikis are non-hierarchical. You can impose a
hierarchy on them via content links, but if the structure you want to
import *assumes* anything hierarchical, you'll have trouble.
It's also a bit confusing that you refer to "a large Mediawiki site"
in one place, and elsewhere to "each wiki." I think you mean "each
page" in the latter case, but if you are really wanting to generate a
number of wiki sites, then it's a different problem. ("Wiki"
generally refers to a site, not a page on that site.)
In the first case, I agree with Kasimir to dump the database to one
plain text file per page, then do a text import. But that will
probably lose the hierarchy information, unless you create it in the
output text. So with a little coding, you could generate a
"breadcrumbs" style hierarchy navigator for each page that would
preserve the hierarchy information on import.
For example, the page for "MyRestaurant" could include the text
"[[Florida]] --> [[Miami]] --> [[South Beach]] --> [[Restaurants]]"
at the top of the page. But this sort of imposed hierarchy may be
difficult to maintain, if you plan to move things often.
:::: I dread success. To have succeeded is to have finished one's
business on earth, like the male spider, who is killed by the female
the moment he has succeeded in his courtship. I like a state of
continual becoming, with a goal in front and not behind. -- George
Bernard Shaw ::::
:::: Jan Steinman http://www.EcoReality.org ::::
The project Word2MediaWikiPlus (Microsoft Word converter) is coming
back from the ashes...
Version 0.7.0.10 has been re-released.
I'm still looking for someone that has version 0.7.0.11.
Version 1.0.0-Beta1 is also available for testing.
http://www.mediawiki.org/wiki/Extension:Word2MediaWikiPlus
I thought that transparency in PNG's wasn't supported in Internet
Explorer yet the logo in the upper left of every page appears to be
transparent letting that grey background through.
How is this happening?
Can the same method work with other PNGs placed inside pages?
~Eric
Dear all,
I'm currently using:
MediaWiki: 1.8.2
PHP: 5.0.5 (apache2handler)
MySQL: 5.0.18-nt* Hooks:
AutoAuthenticate: AutoAuth
PersonalUrls: KillLogout
I'm unable to edit pages in my Wiki. I always get the error message:
"This is only a preview; changes have not yet been saved!".
The page does not get saved.
I have tried out the following:
PHP Session path: I changed the session path to the correct one in the php.ini!
Group permissions: I changed the group permissions in the localsettings.php as
follows
$wgGroupPermissions['*']['edit']=false;
$wgGroupPermissions['user']['edit']=true;
$wgGroupPermissions['user']['createpage']=true;
So I don't know what else to check or to change...
Further on I cleared the browser cache...
I would appreciate any help or suggestions.
Regards,
Jens
Hello
I am working with a very new installation of Mediawiki. It was installed
by following the instructions on:
http://meta.wikimedia.org/wiki/Help:Running_MediaWiki_on_Debian_GNU/Linux
with the following versions:
- Debian “etch”
- Apache 2.2.3
- MySQL 5.0.30
- php 5.2.0
- Mediawiki 1.9.1
One of the first admin tasks I was required to do was reset a user
password. I followed:
http://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_reset_a_password.3F
I ended up using the SQL query method rather than the maintenance script.
Running changePassword.php in the Maintenance directory displays the error:
"A copy of your installation's LocalSettings.php
must exist in the source directory."
Running changePassword.php in the source directory displays the error:
"Could not open input file: maintenance/changePassword.php"
Thinking that it may be a permissions or ownership issue, I checked the
files and directories in the source directory (/var/www/wiki). They are
all owned by user and group '501', except for LocalSettings.php, which
is 'www-data'.
I changed all (except LocalSettings.php) file and directory ownership to
root. I was then able to run the script successfully.
Please can you let me know, or point me to documentation about the
appropriate ownership and permissions of the files and directories in
the source directory. Note: The source directory is also owned by user
and group '501'.
I have searched this archive, mediawiki.org, and www but have not been
able to find a definitive answer.
Regards
Jacqueline