Hi all,
this is my first post in this mailing-list and I say hello to everyone.
I just upgraded my MW installation to 1.14.
Before upgrade, all things were working perfectly, even the SVG
thumbnailing.
After the upgrade, when an SVG is uploaded, I receive this error:
> Warning: passthru() has been disabled for security reasons
> in /path/to/home/includes/GlobalFunctions.php on line 2131
The server admin, in fact, has disabled passthru().
I have always used this to render my SVGs:
$wgSVGConverter = rsvg;
What can I do to have back this function?
Info about my server (I do not have root access to it):
MediaWiki 1.14.0
PHP 5.2.9 (cgi)
MySQL 5.0.68-log
Thank you for any support.
P.S. Sorry for possible mistakes in my post, but I'm not English
native. :)
--
Aldo Latino
OpenPGP key: 0x4397C730
I'd like to have a parser extension that would copy specific text from
a category page to all of its subcategories. I'm imagining that it
would be something where there would be a tag to mark text to
propagate below to all subcategories, sub-subcategories etc, and
another set of tags that would be like an RSS aggregator for all the
text from ancestor categories.
Does such a thing exist? Any thoughts on how bad performance would be?
Thanks!
Jim
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
Thanks for documenting them, Brian. I think that a couple of them are
simply your opinion, some are OS or Mediwiki version specific, and at
least a couple are actually bugs. I'll certainly work on fixing the
latter, and I do appreciate your feedback on the former--I'll take them
into consideration.
Brain Mingus wrote:
> I've documented 11 bugs on this extension's talk page.
>
> http://www.mediawiki.org/wiki/Extension_talk:EzMwLucene
>
> The summary is that this extension is simply not ready for public use. After
> installing it your wiki will be broken in several unacceptable ways.
>
Brian,
You're right about the initial loadling--however, this is actually only
a problem during the import (the realtime feed doesn't have problems
with the unicode in the titles). But, yes, we have seen a couple of
issues around unicode that we'll need to fix.
As far as the line feeds, good catch. I thought I'd updated those with
Linux newlines, but apparently not. I'll make sure it's fixed for the
next release.
Thanks!
Brian Mingus wrote:
> I just about have this extension running. It sure would benefit from
> MWSearch's improved unicode handling:
>
> <snip>
> service.sh has funky windows newlines that simply don't work on linux. I
> used the ubuntu package tofrodos, which contains the program fromdos, which
> cleaned it up for me.
>
Good catch, Ryan. Actually, there is no dependency on 1.6, but POI
(which is used for text extraction from Microsoft formats) does require
at least 1.5.
Unfortunately, since I compiled it under 1.6, the binaries I posted will
need 1.6. I'll have to rebuild them with 1.5...
Ryan Lane wrote:
> Does this require java 1.6? I'm getting an error trying to launch it:
>
> <snip>
> Answering my own question... It works properly with java 1.6, so I'll update
> the wiki page to mention this requirement.
>
>
Hi, I backed up two tables (category, and categorylinks) from my database
and export it into another. Both wikis uses the same Mediawiki Version 1.14.
Although I do see that the two tables are uploaded, I cannot access them. Is
there something that I miss?
PM Poon
Hello all
i have a local wikipedia and working fine for my intranet users, i have
internet conection trougth proxy.
i need make to see images caching of original images (prefer thumbnail only)
to make best look of my wiki, my users no have internet acces.
what i can do??
other cuestion is if i can delete an entry category - subcategory and
respectives articles of wikipedia.
No word yet from the extension owner at Sun Wiki Publisher.
Any ideas/experience from the group?
On Mon, May 4, 2009 at 10:10 AM, Evelyn Yoder <eyoder(a)gmail.com> wrote:
> Hello -
>
>
> We're using siteground to host the site at
> http://clev9.com/~platfor1/wiki/index.php?title=Main_Page<http://clev9.com/%7Eplatfor1/wiki/index.php?title=Main_Page>
>
> Our public wiki help sites are here, and originate from the clev9 database:
>
> http://lj.platformatyourservice.com/~platfor1/wiki/index.php?title=Main_Page
>
> http://rn.platformatyourservice.com/~platfor1/wiki/index.php?title=Main_Page
>
> Best,
> Evelyn
>
>
> ------------------------------
>
> *From:* Evelyn Yoder [mailto:evelyn@longjump.com]
> *Sent:* Friday, May 01, 2009 11:17 AM
> *To:* 'dev(a)sw.openoffice.org'
> *Subject:* question about OpenOffice.Writer / Sun Wiki Publisher /
> MediaWiki setup
>
>
>
> Hi –
>
> I’ve been using Mediawiki to build online help for our PaaS solution. It
> works well, but I’m the lone writer, because contributors aren’t inclined to
> learn MW syntax.
>
> I just found the Sun Wiki Publisher extension and I think it could be the
> solution I’m looking for.
>
> I ran into a problem and wonder if you can help:
>
> - Installed: OpenOffice and the Sun Wiki Publisher extension
>
> - In OpenOffice.Writer: Click Tools | Extension Manager | Sun Wiki
> Publisher | Options | Add
>
> - In dialog box MediaWiki Server, enter:
>
>
>
> URL: http://clev9.com/~platfor1/wiki/
>
> Username: Mediawiki username
>
> Password: Mediawiki password
>
> Error: A connection to MediaWiki system at “
> http://clev9.com/~platfor1/wiki/index.php?title=Main_Page<http://clev9.com/%7Eplatfor1/wiki/index.php?title=Main_Page>”
> could not be created
>
>
>
> Any ideas? Is this a localsettings.php or permission issue?
>
> Thanks in advance for your advice. Best,
>
> Evelyn
>
>
>
> ~~~~~~~~~~~~~~~~~~~~
>
> Evelyn Yoder
>
> Technical Communications
>
> www.longjump.com
>
> Wiki Help: www.longjumpsupport.com
>
> 408-774-9474 x 355
>
>
>
>
> On Mon, May 4, 2009 at 12:31 AM, ccornell - OpenOffice.org <
> ccornell(a)openoffice.org> wrote:
>
>> On 05/02/09 00:37, Evelyn Yoder wrote:
>> > Followup: the Sun Wiki Publisher didn't connect to MW as expected.
>>
>> I'd be interested in what didn't work. Maybe you or I can provide that
>> feedback to the developers and get that extension fixed up so that it
>> works properly with MediaWiki. :-)
>>
>> C
>>
>> --
>> Clayton Cornell ccornell(a)openoffice.org
>> OpenOffice.org Documentation Project co-lead
>> StarOffice - Sun Microsystems, Inc. - Hamburg, Germany
>>
>> _______________________________________________
>> MediaWiki-l mailing list
>> MediaWiki-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>>
>
>
Thanks!
You are correct in assuming that this is designed for small-to-medium
sized wikis--we have about 1000 users a couple of hundred edits per day,
but our scale testing indicated it would handle at least 20-30 combined
queries/updates per second (of normal sized pages).
I'm assuming that you mean "single-host" from a indexing server point of
view, and yes, at this time that is completely correct. Article
indexing, however, can easily support multiple Mediawiki servers calling
it. Currently the attachment indexing relies on there only being a
single Mediawiki server as well, but that's an easy modification.
There is a preload mechanism that grabs the pages directly from the
database for indexing as well. At some point I intend to combine the
two, thereby keeping the real-time update but also providing a
background indexer in case the realtime feed fails for some reason
(therefore ensuring that no articles are missed). For us the latter's
not a big problem as we can reindex in about an hour.
Robert Stojnic wrote:
> Very nice work Chris!
> I think it strikes a good balance of simplicity and flexibility that
> makes is ideal for small-to-medium sites.
>
> The architecture itself seems to be similar to that used in early
> mwsearch, where index is updated via hooks that submit articles directly
> to indexer. So, it assumes single-host architecture and uses
> out-of-the-box lucene scoring and highlighting as far as i can see. I
> think the most interesting part for us is the handling of attachments. I
> see you use apache poi and pdfbox. We should really try to use this as
> well, this shouldn't be too hard to do, but needs a bit of fiddling..
This actually came from the Key Equipment Finance wiki. We've found it
to be pretty good, but not perfect, in a corporate environment. This
addressed point #2, and we've used FCKEditor with pretty good success
for #1. Many folks would argue there's a #3 (fine-grained security),
but I've managed to hold them off on that front thus far.
David Garard wrote:
> I'm still looking forward to corporate readiness of MediaWiki, which
> for us basically means (1) good WYSIWYG (2) good search. (2) means
> Lucene in a box. We hardly care what box.
>
> (The competitor is Confluence. Which is highly usable and an UTTER
> BASTARD to administer. Though Atlassian are very good at support.)
>
>
> - d.
>