Hi all,
Having learned the hard way that just doing Retrospect filesystem
backups does not always work on the database... I'm looking for advice
on how to do backups for our public wikis to minimize downtime when
we're doing server maintenance.
I've looked at the docs at:
http://www.mediawiki.org/wiki/Backup
and I'm still a bit confused. Assuming that I'll be using mysqldump...
do I need to take the wiki offline during the dump process (the
discussion of mysqldump vs mysqlhotcopy seems to be inconsistent with
what's at the mysql.com website wrt using hotcopy with InnoDB
tables)? Are there any tips people can share?
This came up during a migration of /usr/local/mysql and the apache
root directory to a new set of disks. I had backed everything up to
another set of disks (actually this was temporarily using our dev
server as a firewire drive). I pointed usr/local and apache root to
the backups in the hope that I could keep the wikis online while we
replaced the main disks on the production server. The plan was to keep
this running while we set up the new disks and then copy data back to
the new disks, change the symlinks for /usr/local etc to the new
places, and restart mysql and apache. While this is going on, I've
disabled editing on the backup copy, but users should be able to view/
browse/search. But mysql was very unhappy and wouldn't run from the
backups. I ended up deleting all of the files from the backup copy of
the mysql data directory and rebuilding all the databases in the
backup from an SQL dump, with apache turned off for several hours.
I feel like there has to be a better way, even with our small operation.
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
I think that extension ConfirmAccount <http://www.mediawiki.org/wiki/Extension:ConfirmAccount> should help you.
--Matěj Grabovský
>---------------------------------------------------------
>Od: Pavel Kosina
>Přijato: 23.6.2008 16:27:21
>Předmět: [Mediawiki-l] create account
>
>Does there exist any extension that would ensureme, that creating
>
>account must be verified by me as sysop? On a special page I would see
>
>requests for creating accounts or I would get emails from wiki, asking
>
>me to confirm or not.
>
>
>
>Thank you
>
>
>
>--
>
>geon
>
>Pavel Kosina
>
I'm thinking this may be a php bug rather than a mw problem - but I'm
wondering how to get around it. I generate MW xml for importing pages
and I use htmlentities to encode things for xml. But I just saw a
problem with the XML parser failing to recognize the ± entity.
Any suggestions?
Jim
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054
Does there exist any extension that would ensureme, that creating
account must be verified by me as sysop? On a special page I would see
requests for creating accounts or I would get emails from wiki, asking
me to confirm or not.
Thank you
--
geon
Pavel Kosina
Hi list,
the CentralAuth extension is a great addon when it comes to authenticate
users across a set of wikis.
I want to use it in my current setup: One domain housing multiple wikis
separated by subdomains, e.g. de.domain.org, en.domain.org and so on.
I'm currently in an shared hosting environment with limited access to
the databases. I can only create databases with predefined names which
limits me to setup the CentralAuth extension.
Does anyone know how to accomplish this within one database using
prefixes for each of the subwikis?
Best regards,
Marcus
All,
Another quick question concerning authentication in Mediawiki. It would
apear as though we are seeking a system where the user doesn't need a
password and doesn't have to register. I do have all of the users on an LDAP
server which is at my disposal. I guess two questions stem from this :
1. Is there a way for mediawiki to just ask the user a username and not a
password without using LDAP? I know that sounds wierd.... but it's kinda the
end goal.
2. If I use LDAP is there a way to just tell it always to accept the PW
without botherin to check if it's right?
3. My only other idea is to enable httpauth and figure out how to leave the
auth open..
The wiki is on a private network FYI so security isn't really an issue.
--
Thank You and Sincerely,
Jon
All,
I am creating a page that links to a dozen or so other pages; each of
these other pages more or less corresponds to a "chapter" of our
documentation.
I would like this landing page to have a complete table of contents,
including all the sub-headings of the subsidiary pages. Is this possible?
For example, this seems easy (each line is a page link):
* Installing
* Developer's Guide
But what I want is this (the subsections are linked to subheadings):
* Installing
* Installation Instructions
* Software Prerequisites
* Pyserver
* Flashclient
* Compiling
* Developer’s Guide
* New Developer How-To
* Using Subversion
* Branching model
* Checkout
* How to commit
* Postgres notes
* Dumping and loading the database
* Misc
* Troubleshooting
Is this possible (other than manually)? If so, how do I do it?
Many thanks,
Reid
Hi all,
I have three web applications, media wiki, a submission form, and a
repository web application. I want to integrate media wiki
login/authentication to the submission form. Because this is my first
time using media wiki, I do not have clear information about media wiki
authentication for checking the login status and pass the user
information to the submission form (media wiki cookie and session
information). Can anyone provide me more information about this or
provide me a direction to get more information about this?
For the repository, I want to protect the repository from public access
and only allow media wiki user to access it. Is there a way to do this?
Thanks,
Harry
Hopefully this isn't too complicated. I'm in the middle of transistioning a
rather large wiki to mediawiki. Previously it was a custom Ruby wiki using
textile. We have successfully converted all of the textile and what not. Now
we are facing some differences in functionality. There are two main things
that we seem to be missing in mediawiki and are trying to find as extensions
or determine that we have to do some development.
1. Autosummery - a way to display a short summery of a given page. It has a
more button on the bottom that displays the full article.
2. A way to rotate blogs / news articles shown on the main page based on
thier age. IE have the 5 newest pages in the "News" catagory displayed on
the "news" page, if someone posts a new page in the news category it should
then show up and the oldest would no longer be listed but instead accessible
by accessing category:News as normal.
--
Thank You and Sincerely,
Jon