Hi,
I tried to upload my site to free.fr, but I got the message
PHP 5.0.x is buggy on your 64-bit system; you must upgrade to PHP 5.1.x or
higher. ABORTING. (http://bugs.php.net/bug.php?id=34879 for details)
Where can I find a provider using "PHP 5.1.x or higher" ? I live in France
near Paris.
cheers
Klaus
Dear list,
a quick search through the list archives didn't bring up a result so
please excuse me if this issue has been solved already.
I am currently using Mediawiki 1.9.2. and experienced problems uploading
PNG images.
Although my test image shows an 'image/png'-mimetype with 'file -i',
Mediawiki keeps saying the file was corrupted.
Monitoring /tmp/php* while uploading the image again shows the uploaded
file to be image/png, too:
while(usleep 1); do file -i /tmp/php*|grep -v "ERROR"; done
/tmp/phpksjpPO: image/png
Mediawiki debug says
MimeMagic::detectMimeType: magic mime type of /tmp/phpcDoKKE:
text/plain
amongst other things, so I guess MimeMagic isn't working correctly..
Searching the meta wiki gives me the hint to add
$wgMimeDetectorCommand = "/usr/bin/file -bi";
to LocalSettings.php as a workaround, which actually does the trick.
But still I wonder: What's the problem with MimeMagic?
Thanks,
Sebastian
What I want to do is be able to transclude individual sections of pages...
without having to go back and edit old pages to add <onlyinclude> tags.
I did find the Labeled Section Transclusion extension (
http://www.mediawiki.org/wiki/Labeled_Section_Transclusion) but that also
involved edit old pages.
Are there any other options?
Dan
Hi Jim,
On 5/27/07 12:42 PM, "Jim Wilson" <wilson.jim.r(a)gmail.com> wrote:
>
> Without going into too much detail, the current implementation of
> ExtendedSyntaxParser, while operating fine by itself, is not amicable
> to running along side certain other kinds of extensions. It's
> something that I've wanted to revisit, but haven't had time to do so just
yet.
Since I wrote TabbedData, I'm wondering what the incompatibility is? Is there
something I can change in TabbedData to make this work?
BTW, the UsenetSyntax page makes no mention of requiring ExtendedSyntaxParser,
and I can't find it on mw.org... where do I get it?
Ian
We'd like to convert some (eventually all) of our site to printable PDF
(and to be able to autogenerate such in the future.) It's easy enough to
batch-download html, and to organize either via internal tags or an
external TOC (in conjunction with scripts). Is there a better way to do
it directly? And if not, any recommendations for good HTML->PDF
converters, preferably ones that we could do pagination in, and
preferably convert internal links into page references?
Thanks,
Ken
Dear Friends,
my Homepage is hosted by www.loomes.de, PHP 4.3.10-20, phpMyAdmin 2.5.6,
MySQL 5.0.30. Local www.graenz.name/wiki with all dates from Install and
Extract V. 1.10.
No Start-Monitor!
Please help me.
Best Regards from Dresden, Saxony, Germany, Old Europe
René
René Gränz
PF 280214
01142 Dresden
Funk: 0162/1 76 53 55
e-Mail: rgraenz(a)gmx.de
http://www.graenz.name
----------------------------------------
+++ Aktualisierte Daten per Mai 2007 +++
+++ www.ahnenliste.graenz.name +++ Neu +
----------------------------------------
+++ Sie helfen bei geneal. Projekten +++
+++ Neu +++ www.projekte.graenz.name +++
----------------------------------------
Dear mediawiki admin experts,
I have a configuration goal for my installation of mediawiki that might technically only be a web-server related modification, but I am convinced that the solution (if it is even possible) will requires the advanced insights of this group of experts. Here's the situation: I have set-up a mediawiki (1.6.10) on a dedicated company server (Red Hat, Apache 2.0.52) which uniformly (www and intranet) limits browser accessibility to users who have a company username and password which they are required to provide to the browser in order to view the wiki articles. wiki user-accounts for authoring are handled by the LDAP module. This part all works great. --- The problem is --- that I am now being asked if it is possible to make certain pages "publicly" accessible and not protected behind a secure browser authentication against the company's domain (after we've gone to such excellent lengths to protect all of the content!!!) I am being asked if specific articles and/or all of the articles in certain namespace can be made to be an exception to our global restrictions on who can "see" the articles. A specific example is the "Main Page" and any of the User's pages. So, does anyone know how to configure a mediawiki such that "some" pages require secure browser authentication even just to see them? If so, the ideal solution would behave such that new pages are created inaccessible from the public by default. --- sincerest thanks all. - Rich (revansx)
Hi folks,
Does anyone know of a way to limit editing to the first person to
create a page? For example, if I create a page on the wiki, I'm the
only one (besides admins) that can edit the page afterwards?
Richard