Libraries tagged by custom configs

Provide configurable Mail Transport Factories for ZF2 (Custom)

Go to Download

Dynamic Job Tab Bundle: Seamlessly add custom tabs to any job with the Dynamic Job Tab Bundle. This versatile tool allows you to dynamically integrate a custom tab into your job listings. To configure the job name, simply update the configuration.yml file.

Go to Download

Provide configurable Mail Transport Factories for ZF2 (Custom)

Go to Download

Composer plugin for creating symlinks to packages in custom directories. Supports type-based, vendor-based, and name-based matching with configurable paths.

Go to Download

User Administration Module for Yii2. This module wraps and extends the default user management interface provided by the framework. Several parts of this module however, are designed to be fully compatible with the factory-provided implementations related to user management. For this, several configuration options can be set to override module defaults allowing the use of the factory default or custom classes.

Go to Download

This is a core, empty project template used as the starting point for all custom projects developed by GPS Publishing and Distribution. It provides the foundational structure and essential configurations required to begin any new project tailored to our company's standards.

Go to Download

The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.

Go to Download

Provide configurable Mail Transport Factories for ZF2(FMC Custom)

Go to Download

Provide configurable Mail Transport Factories for ZF2(FMC Custom)

Go to Download

A custom implementation of authentication in symfony, without user storage and very minimal configuration

Go to Download

Adds configurable workflow support to the CMS, with a GUI for creating custom workflow definitions.

Go to Download

A flexible way to handle Symfony flash messages. Supports Bootstrap2, Bootstrap3 and Foundation out-of-the-box. Easily configurable to support any other UI framework or custom CSS / Icons.

Go to Download

Drupal 8/9 module providing a custom entity type and a referencing paragraphs bundle to provide History/Timeline pages (no templates, styles and javascript inlcuded, just configuration and additional functionality)

Go to Download