Note: Most of the actions on this page require administrative privileges. They will not work unless you have set an admin username and password in the PhpWiki config file.
First select pages and then define the action:
or call the available WikiAdmin actions directly:
PhpWiki:EmailVerification is currently non-strict, leaving some possible holes, which can be administrated below.
This button will show a list of all users with registered emails and buttons to set the verification status manually.
To prevent from robots eating all possible ressources in a short time, blocking from certain IPs or not-well-behaving user agents can be defined below. See PhpWiki:HowToBlockRobots and MeatBall:SurgeProtector. Note: Not yet enabled.
A Wiki SandBox is very easy to clean. Here you can restore it to pristine condition by loading the default from pgsrc.
Making Snapshots or Backups
ZIP files of database
These links lead to zip files, generated on the fly, which contain all the pages in your Wiki. The zip file will be downloaded to your local computer.
If your php has zlib support, the files in the archive will be compressed, otherwise they will just be stored.
Dump to directory
Here you can dump pages of your Wiki into a directory of your choice.
The most recent version of each page will written out to the directory, one page per file. Your server must have write permissions to the directory!
If you have dumped a set of pages from PhpWiki, you can reload them here. Note that pages in your database will be overwritten; thus, if you dumped your HomePage when you load it from this form it will overwrite the one in your database now. If you want to be selective just delete the pages from the directory (or zip file) which you don't want to load.
Here you can upload ZIP archives, or individual files from your (client) machine.
Here you can load ZIP archives, individual files or entire directories. The file or directory must be local to the http server. You can also use this form to load from an http: or ftp: URL.
- Upgrade the database schema (mysql page.id auto_increment, ADD session.sess_ip),
Format of the files
Currently the pages are stored, one per file, as MIME (RFC:2045) e-mail (RFC:822) messages. The content-type application/x-phpwiki is used, and page meta-data is encoded in the content-type parameters. (If the file contains several versions of a page, it will have type multipart/mixed, and contain several sub-parts, each with type application/x-phpwiki.) The message body contains the page text.
The upload and load functions will automatically recognize each of these three types of files, and handle them accordingly.
This will generate a directory of static pages suitable for distribution on disk where no web server is available. The various links for page editing functions and navigation are removed from the pages.
These are here mostly for debugging purposes (at least, that is the hope.)
In normal use, you should not need to use these, though, then again, they should not really do any harm.
(If your wiki is so configured,) the transformed (almost-HTML) content of the most recent version of each page is cached. This speeds up page rendering since parsing of the wiki-text takes a fair amount of juice.
Hitting this button will delete all cached transformed content. (Each pages content will be transformed and re-cached next time someone views it.)
Page names beginning with the subpage-separator, usually a slash (/), are not allowed. Sometimes though an errant plugin or something might create one....
This button will delete any pages with illegal page names, without possibility to restore.
Warning! This button will delete every empty and unreferenced page, without any possibility to restore them again. This will disable the possibility to revert or get back any deleted page.
This is only needed on SQL or ADODB if you didn't do action=upgrade, but created the new page.cached_html field seperately, and now you want to move this data from page.pagedata over to page.cached_html.