Download the PHP package terminal42/contao-bynder without Composer

On this page you can find all versions of the php package terminal42/contao-bynder. 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?

Informations about the package contao-bynder

terminal42/contao-bynder

This bundle integrates Bynder Asset Management directly into your Contao 5.3+ back end. It works by adding new tab next to the regular file picker tab where you can choose your images of your Bynder Asset Management account. You can search and filter your Bynder assets, download and then select them right from the file tree widget.

You can configure which metadata should be imported and how and the bundle also takes care to map your configured Bynder focus point to Contao's important path configuration.

Why would I need this, if it still downloads all the files to the system?

This approach still has one big advantage which is that you can manage your files in one central location and use it across multiple content management systems or even multiple Contao setups.

Roadmap / Ideas

Installation

1) Install the bundle

2) Configure the bundle

Edit your config.yml file and add the necessary configuration parameters as follows:

With the metaImportMapper you can configure the way you want to import metadata from Bynder to Contao's metadata widget. The key is the language. In our example this is de but you can also specify multiple languages, if you wanted to. This bundle automatically converts your custom media properties and fetches the correct values based on the language for it. It will also check if the media property is configured to allow multiple or only single values. So you don't have to worry about converting arrays with only one value into a string. The templates expect a valid Twig string.

3) Configure your Bynder Account

Bynder can handle huge file assets that do not even make sense in a web environment such as a 750 MB TIFF image. However, Bynder knows the concept of "derivatives". Derivatives are variations of the original image. They allow you to create e.g. a 3000 x 3000 pixel JPEG file from your 750 MB TIFF file. You can ask Bynder to create them every time a user uploads a file or you can create so called on-the-fly derivatives.

You have to tell the bundle which derivative it shall take by passing the name to the configuration as follows:

On-the-fly derivatives even allow any third party application to override the desired parameters. Go and have a look at the "Supported parameters" section in the Bynder knowledge base to see how you can override these. The terminal42_contao_bynder.derivativeOptions setting takes a key value array which it will append when fetching a derivative to do exactly that. We recommend to use the following setting:

This will create an image of decent size and it will not crop it but keep the original proportions which is usually what you want to have. You absolutely do not need to pass this configuration. You can also create a derivative only for this integration and name it e.g. "contao_bynder_integration" and configure the settings already there.

Upgrade from 1.x to 2.x

In order to upgrade the extension to version 2, you need to take the following steps:

  1. Obtain the permanent token as described on https://support.bynder.com/hc/en-us/articles/360013875300-Permanent-Tokens
  2. Update the config.yml file as follows:

All versions of contao-bynder with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
ext-mbstring Version *
contao/core-bundle Version ^5.3
bynder/bynder-php-sdk Version ^2.1
doctrine/dbal Version ^3.0
symfony/http-client Version ^6.4
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 terminal42/contao-bynder contains the following files

Loading the files please wait ....