Download the PHP package openeuropa/oe_multilingual without Composer

On this page you can find all versions of the php package openeuropa/oe_multilingual. 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 oe_multilingual

OpenEuropa Multilingual

Build Status

The OpenEuropa Multilingual module offers default multilingual features for the OpenEuropa project, like:

Table of contents:

Installation

The recommended way of installing the OpenEuropa Multilingual module is via Composer.

Enable the module

In order to enable the module in your project run:

Development

The OpenEuropa Multilingual project contains all the necessary code and tools for an effective development process, such as:

Project setup

Download all required PHP code by running:

This will build a fully functional Drupal test site in the ./build directory that can be used to develop and showcase the module's functionality.

Before setting up and installing the site make sure to customize default configuration values by copying runner.yml.dist to ./runner.yml and overriding relevant properties.

This will also:

Please note: project files and directories are symlinked within the test site by using the OpenEuropa Task Runner's Drupal project symlink command.

If you add a new file or directory in the root of the project, you need to re-run drupal:site-setup in order to make sure they are be correctly symlinked.

If you don't want to re-run a full site setup for that, you can simply run:

After a successful setup install the site by running:

This will:

Using Docker Compose

Alternatively, you can build a development site using Docker and Docker Compose with the provided configuration.

Docker provides the necessary services and tools such as a web server and a database server to get the site running, regardless of your local host configuration.

Requirements:

Configuration

By default, Docker Compose reads two files, a docker-compose.yml and an optional docker-compose.override.yml file. By convention, the docker-compose.yml contains your base configuration and it's provided by default. The override file, as its name implies, can contain configuration overrides for existing services or entirely new services. If a service is defined in both files, Docker Compose merges the configurations.

Find more information on Docker Compose extension mechanism on the official Docker Compose documentation.

Usage

To start, run:

It's advised to not daemonize docker-compose so you can turn it off (CTRL+C) quickly when you're done working. However, if you'd like to daemonize it, you have to add the flag -d:

Then:

Using default configuration, the development site files should be available in the build directory and the development site should be available at: http://127.0.0.1:8080/build.

Running the tests

To run the grumphp checks:

To run the phpunit tests:

To run the behat tests:

Step debugging

To enable step debugging from the command line, pass the XDEBUG_SESSION environment variable with any value to the container:

Please note that, starting from XDebug 3, a connection error message will be outputted in the console if the variable is set but your client is not listening for debugging connections. The error message will cause false negatives for PHPUnit tests.

To initiate step debugging from the browser, set the correct cookie using a browser extension or a bookmarklet like the ones generated at https://www.jetbrains.com/phpstorm/marklets/.

Disable Drupal 8 caching

Manually disabling Drupal 8 caching is a laborious process that is well described here.

Alternatively you can use the following Drupal Console commands to disable/enable Drupal 8 caching:

Note: to fully disable Twig caching the following additional manual steps are required:

  1. Open ./build/sites/default/services.yml

  2. Set cache: false in twig.config: property. E.g.:

  3. Rebuild Drupal cache: ./vendor/bin/drush cr

This is due to the following Drupal Console issue.

Demo module

The OpenEuropa Multilingual module ships with a demo module which provides all the necessary configuration and code needed to showcase the modules' most important features.

The demo module includes a translatable content type with automatic URL path generation.

In order to install the OpenEuropa Multilingual demo module follow the instructions or enable it via Drush by running:

Known Issues

Enabling string English string translation

Enabling English string translation can have unintended consequences when making changes to translatable configuration entities. If these strings are available in locale, the change would get saved as EN translations.

Enabling URL suffix

This is optional and should be done only if your website should follow the IPG rules for language negotiation.

In order to use this feature you need to enable the OpenEuropa Multilingual URL Suffix module by following these instructions or via Drush by running:

After enabling the module:

  1. Go to admin/config/regional/language/detection
  2. Disable the URL method in Interface text language detection and Content language detection;
  3. Enable the URL suffix method in Interface text language detection and Content language detection;
  4. Make sure that the URL suffix method is located on top of list but after the Administration pages negotiation method, if you use it
  5. Save new order
  6. If necessary configure the URL suffix method by clicking on Configure
  7. Rebuild cache

URL suffix usage

Contributing

Please read the full documentation for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the available versions, see the tags on this repository.

All versions of oe_multilingual with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
drupal/core Version ^10.3 || ^11
drupal/language_selection_page Version ^3.0
drupal/pathauto Version ^1.12
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 openeuropa/oe_multilingual contains the following files

Loading the files please wait ....