No Description

Roman 896bbe76b4 SQL CaseWhen/Sum + ContactRequest API fix 1 week ago
.idea b2cb0c4bf3 .htaccess + more pages & routes 10 months ago
adminPanel 18e7955b12 Readme, some fixes, rel noopener for _blank links 2 weeks ago
core 896bbe76b4 SQL CaseWhen/Sum + ContactRequest API fix 1 week ago
css 0deb6fff52 Password Reset + Bugfixes 9 months ago
docker 6292f72032 docker stuff 1 week ago
docs efe3ada470 Frontend stuff 1 year ago
fileControlPanel 4a52ab2fd7 fix max size unit 2 weeks ago
files 191afa06fb FileAPI + Frontend 3 months ago
fonts 62f67967ba Initial Commit 1 year ago
img 43f4407269 removed exif data 2 weeks ago
js 8d408046de install.js port fix 2 weeks ago
static 536cae7a90 maintenance 2 weeks ago
.htaccess 518045e238 htaccess + token bugfix 3 months ago 2ae209f53b README update 1 week ago
cli.php 779550cab4 Contact Mails 1 week ago
docker-compose.yml 43d9a65def Triggers + EntityLog 1 week ago
index.php 6292f72032 docker stuff 1 week ago
robots.txt 62f67967ba Initial Commit 1 year ago


Web-Base is a php framework which provides basic web functionalities and a modern ReactJS Admin Dashboard.


  • PHP >= 7.4
  • One of these php extensions: mysqli, postgres
  • Apache/nginx or docker

Current Functionalities:


I actually don't know what i want to implement here. There are quite to many CMS out there with alot of vulnerabilities. There also exist some frameworks already. This project is meant to provide a stable project base to implement what ever a developer wants to: Dynamic Homepages, Webshops, ..


