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
In conjuction with the embeded and safe JavaScriptInterpreter, a limited and secure (== read-only) set of functions may allow for user contributed site/wiki extensions and plugins and user editable code chunks in pages. (Parts of that was discussed as WikiFeatures:AutomaticFeatureInstall.)
guidelines
- read-only access to pages and system variables
- page code chunks may generate <html> or only Wiki output?
- eventually standardizable functions should begin with "wiki." - any internal features are accessible through "ewiki." prefixed function calls
API ideas
- wiki.getPage(id)
- most WikiXmlRpc calls
- wiki.getPageInfo(id)
- ...
- wiki.getAllPages()
- wiki.getRecentChanges(since_timestamp)
- wiki.listLinks(pagename)
- wiki.getBackLinks(pagename)
- wiki.searchPageTexts(new Regex("/content/i"))
- wiki.searchPage(namestr) - or regex
- make $_GET and $_POST available, allow for <form> generation
- ewiki.getVersion()
- ewiki.storeWikiVariable(name, value) - r/w access
- ewiki.appendToPage(name, content) - r/w access
- wiki.usemod.linkDatabase()
- ewiki.log(message) - r/w access
