Skip to content

API Overview

This page gives developers a starting point for the most common QUIQQER API entry points. It is not a generated API reference.

Common Entry Point

The global QUI class is a central service entry point for package code. It exposes configuration, managers, runtime helpers, database access, request/session access, and package/project objects.

Common entry points include:

MethodArea
QUI::conf()Main configuration access.
QUI::getConfig()Load a specific config file.
QUI::getPackageManager()Package manager access.
QUI::getPackage()Package object access.
QUI::getProjectManager()Project manager access.
QUI::getProject()Project access.
QUI::getEvents()Event manager access.
QUI::getPermissionManager()Permission manager access.
QUI::getUsers()User manager access.
QUI::getGroups()Group manager access.
QUI::getLocale()Runtime locale access.
QUI::getSystemLocale()System locale access.
QUI::getTemplateManager()Template manager access.
QUI::getMailManager()Mail manager access.
QUI::getDB() / QUI::getPDO() / QUI::getDataBase()Database access.
QUI::getQueryBuilder()Doctrine query builder access.
QUI::getSchemaManager()Doctrine schema manager access.
QUI::getRequest()Current HTTP request access.
QUI::getSession()Current session access.
QUI::getTemp()Temporary file/data helper access.

Managers And Services

QUIQQER exposes manager classes for major system areas, including:

  • packages: QUI\Package\Manager
  • projects: QUI\Projects\Manager
  • users: QUI\Users\Manager
  • groups: QUI\Groups\Manager
  • permissions: QUI\Permissions\Manager
  • events: QUI\Events\Manager
  • mail: QUI\Mail\Manager
  • cache: QUI\Cache\Manager
  • uploads: QUI\Upload\Manager

Use these entry points from package code when you need to integrate with projects, users, permissions, events, packages, templates, mail, cache, uploads, or database access.

Released under GPL-3.0-or-later.