Download the PHP package liquidlight/typo3-media-gallery without Composer

On this page you can find all versions of the php package liquidlight/typo3-media-gallery. 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 typo3-media-gallery

TYPO3 Media Gallery

A plugin to show images with a list of different engines to display.

Installation

  1. composer req liquidlight/typo3-media-gallery
  2. Include the TypoScript, either by using static includes or including the files yourself
    • Constants: @import 'EXT:media_gallery/Configuration/TypoScript/constants'
    • Setup: @import 'EXT:media_gallery/Configuration/TypoScript/setup'
  3. Add a new gallery to a page & select images
  4. Pick your engine (library) or add your own
  5. Allow the following permissions (if required)
    • Tables (listing): File collection
    • Tables (modify): File collection
    • Page Content: File collections
    • Page Content: Type: [Allow] Media Gallery

Engines

Throughout this extension you will see and interact with the word "engine". This describes the library/package used to render the images. Examples of engines are Fancybox and Swiper. There is also an Ajax and Basic engine included which, by default, adds no extra CSS or JavaScript.

Configuration

Media Gallery comes bundled with several libraries included, which can all be configured via the $GLOBALS array to alter their behaviour. You also have the option of adding your own media gallery engine if desired.

Remove assets of an existing engine

If an existing or added engine includes assets which you, yourself, are bundling in your site package or FE assets, you can remove assets in various ways.

You can add the following to your ext_localconf.php:

Alternatively, you can unset() a specific item - e.g.:

Remove an engine

It might be that you don't want some (or any) of the default engines to be available. In which case, you can unset the entire engine.

For example, to remove the base & carousel engines:

Add an engine

Engines are set via $GLOBALS['TYPO3_CONF_VARS']['EXTCONF']['media_gallery']['engines'] and appended to the array.

The key should be a simple/slugified version of the engine/plugin. This allows unsetting and overriding should that be required.

The array can have several keys to add assets & define settings - all of them optional. See below for an explanation of the assets.

Adding a new engine

Assets

The 4 asset keys (styleSheet, javaScript, inlineStyleSheet, inlineJavaScript) allow you to load assets when the particular engine is loaded. Each one can take a string or a (multi-dimensional) array and is passed to the TYPO3 AssetCollector (docs).

Most of the time, the string will be enough, however there may be times where you need to set the priority or add data attributes.

This applies to all 4 assets, but as an example, the CSS can be formatted in 3 different ways:

As a string

As an array

As a multidimensional array

This allows you to set attributes and options as you would if using the AssetCollector directly

Templates

If you wish to override any partials, add the following to your constants.typoscript.

Alternatively, you can add them directly to the setup.typoscript

Note: The custom <gallery:assets engine="{engine}" /> view helper is how the assets are injected into the template - ensure your template contains this if overriding the Gallery.html

Upgrading

When upgrading from v3 (our internal, private package) to v4, please do the following:

Once deployed and upgraded on live:


All versions of typo3-media-gallery with dependencies

PHP Build Version
Package Version
Requires typo3/cms-core Version ^10.4 || ^11.5
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 liquidlight/typo3-media-gallery contains the following files

Loading the files please wait ....