Libraries tagged by sections

A PHP client for the Asana API expanded with sections

Go to Download

This package is use of Create new Reservation based on available time slots & meals and also assigned the table accordingly section with different payment gateway method.

Go to Download

Classes for simplifying the creation of theme options, option sections, & option pages.

Go to Download

Classes for simplifying the creation of general settings options, sections, & pages.

Go to Download

Promo Widget extension for Magento 2. Adds Widget Banner section for Sales Promo Quote edit form.

Go to Download

Magento extension. Email subscription opt-ins at onepage checkout in review order section.

Go to Download

Creates Symlinks and can be used with your composer in the scripts section

Go to Download

Magento 2 Add custom text under the 'ship to' section of order summary page on checkout page

Go to Download

Display applied patches in the footer of the Admin section

Go to Download

Provides Multi SiteTree sections in SilverStripe CMS

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.44) is used. For example, calling `/info` is the same as calling `/v1.44/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

This library is an implementation of the skeleton function described in the Confusion Detection section of the Unicode Security Mechanisms technical standard.

Go to Download

Adds single field to CMS settings section to hold GA or GTM code. Template snippets need to be inserted to theme templates manually.

Go to Download

This will allow us to to view and administer the contact information section of the framework

Go to Download

This will allow us to view and administer the blog section of the framework

Go to Download