MediaWiki-l July 2006

mediawiki-l@lists.wikimedia.org

191 participants
295 discussions

Re: [Mediawiki-l] MediaWiki 1.7.0 and SVG support
by Frederich, Eric P2173 10 Jul '06

10 Jul '06

Good point. Still really sad. Similar to when I get upset when these web sites take all those goofy videos and re-encode them to some other format and put their own logo on them, they wind up getting re-encoded 50 times as they go from site to site. -----Original Message----- From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Rob Church Sent: Monday, July 10, 2006 2:27 PM To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] MediaWiki 1.7.0 and SVG support On 10/07/06, Frederich, Eric P2173 <eric.frederich(a)siemens.com> wrote: > I don't know much about SVG, but why would any external program need to > rasterize an SVG image. I thought that the whole point of SVG was that > it could be scaled very easily and not lose any detail. Lack of browser support for SVG. Rob Church _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

1 0

Re: [Mediawiki-l] MediaWiki 1.7.0 released
by Jimmy Collins 10 Jul '06

10 Jul '06

you recognized: [...] a.. PHP's memory_limit is 16M. If this is too low, installation may fail! Attempting to raise limit to 20M... failed. [...] ? Cheers, Jimmy > -----Ursprüngliche Nachricht----- > Von: MediaWiki announcements and site admin list <mediawiki-l(a)Wikimedia.org> > Gesendet: 08.07.06 15:12:35 > An: "MediaWiki announcements and site admin list" <mediawiki-l(a)Wikimedia.org> > Betreff: Re: [Mediawiki-l] MediaWiki 1.7.0 released > I have been running MediaWiki v1.4.15, and tried upgrading to v1.7 today... > > As I don't have any root access, I relied on the webinstaller. After making > secure backups of everything, I crossed my fingers, uploaded the files, and > pushed ready to go. The install script runs fine, but after pressing > "install", the browser promptly comes up with a new screen and simply hangs > there, nothing happening, page load done. It is not apparent to me, if an > error has occured or something, and this is the intended behaviour? > > No localsettings.php is created - and it doesn't seem like the installer is > actually doing any work. > Can someone explain what is going on? - Or please direct me to a page of > reference? I'm not even sure if this is an error message or if so, what the > error is precisely. > > This is what the screen tells me : > > Warning: set_time_limit() [function.set-time-limit]: Cannot set time limit > in safe mode in > /customers/crewscut.com/crewscut.com/httpd.www/install-utils.inc on line 21 > > a.. PHP 5.1.4 installed > a.. Found database drivers for: MySQL > a.. Warning: PHP's safe mode is active. You may have problems caused by > this, particularly if using image uploads. > a.. PHP server API is cgi-fcgi; using ugly URLs (index.php?title=Page_Title) > a.. Have XML / Latin1-UTF-8 conversion support. > a.. PHP's memory_limit is 16M. If this is too low, installation may fail! > Attempting to raise limit to 20M... failed. > a.. Have zlib support; enabling output compression. > a.. Neither Turck MMCache nor eAccelerator nor APC are installed, can't use > object caching functions > a.. GNU diff3 not found. > a.. Found GD graphics library built-in, image thumbnailing will be enabled > if you enable uploads. > a.. Installation directory: /customers/crewscut.com/crewscut.com/httpd.www > a.. Script URI path: > a.. Environment checked. You can install MediaWiki. > a.. Warning: $wgSecretKey key is insecure, generated with mt_rand(). > Consider changing it manually. > Generating configuration file... > > a.. Database type: MySQL > > Best wishes, > Morten :-) > > -- > Crews Cut Production > Morten Blaabjerg > Danmarksgade 97 - DK-5000 Odense C > Tlf. 65 90 60 88 / 51 80 91 55 > http://morten.crewscut.com > morten(a)crewscut.com > > > ----- Original Message ----- > From: "Brion Vibber" <brion(a)pobox.com> > To: <mediawiki-announce(a)wikimedia.org>; <mediawiki-l(a)wikimedia.org>; > <wikitech-l(a)wikimedia.org> > Sent: Friday, July 07, 2006 10:11 PM > Subject: [Mediawiki-l] MediaWiki 1.7.0 released > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > This is the quarterly release snapshot for Summer 2006. While the code > > has been running on Wikipedia for some time, installation and upgrade > > bits may be less well tested. Bug fix releases may follow in the coming > > days or weeks. > > > > > > MediaWiki is now using a "continuous integration" development model with > > quarterly snapshot releases. The latest development code is always kept > > "ready to run", and in fact runs our own sites on Wikipedia. > > > > Release branches will continue to receive security updates for about a > > year > > from first release, but nonessential bugfixes and feature development > > happen > > on the development trunk and appear in the next quarterly release. > > > > Those wishing to use the latest code instead of a branch release can > > obtain > > it from source control: http://www.mediawiki.org/wiki/Download_from_SVN > > > > > > This is the first version of MediaWiki to require PHP 5. 5.1.x is > > recommended; > > 5.0 may work but is not well tested. (PHP 5.0 is no longer maintained; all > > PHP > > 5.0 users should upgrade to a current 5.1 release to ensure they have all > > security fixes.) PHP 4.x is no longer supported by MediaWiki. If you are > > unable > > to upgrade PHP, sorry, but you will have to stick with old versions of > > MediaWiki > > for now. > > > > > > Full release notes: > > http://svn.wikimedia.org/viewvc/mediawiki/tags/REL1_7_0/phase3/RELEASE-NOTES > > http://svn.wikimedia.org/viewvc/mediawiki/tags/REL1_7_0/phase3/HISTORY > > > > Download: > > http://prdownloads.sourceforge.net/wikipedia/mediawiki-1.7.0.tar.gz > > > > MD5 checksum: > > d3b0ed529ae5ac9dfe713fbdbeae8025 mediawiki-1.7.0.tar.gz > > > > SHA-1 checksum: > > 90c484ad4c2c20023ee1dcbd0eb2904e1a6a1727 mediawiki-1.7.0.tar.gz > > > > > > Before asking for help, try the FAQ: > > http://www.mediawiki.org/wiki/Help:FAQ > > > > Low-traffic release announcements mailing list: > > (Please subscribe to receive announcements of security updates.) > > http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce > > > > Wiki admin help mailing list: > > http://mail.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) > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.4 (Darwin) > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > iD8DBQFErr/xwRnhpk1wk44RAoIoAJ0bj15IFY+Svs0rTnKVbVvZ21kdTgCfYfq2 > > airYE+1H4ga28uhXTSXNL+k= > > =o2qo > > -----END PGP SIGNATURE----- > > _______________________________________________ > > MediaWiki-l mailing list > > MediaWiki-l(a)Wikimedia.org > > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l > > > > > _______________________________________________ > MediaWiki-l mailing list > MediaWiki-l(a)Wikimedia.org > http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

