"User list", "version" => "0.1", "author" => "Starbeamrainbowlabs", "description" => "Adds a 'user-list' action that generates a list of users. Supports json output with 'format=json' in the queyr string.", "id" => "page-user-list", "code" => function() { global $settings; /** * @api {get} ?action=user-list[format=json] List all users * @apiName UserList * @apiGroup Utility * @apiPermission Anonymous */ /* * ██ ██ ███████ ███████ ██████ ██ ██ ███████ ████████ * ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ * ██ ██ ███████ █████ ██████ █████ ██ ██ ███████ ██ * ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ * ██████ ███████ ███████ ██ ██ ███████ ██ ███████ ██ */ add_action("user-list", function() { global $env, $settings; $userList = array_keys(get_object_vars($settings->users)); if(!empty($_GET["format"]) && $_GET["format"] === "json") { header("content-type: application/json"); exit(json_encode($userList)); } $content = "
Although you can use the edit page to view a page's source, you can also ask $settings->sitename to send you the raw page source and nothing else. This feature is intented for those who want to automate their interaction with $settings->sitename.
To use this feature, navigate to the page for which you want to see the source, and then alter the action
parameter in the url's query string to be raw
. If the action
parameter doesn't exist, add it. Note that when used on an file's page this action will return the source of the description and not the file itself.