Libraries tagged by cms functionality

awilum/craft-benchmark

3 Favers
101 Downloads

Simple benchmark plugin with basic benchmark functionality for Craft CMS.

Go to Download


agentmedia/phine-core

0 Favers
121 Downloads

The core bundle for the Phine CMS, including base backend functionality and an installer

Go to Download


s1lentium/craft-recurring-dates

1 Favers
29 Downloads

This is a plugin for the Craft CMS to add recurring dates functionality

Go to Download


obisconcept/neos-search

1 Favers
1392 Downloads

A Neos CMS package to add search functionality for NEOS 3.0.0.

Go to Download


hoppinger/preview_entity

0 Favers
0 Downloads

Drupal module to provide preview functionality to the Headless CMS

Go to Download


thefehr/reloquent

0 Favers
1 Downloads

A Redaxo CMS (v5) AddOn providing Eloquent functionalities

Go to Download


hofff/contao-newsletter-extended

1 Favers
16 Downloads

Extended newsletter functionality for Contao Open Source CMS.

Go to Download


devhub/admin-preview

0 Favers
4 Downloads

Admin Preview extension provides functionality to preview product, category and cms pages from backend.

Go to Download


kruegge82/jumingo

0 Favers
31 Downloads

## About With the JUMINGO shipping API you can import your shipments into your JUMINGO account from any source. The functionalities of the API include creating and updating shipment drafts, fetching suitable shipment rates for a given shipment and purchasing shipping labels. Furthermore, you can retrieve tracking data and fetch shipping labels and documents for all your purchased shipments. The current main purpose of the API is to connect your account to e-commerce systems and marketplaces. ## General The API is organized around REST. Our API has resource-oriented URLs and uses HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs. All API requests must be made over HTTPS. Calls made over plain HTTP will return errors. Request data is passed to the API as JSON objects and JSON is also returned by all API responses, including errors, although our API SDKs convert requests and responses to appropriate language-specific objects. Best practice usage of the API and business logic is described in the supplementary [integration guide](https://www.jumingo.com/cms/JUMiNGO_API-integration-guide.pdf "JUMiNGO API Integration Guide"). ## Base URL The base URL for all calls is: `https://api.jumingo.com/v1` ## HTTP status codes HTTP response codes in the `2xx` range indicate success. Codes in the `4xx` range indicate an error on the client side (e.g. a required parameter is missing). Codes in the `5xx` range indicate an error with our servers. Each error should provide an error code and an error message with further information. HTTP status code | Description ---------------- | ----------- 200, 201, 204 - OK | Everything worked. 400 - Bad Request | The request was unacceptable, often due to missing a required parameter or a validation error. 401 - Unauthorized | No valid API key has been provided or your account is disabled. 403 - Forbidden | You are not allowed to talk to this endpoint. This can either be due to a wrong authentication or when you’re trying to reach an endpoint that your account isn’t allowed to access. 404 - Not Found | The requested resource doesn’t exist. 500, 502, 503, 504 - Server Errors | Something went wrong on our side. Please contact our support if you receive this error. ## Authentication All API requests requires authentication. Unauthorized calls will return errors. Authenticate by including your API key in the `X-AUTH-TOKEN` HTTP header of each API call, e.g.: `X-AUTH-TOKEN: INSERT_YOUR_API_KEY` You can find your API key in your JUMINGO user account. You can get access to the JUMiNGO customer API by enabling it in your [user account](https://www.jumingo.com/de-de/users/connections/create/8). After activation, you will get your personal API key. ## Date/Time Format All values of type `string ` are defined in a specific [RFC 3339](https://tools.ietf.org/html/rfc3339#section-5.6) format and must also be formatted accordingly for requests. The format is: YYYY-MM-DD hh:mm:ss Example: 2018-07-26 15:54:13 All dates and times are specified in UTC (Coordinated Universal Time).

Go to Download


heimrichhannot/contao-multilingual-fields-bundle

1 Favers
163 Downloads

This utility bundle offers functionality for backend editor's to translate arbitrary fields of any table-driven data container in the Contao CMS.

Go to Download


heimrichhannot/contao-ldap-bundle

0 Favers
30 Downloads

This bundle offers functionality concerning LDAP servers for the Contao CMS.

Go to Download


heimrichhannot/contao-dc-multilingual-utils-bundle

0 Favers
375 Downloads

This bundle offers functionality concerning terminal42/contao-DC_Multilingual for the Contao CMS.

Go to Download


heimrichhannot/contao-amp-bundle

0 Favers
304 Downloads

This bundle offers functionality concerning "Accelerated Mobile Pages" (AMP) for the Contao CMS.

Go to Download


heimrichhannot/contao-alert-reminder-bundle

1 Favers
1504 Downloads

This utility bundle offers functionality to remind the backend users of existing alerts in the Contao CMS.

Go to Download


kalamu/cms-core-bundle

0 Favers
28 Downloads

Core functionalites for Kalamu CMS

Go to Download


<< Previous Next >>