4 6

Purging a cached page
by Green, Chris 10 Jul '06

10 Jul '06

I'm trying to set my wiki purge a cached page. Supposedly you add '&action=purge' to the page url. Whereabouts are the url's kept that I need to add this to ? Thanks All in anticipation Chris This e-mail (and any attachments) may contain privileged and/or confidential information. If you are not the intended recipient please do not disclose, copy, distribute, disseminate or take any action in reliance on it. If you have received this message in error please reply and tell us and then delete it. Should you wish to communicate with us by e-mail we cannot guarantee the security of any data outside our own computer systems. For the protection of Legal & General's systems and staff, incoming emails will be automatically scanned. Any information contained in this message may be subject to applicable terms and conditions and must not be construed as giving investment advice within or outside the United Kingdom. The following companies are subsidiary companies of the Legal & General Group Plc which are authorised and regulated by the Financial Services Authority for advising and arranging the products shown: Legal & General Partnership Services Limited (insurance and mortgages), Legal & General Insurance Limited (insurance), Legal & General Assurance Society Limited (life assurance, pensions and investments), Legal & General Unit Trust Managers Limited and Legal & General Portfolio Management Services Limited (investments). They are registered in England under numbers shown. The registered office is Temple Court, 11 Queen Victoria Street, London EC4N 4TP. Legal & General Partnership Services Limited: 5045000 Legal & General Assurance Society Limited: 166055 Legal & General (Unit Trust Managers) Limited: 1009418 Legal & General (Portfolio Management Services) Limited: 2457525 Legal & General Insurance Limited: 423930 They are registered with the Financial Services Authority under numbers shown. You can check this at www.fsa.gov.uk/register Legal & General Partnership Services Limited: 300792 Legal & General Assurance Society Limited: 117659 Legal & General (Unit Trust Managers) Limited: 119273 Legal & General (Portfolio Management Services) Limited: 146786 Legal & General Insurance Limited: 202050

4 3

Email notifications on all changes for wiki with few outside contributions
by Rick DeNatale 10 Jul '06

10 Jul '06

