project
project summary freshmeat entry development infos mailing list WebInstaller database tools ChangeLog
page plugins
ProtectedEmail PowerSearch README README.config README.plugins README.fragments ProtectedMode INTERNALS WordIndex AboutPlugins PhpInfo OrphanedPages ListOfPluginHooks RSS RecentChanges PageIndex NewestPages SearchPages MostVisitedPages MostOftenChangedPages UpdatedPages
usage hint
9OTUNE YOGURT SÜREER AYRAN OLANA KADAR SİKERİMxD
The ewiki.php script basically is some sort of library, and it is possible to build multiple frontends to your Wiki (like the scripts in our examples/ directory). This not only allows to have multiple layouts available, but also to have each with a different feature set.
A different feature set then could also mean, that you have one wrapper for the public (which for example wouldn't allow editing), and a second for yourself, which did (but then required a password; see also fragments/funcs/auth.php). This is useful, if you want a PersonalWiki.
a sample public wrapper, that forbids editing
<?php
define("EWIKI_SCRIPT", "public.php?id=");
include("config.php");
// or include("ewiki.php");
#-- disallow some stuff, you wouldn't want visitors to do
unset($ewiki_plugins["action"]["edit"]);
?>
...
<body>
<?php
#-- output page content
echo ewiki_page();
?>
</body>
...
Often you would want to call this (see EWIKI_SCRIPT) file then "index.php" instead.
your unrestricted personal wrapper
<?php
define("EWIKI_SCRIPT", "admin.php?id=");
include("config.php"); // or include("ewiki.php");
#-- add some admin stuff
include("plugins/admin/page_searchandreplace.php");
#-- require a password
include("fragments/funcs/auth.php");
?>
...
<?php
echo ewiki_page();
?>
...
Please note, the different setting for EWIKI_SCRIPT here. It is not necessary to keep the name "admin.php" script secret, because it is already protected by HTTP auth (see the .../auth.php script).
