Download the PHP package openeuropa/oe_whitelabel without Composer
On this page you can find all versions of the php package openeuropa/oe_whitelabel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download openeuropa/oe_whitelabel
More information about openeuropa/oe_whitelabel
Files in openeuropa/oe_whitelabel
Package oe_whitelabel
Short Description OpenEuropa Whitelabel theme.
License EUPL-1.2
Informations about the package oe_whitelabel
The OpenEuropa Whitelabel theme
Sub-theme of OpenEuropa Bootstrap base theme, with theming for OpenEuropa library features.
Features
Paragraphs
The paragraphs below are not yet themed therefore not recommended for usage:
- Contextual navigation
- Document
Some paragraphs are considered "internal", and only meant to be used inside other paragraphs:
- Listing item: To be used as item paragraph within 'Listing item block'.
- Fact: To be used as item paragraph within 'Facts and figures'.
Usage as a dependency
Website projects can use oe_whitelabel
either as an active theme, or they can create a custom theme using oe_whitelabel
as a base theme.
Requirements
The package is meant for Drupal projects that manage their dependencies with Composer.
Ideally this project should be managed with Docker and Docker Compose, but this is not a hard requirement.
Check the composer.json for required PHP version and other dependencies.
Add the composer package
Add this manually in composer.json, or combine with existing entries:
While this package is still in its alpha
phase, you need an extra step in composer, to avoid getting anything from the obsolete and unsupported 0.x
branch.
One option is to set minimum-stability
and require the ^1.0
version.
You should also set prefer-stable
to mitigate the impact on other dependencies.
Review this again when the site goes into production.
Alternatively, if you don't want to set minimum-stability
, you need to specify explicit versions for all dependencies with alpha versions:
Review the installed package versions.
Enable and configure
Enable required and optional submodules:
Enable the theme and set as default:
Development setup
Using LAMP stack or similar
This is not officially supported. You are on your own.
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.
Start the container
If you have other (daemonized) containers running, you might want to stop them first:
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
:
Optionally purge existing installation
If you already had the package installed, and want a clean start:
Install the package
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 or http://web:8080/build.
Run the tests
To run the grumphp checks:
To run the phpunit tests:
Upgrade from older versions
Upgrade to 1.0.0-alpha7
Paragraphs migration
Paragraphs-related theming and functionality has been moved from the OpenEuropa Bootstrap base theme to OpenEuropa Whitelabel.
Special paragraphs fields that were introduced in oe_bootstrap_theme_paragraphs
are being renamed in oe_whitelabel_paragraphs
.
If you have the oe_paragraphs
module enabled, you should create a hook_post_update_NAME()
in your code, to enable the oe_whitelabel_paragraphs
module during deployment.
This is needed to make sure that the install hook for oe_whitelabel_paragraphs
runs before config-import during a deployment.
Note that drush updb
will also trigger update hooks in oe_bootstrap_theme_helper
, which will uninstall the legacy module oe_bootstrap_theme_paragraphs
.
Upgrade to 1.0.0-alpha6
This release contains some bugs, please move directly to alpha7.
All versions of oe_whitelabel with dependencies
cweagans/composer-patches Version ^1.7
drupal/core Version ^10
drupal/daterange_compact Version ^2.0.1
drupal/twig_field_value Version ^2.0.2
openeuropa/composer-artifacts Version ^1.0.0-alpha1
openeuropa/oe_bootstrap_theme Version ^1.17