I run a wiki in which 99% of the changes come from me. Is there a way to set up e-mail notifications of any new pages or changed pages from anyone else? It looks like the Enotify functions which are now part of the mainstream mediawiki distribution only notify on specific pages in the user's watchlist, and can't yet notify of new pages. Am I missing something? -- Rick DeNatale IPMS/USA Region 12 Coordinator http://ipmsr12.denhaven2.com/ Visit the Project Mercury Wiki Site http://www.mercuryspacecraft.com/

2 2

10 Jul '06

Hi! Googled the list archives for this error but couldn't see an obvious reference. A new user to our wiki - http://www.jigsawuk.org - told me that he couldn't add a page: I'm having problems editing the internet page as a registered user, I keep getting this error message when I click 'save': Fatal error: Call to undefined function: memsess_key() in /var/www/ html/includes/User.php on line 1695 When I tried to login myself: 1) I put in the username and password, but found it did not actually result in a login. 2) Now the login page itself just keeps refreshing. And other (but not all) pages refresh about three times before they load fully. One clue is that the main page and pages linked from the left menus all load as usual, but when I click on an internal link from one page to another, the page I'm trying to access keeps refreshing. This page ("Internet") is OK: http://www.jigsawuk.org/index.php?title=Internet But if I click on a link from the Internet page, the page I'm trying to reach is refreshing: http://www.jigsawuk.org/index.php?title=Eventsites Any help would be much appreciated! Regards, Colin ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html

2 1

Pages disappeared after 1.5.8 to 1.6.7 upgrade
by Leon Kolchinsky 10 Jul '06

10 Jul '06

Hello, After upgrade from 1.5.8 to 1.6.7 version, many pages with data disappeared. I did: In the maintenance directory: # php update.php # php refreshLinks.php And now I can see that links from the main menu for: portal sitesupport currentevents Leading to empty pages: "there is no text" in this page How can I fix it? Best Regards, Leon Kolchinsky

2 2

Restricting write access for a custom namespace to a single group
by Isaac Guenard 10 Jul '06

10 Jul '06

Hello I am searching the archives for an answer at the moment, but it’s a pretty long task, so I thought I would post the question while I searched in case anyone had an answer. In http://meta.wikimedia.org/wiki/Preventing_Access there is an excellent section detailing how to restrict read access for a custom namespace to a single group. I am attempting to modify the same approach so that I can restrict edit access instead. The idea is that we intend to operate a public wiki, but a small portion of the content is to be set aside to host the official product documentation. I want this custom namespace to only permit edit access to members of a custom group. At first glance, it seems I need to edit Title.php and modify the userCanEdit() function, but my initial attempts generate some pretty gnarly errors. My PHP skills are VERY novice level, and I have only been using Wikipedia for a week, so I feel a bit like a bull in a fine china shop. Can anyone provide a hint or some pointers? Thanks Isaac Guenard Sr. Product Manager - eyeon Software web : www.eyeonline.com email : izyk(a)eyeonline.com phone : 416 686-8411 x300 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.9/382 - Release Date: 7/4/2006

2 1

during 1.7.0 install, "Specified key was too long; max key length is 1024 bytes"
by Hugh Prior 10 Jul '06

10 Jul '06

I have tried to do a clean install of 1.7.0 and get the following error message: Creating tables... using MySQL 4 table defs...Query "CREATE TABLE `wiki_job` ( job_id int(9) unsigned NOT NULL auto_increment, job_cmd varchar(255) NOT NULL default '', job_namespace int NOT NULL, job_title varchar(255) binary NOT NULL, job_params blob NOT NULL default '', PRIMARY KEY job_id (job_id), KEY (job_cmd, job_namespace, job_title) ) TYPE=InnoDB " failed with error code "Specified key was too long; max key length is 1024 bytes (localhost)". When you do the maths, MySQL does have a point. I remember fighting with a similar key problem on another recentish release. I suppose I could just truncate each of the offered keys like the previous fudge suggested (if I can find it again). Comments? Hugh

1 0

Re: [Mediawiki-l] [Mediawiki-I] Permission to only access certain articles for users?
by Alex Powell 10 Jul '06

10 Jul '06

