Download the PHP package wieni/wmsettings without Composer

On this page you can find all versions of the php package wieni/wmsettings. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of wieni/wmsettings

Informations about the package wmsettings

wmsettings

Latest Stable Version Total Downloads License

Provides an Editor UI and Developer API for managing custom settings

Why?

Provides an Editor UI and Developers API for setting/getting content that needs to be all over the place but isn't exactly config, and isn't exactly entity stuff.

How does it work?

Technically you create config keys (eg global or site-settings). This key gets linked directly to exactly one bundle in the settings entity type.

Developers are free to create bundles/fields in the entity type settings themselves, and create keys to refer to them.

Adding configs

On /admin/config/wmsettings one can add settings. A setting effectively links a machine name to a specific entity id. The entity gets autocreated.

You can also add configs by directly writing config files I suppose, for the brave that feel up to it. Just follow the wmsettings.schema.yml for that.

Editor UI

The administrative interface for editors is at admin/content/wmsettings. Note that:

Developers API

There are several ways to access the entity for a key.

1. The service.

2. The module function.

3. The fill function.

Returns a quick flattened array of all values in a setting, given field names and field types. Not a lot of field types are supported now.

Adding Tabs (local tasks) to settings for your custom routes

Drupal requires at least two tasks to show them, so for the sake of completeness this example loads two tasks too:

Changelog

All notable changes to this project will be documented in the CHANGELOG file.

Security

If you discover any security-related issues, please email [email protected] instead of using the issue tracker.

License

Distributed under the MIT License. See the LICENSE file for more information.

All versions of wmsettings with dependencies

PHP Build Version
Package Version
Requires php Version >=7.1
drupal/core Version ^9.2 || ^10.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package wieni/wmsettings contains the following files

Loading the files please wait ....