Default Installation

  1. git clone (or
  2. Create a mysql or postgresql database or use an existing empty database (e.g. test or public)
  3. Open the webapp in your browser and follow the installation guide

Docker Installation

  1. docker-compose up
  2. Open the webapp in your browser and follow the installation guide


For any changes made in /adminPanel or /fileControlPanel, run:

  1. once: npm i
  2. build: npm run build The compiled dist files will be automatically moved to /js.

To fulfill the requirements of data deletion for GDPR, add the following line to your /etc/crontab or any other cron file:

@daily www-data /usr/bin/sh -c 'cd /var/www/html && /usr/bin/php cli.php db clean'

Extending the Base

Adding API-Endpoints

Each API endpoint has usually one overlying category, for example all user and authorization endpoints belong to the UserAPI. These endpoints can be accessed by requesting URLs starting with /api/user, for example: /api/user/login. There are also endpoints, which don't have a category, e.g. VerifyCaptcha. These functions can be called directly, for example with /api/verifyCaptcha. Both methods have one thing in common: Each endpoint is represented by a class inheriting the Request Class. An example endpoint looks like this:

namespace Api;
use Api\Parameter\Parameter;
use Objects\User;

class SingleEndpoint extends Request {

  public function __construct(User $user, bool $externalCall = false) {
    parent::__construct($user, $externalCall, array(
      "someParameter" => new Parameter("someParameter", Parameter::TYPE_INT, true, 100)

  public function execute($values = array()): bool {
    if (!parent::execute($values)) {
       return false;
    $this->result['someAttribute'] = $this->getParam("someParameter") * 2;
    return true;

An endpoint consists of two important functions:

  1. the constructor defining the expected parameters as well as some restrictions and endpoint configuration.
  2. the execute function, checking all requirements by calling the parent, and then executing the own method.

To create an API category containing multiple endpoints, a parent class inheriting from Request, e.g. class MultipleAPI extends Request is required. All endpoints inside this category then inherit from the MultipleAPI class.

The classes must be present inside the Api directory according to the other endpoints.

Access Control

By default, and if not further specified or restricted, all endpoints have the following access rules:

  1. Allowed methods: GET and POST ($this->allowedMethods)
  2. No login is required ($this->loginRequired)
  3. CSRF-Token is required, if the user is logged in ($this->csrfTokenRequired)
  4. The function can be called from outside ($this->isPublic)
  5. An API-Key can be used to access this method ($this->apiKeyAllowed)
  6. All user groups can access the method (Database, Table: ApiPermission)

The first five restrictions can be modified inside the constructor, while the group permissions are changed using the Admin Dashboard. It's default values are set inside the database script.

Using the API internally

Some endpoints are set to private, which means, they can be only accessed inside the backend. These functions, as well as the public ones, can be used by creating the desired request object, and calling the execute function with our parameters like shown below:

$req = new \Api\Mail\Send($user);
$success = $req->execute(array(
  "to" => "", 
  "subject" => "Example Mail", 
  "body" => "This is an example mail"

if (!$success) {
   echo $req->getLastError();

The user object is usually obtained from the api ($this->user) or from the frontend document ($document->getUser()). If any result is expected from the api call, the $req->getResult() method can be used, which returns an array of all field.

Modifying the database

This step is not really required, as and changes made to the database must not be presented inside the code. On the other hand, it is recommended to keep track of any modifications for later use or to deploy the application to other systems. Therefore, either the default installation script or an additional patch file, which can be executed using the CLI, can be created. The patch files are usually located in /core/Configuration/Patch and have the following structure:

namespace Configuration\Patch;

use Configuration\DatabaseScript;
use Driver\SQL\SQL;

class example_patch extends DatabaseScript {
  public static function createQueries(SQL $sql): array {
    $queries = [];
    $queries[] = $sql->createTable("ExampleTable")
        ->addString("someString", 32)
    return $queries;


To access and view any frontend pages, the internal router is used. Available routes can be customized on the admin dashboard. There are four types of routes:

  1. Permanent redirect (http status code: 308)
  2. Temporary redirect (http status code: 307)
  3. Static Route
  4. Dynamic Content

A static route targets a file, usually located in /static and does nothing more, than returning its content. A dynamic route is usually the way to go: It takes two parameters, firstly the target document and secondly, an optional view. For example, take the following routing table:

Route Action Target Extra
/funnyCatImage Serve Static /static/cat.jpg
/someRoute(/(.*))? Redirect Dynamic \Documents\MyDocument\ $2

The first route would return the cat image, if the case-insensitive path /funnyCatImage is requested. The second route is more interesting, as it firstly contains regex, which means, any route starting with /someRoute/ or just /someRoute is accepted. Secondly, it passes the second group ($2), which is all the text after the last slash (or null) to the dynamically loaded document MyDocument.

Creating and Modifying documents

A frontend page consists of a document, which again consists of a head and a body. Furthermore, a document can have various views, which have to be implemented programmatically. Usually, all pages inside a document look somehow similar, for example share a common side- or navbar, a header or a footer. If we think of a web-shop, we could have one document, when showing different articles and products, and a view for various pages, e.g. the dashboard with all the products, a single product view and so on. To create a new document, a class inside /core/Documents is created with the following scheme:

namespace Documents {

  use Elements\Document;
  use Objects\User;
  use Documents\Example\ExampleHead;
  use Documents\Example\ExampleBody;

  class ExampleDocument extends Document {
    public function __construct(User $user, ?string $view = NULL) {
      parent::__construct($user, ExampleHead::class, ExampleBody::class, $view);

namespace Documents\Example {

  use Elements\Head;
  use Elements\Body;

  class ExampleHead extends Head {
    public function __construct($document) {
    protected function initSources() {
    protected function initMetas() : array {
      return array(
        array('charset' => 'utf-8'),
    protected function initRawFields() : array {
      return array();
    protected function initTitle() : string {
      return "Example Document";
  class ExampleBody extends Body {
    public function __construct($document) {
    public function getCode(): string {
       $view = $this->getDocument()->getRequestedView() ?? "<Empty>";
       return "<b>Requested View:</b> " . htmlspecialchars($view);

Of course, the head and body classes can be placed in any file, as the code might get big and complex.


Currently, there are two languages specified, which are stored in the database: en_US and de_DE. A language is dynamically loaded according to the sent Accept-Language-Header, but can also be set using the lang parameter or /api/language/set endpoint. Localization of strings can be achieved using the LanguageModule-Class. Let's look at this example:

class ExampleLangModule extends \Objects\lang\LanguageModule {
    public function getEntries(string $langCode) {
      $entries = array();
      switch ($langCode) {
        case 'de_DE': 
          $entries["EXAMPLE_KEY"] = "Das ist eine Beispielübersetzung";
          $entries["Welcome"] = "Willkommen";
          $entries["EXAMPLE_KEY"] = "This is an example translation";
      return $entries;     

If any translation key is not defined, the key is returned, which means, we don't need to specify the string Welcome again. To access the translations, we firstly have to load the module. This is done by adding the class, or the object inside the constructor. To translate the defined strings, we can use the global L() function. The following code snipped shows the use of our sample language module:

class SomeView extends \Elements\View {
  public function __construct(\Elements\Document $document) {
    $this->langModules[] = ExampleModule::class;
  public function getCode() : string{
    return L("Welcome") . "! " . L("EXAMPLE_KEY");


Using the CLI, you can toggle the maintenance mode, perform database updates, managing routes and updating the whole project. Some example usages:

Maintenance commands

php cli.php maintenance status
php cli.php maintenance off
php cli.php maintenance on
php cli.php maintenance update

Database commands

php cli.php db export > dump.sql
php cli.php db export --data-only > data.sql
php cli.php db import dump.sql
php cli.php db migrate Patch/SomePatch

Route commands

# Route commands
php cli.php routes list
php cli.php routes remove 1
php cli.php routes enable 1
php cli.php routes disable 1
php cli.php routes add /some/path static /static/test.html
php.cli.php routes modify 1 '/regex(/.*)?' dynamic '\\Documents\\Test'

Anything more?

Feel free to contact me regarding this project and any other questions.