Hi Rob, I'm not sure I agree that they cannot work. What they cannot do is be supported between versions, and it will be hard to prove robustness. If you patch one version completely, a new one with new holes will soon appear - special pages etc. http://conseil-recherche-innovation.net/index.php/1974/04/11/41-restrict-pa… This lot have done an admirable job of trying to keep up with the MW codeline, but the base codeline seems resistant to the hooks they require to maintain it. Instead they patch diligently each version a few weeks later. Whether this actually patches every possible hole is probably mute. After all early MW versions had XSS vulernabilities (and probably still do as new ones are found). Security is a piece of continuous work, not something that can be done and forgotten about. It is also requires the collaborative approach - by people that understand the code and implications of doing certain things. MW authentication has come on leaps and bounds due to parser hooks, though much is not used by MW itself. It would be nice to see a similar approach adopted for permission hooks. People could report holes, and they could get hooks put in it the relevant places. The MW code does not have too many points where pages can be obtained from the database. Looking thru the patch main area is in the searches and title listing. Unifying and hooking those would go a long way towards creating a robust way to produce an access control extension that was robust for the core and for special pages. As for document management systems, well I think you can be quite smug in the knowledge that your solution is several times better than any commerical products for knowledge gathering and desimination. So I second the call for more hooks - at least enough so that the chaps doing the view restrict patch don't have to fight every release of MW. I also fully accept its not in the direct path of MediaWiki at the moment - but then the wikipedia used to be completely open and editable by anyone ;). Regardless, keep up the good work. I'm sure that time will resolve this problem in some fashion... Best wishes Alex ---------- Forwarded message ---------- From: "Rob Church" <robchur(a)gmail.com> To: "MediaWiki announcements and site admin list" <mediawiki-l(a)wikimedia.org > Date: Sat, 8 Jul 2006 12:02:48 +0100 Subject: Re: [Mediawiki-l] Permission to only access certain articles for users? On 08/07/06, Gregory Szorc <gregory.szorc(a)gmail.com> wrote: > If only the UserCan hook was called more and more. I would love a global > variable like $wgInsanePermissions that, when activated, would have Article > and Title constructors, etc call UserCan for ($wgUser). It wouldn't help, though, because MediaWiki is built around being able to access the content via hundreds of different methods...hence the reason all these hacks don't work 100%. Rob Church

2 1

Re: [Mediawiki-l] [SPAM?]: error after importing database with phpmyadmin
by Vasiliadis, Thomas 10 Jul '06

10 Jul '06

Tschecht Michał Could it be, that your mysql server at home and your online server have different codepages? (latin1_bin vs. latin2_general_ci). Your online and offline Databases have to have the same type of codepages or sth like this can happen. Take care that both are of the same type and try again, TV -----Ursprüngliche Nachricht----- Von: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] Im Auftrag von Michal Gawronski Gesendet: Montag, 5. Juni 2006 21:15 An: mediawiki-l(a)Wikimedia.org Betreff: [SPAM?]: [Mediawiki-l] error after importing database with phpmyadmin Hello. Ive prepared my wikipedia on localmachine - running Windows XP and EasyPHP, when ive copied all files to server, exported database from EasyPHP with phpmyadmin and imported it to server using phpmyadmin too. But now i get this error message when i try to open wiki on server: Error in fetchObject(): Illegal mix of collations (latin1_bin,IMPLICIT) and (latin2_general_ci,COERCIBLE) for operation ' IN ' Backtrace: GlobalFunctions.php line 602 calls wfbacktrace() Database.php line 596 calls wfdebugdiebacktrace() Database.php line 1787 calls databasemysql::fetchobject() LinkBatch.php line 76 calls resultwrapper::fetchobject() LinkBatch.php line 55 calls linkbatch::executeinto() Skin.php line 192 calls linkbatch::execute() Skin.php line 171 calls skinmonobook::preloadexistence() SkinTemplate.php line 108 calls skin::initpage() MonoBook.php line 28 calls skintemplate::initpage() SkinTemplate.php line 151 calls skinmonobook::initpage() OutputPage.php line 577 calls skinmonobook::outputpage() OutputPage.php line 794 calls outputpage::output() Database.php line 476 calls outputpage::databaseerror() Database.php line 419 calls databasemysql::reportqueryerror() Database.php line 806 calls databasemysql::query() Database.php line 825 calls databasemysql::select() Article.php line 391 calls databasemysql::selectrow() Article.php line 403 calls article::pagedata() Wiki.php line 209 calls article::pagedatafromtitle() Wiki.php line 48 calls mediawiki::initializearticle() index.php line 123 calls mediawiki::initialize() Whats going on? Wiki is in poland language. -- Pozdrowienia, Michał Gawroński _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l

1 0

← Newer
1
...
18
19
20
21
22
23
24
...
30
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

MediaWiki-l July 2006