Morning!
I am building a web site for a family member who is in the process
of completing a PhD and MediaWiki looks like the ideal CMS to use
as they will be able to update their own web site (delegation is
always important :-)
Two questions:
1) There may be a need to have certain pages in multiple languages.
Is the best way to do this for a small site is to add a language
identifier to the page title eg:
here is the CV in [[CV.en|English]] or in [[CV.nl|Dutch]].
Is there a way to do this and still have a more readable title eg
"English CV" rathern than "CV.en"?
2) I see from the LocalSettings.php that it is possible to prevent
access to certain pages for users who are not logged in. Do I
need to list all the pages I want blocked or is it possible
to do wildcards eg internal*
TIA
James
I documented the steps to add AdSense to MediaWiki 1.4, as I suspect others
will also find this useful. If you're not familiar with it, AdSense pays
you ~70% of the click-though revenues Google receives by placing ads on your
page.
http://www.dankohn.com/archives/000338.html
You can see the results
at http://www.pwsnotes.org
- dan
--
Dan Kohn <mailto:dan@dankohn.com>
<http://www.dankohn.com/> <tel:+1-650-327-2600>
Hi,
config/index.php has failed on creating table
I tried piece of maintanance/tables.sql
in mysql
mysql> CREATE TABLE /*$wgDBprefix*/categorylinks (
-> cl_from int(8) unsigned NOT NULL default '0',
-> cl_to varchar(255) binary NOT NULL default '',
-> cl_sortkey varchar(255) binary NOT NULL default '',
-> cl_timestamp timestamp NOT NULL,
-> UNIQUE KEY cl_from(cl_from,cl_to),
-> KEY cl_sortkey(cl_to,cl_sortkey(128)),
-> KEY cl_timestamp(cl_to,cl_timestamp)
-> );
ERROR 1071 (42000): Specified key was too long; max key length is 1024 bytes
mysql>
mediawiki version 1.4rc1
mysql version 4.1.10.
What should be changed in mysql config in order not to bump in limitation.
Thank in advance.
--Nick Zhokhov
I've read this page:
http://meta.wikimedia.org/wiki/Documentation:Security
but I'd like to know how to require editors to log in first, and how to
disable account creation.
Also, I'm not sure how to disable running PHP scripts in any directories
except the script directories. Can I just copy this ato the end of my
httpd.conf file and then reboot the server:
<Location "/wiki/images">
php_admin_flag engine off
AddType text/plain .html .htm .shtml
</Location>
All related comments on how to secure a wiki are welcome.
TIA
Although it's my habit to first lurk a bit on a mailinglist, then
write, I've got an issue which bothers me so much I deny my normal
behaviour (too much difficult english words in a too lang sentence for
a simple dutch guy).
While working with my wiki, I want to create different layouts for
different peaces of my wiki. I could just install different
mediawiki's, but that is a bit too much space consuming, so after a
while of searching I found the word Wikifarm.
Only problem is that there is no information regarding wikifarms and
mediawiki. )-:
the question: Should the solution be somewhere in wikifarms or are
there other ways to achieve multiple layouts?
thanks in advance
Lighans
--
My mediawiki effort (in dutch): http://huijgen.ligfiets.net/mediawiki/
We just tried going to 1.4.0 and got this result - make sense to
anyone?! TIA
> OK - I've upgraded the Wiki software to version 1.4.0. It all seemed
> to go smoothly, so please check if everything looks OK. In case of
> emergencies, I backed up the old version into folder mediawiki-1.3.1,
> and also dumped the old database into that folder (using mysqldump) as
> file database-dump.
>
> Oh no! I just logged in to the Wiki and all the dates are completely
> crazy, although the data all seems to be there. Should I revert to
the
> old system?
>
>
and
>
>
> The new installation was unusable. Apart from the silly dates, I
> couldn't update any Wiki pages. The "recent changes" pages showed a
> list of changes dated in the year 2030, and the history of an
> individual page showed potty dates such as 1919 or 1995. Check it out
> at http://www.ucl.ac.uk/calt/alpd/wiki-new
>
> I've now reverted to the old system. I restored the old database into
> a new one with a different name (uczaw3e_alpdwiki2). The restore from
> the dumped database appeared to go OK - please check that everything
> seems in place.
>
> I'll try to think of another way to do the upgrade. I was trying to
do
> it in the existing folder, in case you had made any changes to it.
> Have you ever added or changed any files in the folder? If not, I'll
> try it in a new folder. Doh - just tried it in a new folder and got
> the same mess. I'm a bit stumped.
Hello,
I have implemented mediawiki to manage documentation on development rules
and source code management tools usage from my firm.
All users find it very usefull and simple to use and easy to make
modifications on articles.
We have now a new office in another country. We have a VPN between the 2
locations but the bandwith is to small. The users in the new office find
borring to use wiki (20 secondes to display a page against instant display
in "old" office)
I would like to have 2 instances of mediawiki on 2 servers, to synchronize
them and to allow users to make modification on both instances.
For php scripts and uploaded files, I have the solution, but I don't have
one for database.
We have a server A (located in old office) and a server B (located in new
office), both of them are complete webserver (L.A.M.P.)
Users from the old office are connected to A, Users from the new one to B.
Users make modification on A, they are transfert to B ("simple" master/slave
replication in mysql).
But if users modify something on B ... it's not transfered (mysql don't have
master/master replication).
Is there a way to redirect mysql queries according to their type in
mediawiki : select on B(slave) and insert/update/delete on master(A) ?
(mysql replication is used to push modification for A to B)
Perhaps, the solution implemented to wikipedia is the one I need.
Could you explain it ?
Best regards,
Laurent
PS1 : I tryed a solution with cache Turck MMCache and mediawiki on B that
connect to the database on A. The time to display a page is of 10s.
PS2 : Sorry for the long mail ...
PS3 : Soon ;)
I'm starting a new intranet-style wiki, and I'd like to make the wiki
links fully case-insensitive.
I've read various discussions about the pros and cons of
case-sensitivity. What I'm not entirely clear about is what would need
to be changed (at the technical level) to achieve it. From what I've
read, it may be that the chief technical problem is dealing with
existing pages whose title differs only in case. Since I'm starting
from scratch, that wouldn't be a concern for me.
Is there some well-known bit of code that needs to be modified to
achieve case-insensitive links for a new wiki? Or is this something
that needs to be figured out yet?
Hi,
I'm using the Mediawiki 1.4rc1 . I couldn't find the
templates/xhtml_slim.pt file.
There is no templates directory..
!!! Please Help !!!
Karthik.G
>The main skeleton of pages is in templates/xhtml_slim.pt
>Beware when you play with it, it's not simple html. As you can see it is
>a little bit written to be interpreted by an engine (called phptal)
>Fxparlant
>(François)
Karthik Gopalakrishnan wrote:
> Hi,
>
> I'm relatively to new to mediawiki. I'm planning to run a wiki in my
> local intranet using the wikipedia Database Dump. I know that full
> text search functionalaity is disabled. I want to remove the "Search"
> Button and just have the "Go" Button to search the articles. Which php
> file should I modify.
>
> !!! Please Help !!!
> Karthik.G