Hi All,
I've installed Extension:Collection on mw 1.15 from svn and I've not changed
any of the defaults - in particular, I'm using the default rendering
server. My collections seem to render (and are viewable on pediapress).
However I cannot download them; when I click the download link, it used to
download a zero byte pdf. Now, after updating svn to head, I just get a
blank page.
I saw some discussion of this problem on the extensions discussion page.
However, the suggested fixes were old, suggested a couple of different
possible problems, and none are confirmed as actual fixes. I'm hoping
someone on this list may have had a similar experience and would be willing
to share their solution.
Thanks,
Jason
I apologize for coming to this list for help out of the blue, but I've
run out of other resources to check.
I'm trying to move the contents of an existing MW installation,
v.1.10.0, to a new version of MW on a different server. I don't get a
choice about what version is put on the new server (ISP canned install),
so it's 1.15.4. It's already installed there, tables/wiki user created
in MySQL, etc. The wiki DB user has a different name on the two systems,
and on the new system the tables have a mw_ prefix. Again, I didn't get
a choice in this matter.
Now, my SQL is very good - it's what I do all day - and I'm perfectly
willing to try to export the contents of the old wiki as SQL/DDL,
search/replace/alter those as needed, and import them into the new
database. But I gather this is a bad, messy idea. Even if the columns in
the 34 tables from 1.10 haven't changed, there's the question of the
seven tables which have been added to the schema since then. Nor can I
find any good version-by-version docs on how the schema has changed over
time.
There's also the possibility of exporting and importing by some means
other than altering the database directly - e.g. Special:Export - but
that seems to not be a viable "export entire wiki in bulk" option.
I don't absolutely need to export revision history and I don't care if
details of page ownership etc are lost. If I can just grab latest
version of each page, even if they are all marked as owned by WikiSysop,
that's fine. I can remake template inclusions and other niceties by hand
- there aren't many. It's just the 500+ pages of actual body content
that are the problem.
Can anybody give advice on this?
Todd Belton
Harvard Graduate School of Design
Use the XML export/import scripts in maintenance/. You'll need to create an AdminSettings.php config file on both hosts to allow this to happen. Have a look on the mediawiki wiki for the details. You can do single page or full history exports as you prefer.
Russell
----- Original Message -----
From: mediawiki-l-bounces(a)lists.wikimedia.org <mediawiki-l-bounces(a)lists.wikimedia.org>
To: mediawiki-l(a)lists.wikimedia.org <mediawiki-l(a)lists.wikimedia.org>
Sent: Thu Jul 22 17:38:15 2010
Subject: [Mediawiki-l] Moving entire wiki 1.10.0 -> 1.15.4
I apologize for coming to this list for help out of the blue, but I've
run out of other resources to check.
I'm trying to move the contents of an existing MW installation,
v.1.10.0, to a new version of MW on a different server. I don't get a
choice about what version is put on the new server (ISP canned install),
so it's 1.15.4. It's already installed there, tables/wiki user created
in MySQL, etc. The wiki DB user has a different name on the two systems,
and on the new system the tables have a mw_ prefix. Again, I didn't get
a choice in this matter.
Now, my SQL is very good - it's what I do all day - and I'm perfectly
willing to try to export the contents of the old wiki as SQL/DDL,
search/replace/alter those as needed, and import them into the new
database. But I gather this is a bad, messy idea. Even if the columns in
the 34 tables from 1.10 haven't changed, there's the question of the
seven tables which have been added to the schema since then. Nor can I
find any good version-by-version docs on how the schema has changed over
time.
There's also the possibility of exporting and importing by some means
other than altering the database directly - e.g. Special:Export - but
that seems to not be a viable "export entire wiki in bulk" option.
I don't absolutely need to export revision history and I don't care if
details of page ownership etc are lost. If I can just grab latest
version of each page, even if they are all marked as owned by WikiSysop,
that's fine. I can remake template inclusions and other niceties by hand
- there aren't many. It's just the 500+ pages of actual body content
that are the problem.
Can anybody give advice on this?
Todd Belton
Harvard Graduate School of Design
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
Hi,
Currently, every time we sign with a new client, we create 3 or 4 pages
that all use more or less the same info for different purposes (client
name and some info).
Is there any way to create all the pages in a "single creation", maybe
by using a page substitution or something like that?
Using an external program to script the creation process isn't really a
good solution in our context.
--
Gabriel Filion
I want an email when a particular page is edited on an intranet wiki I
just set up. Enotif is apparently (largely) part of MW these days, but
I can't find how to switch it on.
The wiki is MW 1.15.4 with SMW installed via Semantic Bundle (the only
sensible way to set up SMW). It has a pile of interesting extensions,
but the core isn't hacked about.
Is this actually included in the MW tarball or do I have to add something else?
- d.
Hi,
is there a way to manipulate wiki-headers and sub-headers in a way that only parts of it are shown in the TOC? I.e.,something like
==Important message<hide from TOC>less important message</ >==
or so?
thx
Bernhard
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
Hello,
we trying at the moment the executability of Mediawiki on an Oracle
database. I know, that it isnt really good supported, but may you can give
some ways that may helping us to make the system go on that database. We
have the newest Mediawiki-version and an Oracle-Database already. But i need
to know the steps to go on with installing the Wiki on that database. May
someone can help.
thanks
--
View this message in context: http://old.nabble.com/Newest-Mediawiki-on-Oracle-tp29228960p29228960.html
Sent from the WikiMedia General mailing list archive at Nabble.com.
ansorri Iam not spikin inglish. no comprendo todos los mail recibidos. Yo solo soy, un ser preocupado por lo que vio. sin poder y con miedo. Amo a mi familia y a mi mundo.Por momentos tomo coraje y trato de hacer publico, lo que vi. Despues razono y me arrepiento. Cuando evaluo que puede pasar. Solo me queda problemas y preocupaciones. Asi creyeran en mi. igual seria malo, por las concecuencias que trae,el comportamiento humano es egoista. y la especulacion, haria mas daño que el echo real, en si.
Me contacte con ustedes,para sacar mi incertidumbre.y saber si hay alguien mas, que se atreva a declarar como testigo de avistamiento de estos monstruos.y a futuro cuando, esto sea mas creible. Brindarle ayuda y colaboracion al especialista, que este a cargo de la investigacion. Me despido de ustedes, esperando que comprendan mi pocision
> From: mediawiki-l-request(a)lists.wikimedia.org
> Subject: MediaWiki-l Digest, Vol 82, Issue 22
> To: mediawiki-l(a)lists.wikimedia.org
> Date: Tue, 20 Jul 2010 12:00:08 +0000
>
> Send MediaWiki-l mailing list submissions to
> mediawiki-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
> or, via email, send a message with subject or body 'help' to
> mediawiki-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> mediawiki-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of MediaWiki-l digest..."
>
>
> Today's Topics:
>
> 1. Re: short headers in TOC (Frederick Grose)
> 2. Re: How to enable new features of MW 1.16? (Peter Velan)
> 3. Re: short headers in TOC (Scheid, Bernhard)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Jul 2010 22:01:18 -0400
> From: Frederick Grose <fgrose(a)gmail.com>
> Subject: Re: [Mediawiki-l] short headers in TOC
> To: mediawiki-l(a)lists.wikimedia.org
> Message-ID:
> <AANLkTikqUC41jemQLT2QkOhPIYKqhUvmM2YWtQvOH1V_(a)mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Mon, Jul 19, 2010 at 7:53 PM, Platonides <Platonides(a)gmail.com> wrote:
>
> > Scheid, Bernhard wrote:
> > > Sounds interesting but a bit arcane. I found the tocLine() function in
> > my Linker.php, but the problem seems to me how to define/override the
> > $tocline parameter.
> > > Can you give me some more detailled advice? New skin would be no problem,
> > btw...
> > >
> > > B.
> >
> > The skins inherit from the linker.
> > You could create a skin (supposing you want it to look like the vector
> > skin) by putting in the appropiate file in the skins folder something
> > like this:
> >
> > require_once "Vector.php";
> > class SkinBernhard extends SkinVector {
> > var $skinname = 'bernhardtoc';
> >
> > function tocLine( $anchor, $tocline, $tocnumber, $level, $sectionIndex
> > = false ) {
> > $n = strpos($tocline, ' ');
> > if ($n !== false) $tocline = substr( $tocline, 0, $n );
> > return parent::tocLine($anchor, $tocline, $tocnumber,
> > $level,
> > $sectionIndex);
> > }
> > }
> >
> > In this case, if the has a double space, the toc only shows the text
> > that appears before that.
>
>
> This would be a valuable feature to make part of the standard software. It
> would provide a way to collapse TOC boxes made suddenly wide, and obscuring
> of page content, by the insertion of a long section header.
>
> Is there a CSS or JS method we could employ for those without access to the
> Skins folder?
>
> --Fred
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 20 Jul 2010 08:04:15 +0200
> From: Peter Velan <pv0001(a)dynapic.net>
> Subject: Re: [Mediawiki-l] How to enable new features of MW 1.16?
> To: mediawiki-l(a)lists.wikimedia.org
> Message-ID: <4C453C5F.6060103(a)dynapic.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> am 19.07.2010 15:52 schrieb Lane, Ryan:
> >> I put this ...
> >>
> >> $wgVectorModules['collapsiblenav']['user'] = true;
> >> $wgVectorModules['collapsiblenav']['global'] = true;
> >>
> >> ... to my LocalConfig and checked that 'collapsiblenav' is enabled
> >> in my own settings.
> >>
> >> Nevertheless there's no collapsing menu entries. What I'm doing wrong?
> >
> > Collapsible nav doesn't work in 1.16 without modifying the Javascript.
> >
> > To fix this, replace all instances of #mw-panel with #panel in
> > Vector/Vector.combined.min.js, Vector/Vector.combined.js,
> > Vector/Modules/CollapsibleNav/CollapsibleNav.js, css/combined.min.css,
> > css/combined.css, and css/vector.collapsibleNav.css.
>
> I tried this and yes, collapsible nav worked, until ...
> ... I had to step back, 'cause the side effects are intolerable:
>
> - searchbox is filled with rubbish
> - some labels are undecipherable for my users
> - some new edit features are unusable
>
> Sad to say, but I'm still not able to use collapsible nav.
>
> Anyway, thanks for any suggestions,
> Peter
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 20 Jul 2010 13:17:16 +0200
> From: "Scheid, Bernhard" <Bernhard.Scheid(a)oeaw.ac.at>
> Subject: Re: [Mediawiki-l] short headers in TOC
> To: MediaWiki announcements and site admin list
> <mediawiki-l(a)lists.wikimedia.org>
> Message-ID:
> <366D7D7F1F289542B015A3E5DE057D5401C4FBAB9E8C(a)W07EXCHANGE.oeaw.ads>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Thank you, unfortunately it does not work. I do use a skin of my own and inserted your function there, but to no effect. I also tried ' ' and '-' as a delimiter.
>
> B.
>
> PS: Seems to be a good candidate for an extension, however I am unable to do that...
>
> -----Urspr?ngliche Nachricht-----
> Von: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] Im Auftrag von Platonides
> Gesendet: Dienstag, 20. Juli 2010 01:54
> An: mediawiki-l(a)lists.wikimedia.org
> Betreff: Re: [Mediawiki-l] short headers in TOC
>
> Scheid, Bernhard wrote:
> > Sounds interesting but a bit arcane. I found the tocLine() function in my Linker.php, but the problem seems to me how to define/override the $tocline parameter.
> > Can you give me some more detailled advice? New skin would be no problem, btw...
> >
> > B.
>
> The skins inherit from the linker.
> You could create a skin (supposing you want it to look like the vector
> skin) by putting in the appropiate file in the skins folder something
> like this:
>
> require_once "Vector.php";
> class SkinBernhard extends SkinVector {
> var $skinname = 'bernhardtoc';
>
> function tocLine( $anchor, $tocline, $tocnumber, $level, $sectionIndex
> = false ) {
> $n = strpos($tocline, ' ');
> if ($n !== false) $tocline = substr( $tocline, 0, $n );
> return parent::tocLine($anchor, $tocline, $tocnumber, $level,
> $sectionIndex);
> }
> }
>
> In this case, if the has a double space, the toc only shows the text
> that appears before that.
>
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
>
> ------------------------------
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
>
> End of MediaWiki-l Digest, Vol 82, Issue 22
> *******************************************
_________________________________________________________________
En Hotmail estamos reinventando un nuevo correo. Preparate para lo que se viene. Ver más
http://www.nuevohotmail.com