openeuropa / oe_media
Media features for the OpenEuropa project.
Installs: 122 022
Dependents: 7
Suggesters: 1
Security: 0
Stars: 4
Watchers: 21
Forks: 7
Open Issues: 11
Type:drupal-module
Requires
- php: >=8.1
- drupal/core: ^10
- drupal/embed: ^1.5
- drupal/entity_browser: ^2.5
- drupal/file_link: ^2.1
- drupal/inline_entity_form: ~1.0-rc12
- drupal/media_avportal: ^1.2
Requires (Dev)
- composer/installers: ~1.5
- cweagans/composer-patches: ^1.7 | ^2.0
- drupal/ckeditor: ^1.0
- drupal/composite_reference: ^2.2
- drupal/config_devel: ^1.9
- drupal/core-composer-scaffold: ^10
- drupal/drupal-extension: ^5.0
- drupal/entity_reference_revisions: ^1.7
- drupal/json_field: ^1.1
- drush/drush: ^12.4
- mikey179/vfsstream: ^1.6
- nikic/php-parser: ^4.18
- openeuropa/behat-transformation-context: ^0.2
- openeuropa/code-review: ^2.0.0-alpha6
- openeuropa/oe_link_lists: ^0.22
- openeuropa/oe_oembed: ~0.7.0
- openeuropa/oe_webtools: ^1.23
- openeuropa/task-runner-drupal-project-symlink: ^1.0-beta6
- phpspec/prophecy-phpunit: ^2
- symfony/phpunit-bridge: ^6.4
- dev-master
- 1.28.0
- 1.27.0
- 1.26.0
- 1.25.0
- 1.24.0
- 1.23.1
- 1.23.0
- 1.22.0
- 1.21.x-dev
- 1.21.2
- 1.21.1
- 1.21.0
- 1.20.0
- 1.19.0
- 1.18.0
- 1.17.0
- 1.16.0
- 1.15.0
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.1
- 1.10.0
- 1.9.0
- 1.8.0
- 1.7.0
- 1.6.0
- 1.5.0
- 1.4.0
- 1.3.0
- 1.2.0
- 1.1.0
- 1.0.0
- 1.0.0-beta5
- 1.0.0-beta4
- 1.0.0-beta3
- 1.0.0-beta2
- 1.0.0-beta1
- 0.4.0
- 0.3.0
- 0.2.0
- 0.1.0
- dev-EWPP-4984
- dev-release-1.28.0
- dev-contribution/UCPKN-3218
- dev-EWPP-3839
- dev-EWPP-3722
- dev-EWPP-3721
- dev-EWPP-0000
- dev-release-1.21.2
- dev-release-1.21.0
- dev-EWPP-2832
- dev-release-1.17.0
- dev-release-1.14.0
- dev-EWPP-847
- dev-EPIC-Media-iframe
- dev-EWPP-682
- dev-EWPP-483
- dev-EWPP-474
- dev-EWPP-284
- dev-EWPP-253
- dev-EWPP-32
- dev-EWPP-72
- dev-EWPP-95
- dev-OPENEUROPA-3047
- dev-EPIC-Link-lists-assets
- dev-OPENEUROPA-3234
- dev-OPENEUROPA-2818
- dev-release-1.6.0
- dev-OPENEUROPA-2659
- dev-SGECI2-370
- dev-OPENEUROPA-1766
- dev-OPENEUROPA-2258-test-php72
This package is auto-updated.
Last update: 2024-12-16 15:25:03 UTC
README
The OpenEuropa project uses media entities as a wrapper to any kind of assets such as images, documents, videos, etc. Therefore all asset field types should reference media entities rather than directly files.
The OpenEuropa Media module provides various functionality that allows using Media on your site.
The following types of Media (bundles) are currently available:
- Images (local)
- Documents (local)
- Remote videos (supports Youtube, Vimeo, Daily Motion)
- AV Portal videos and photos
- Video iframes
- Iframes
Additionally, there is a demo module inside that exposes a content type and a generic Entity Browser meant to demonstrate the usage of Media with content.
Permissions
The component provides a new permission called view any unpublished media
which is used when checking access to viewing unpublished media entities.
Table of contents:
Document media bundle
Out of the box, the Document media bundle provides the capability to upload a local document or choose a remote URL for the document, whose metadata will be pulled from that remote file (such as file type and size).
If you are updating from a version before 1.10.0
and you would like to benefit from the remote document capability, all you have to do is:
- Run the database updates as you normally would
- Edit the Document media form display and place the
File Type
andRemote File
fields below theName
field. The most common order would be:- Name
- File Type
- File
- Remote File
This will ensure the functionality kicks in.
Known Issues
- The Daily Motion video URLs in the Remote video bundles need to have the HTTP scheme (not HTTPs).
- The Daily Motion thumbnail URLs are typically without an extension so the local copy is not usable. This is fixed in #3080666 so if your version of Drupal core does not include that commit yet, you can apply the latest patch there.
Development setup
You can build the test site by running the following steps.
- Install all the composer dependencies:
composer install
- Customize build settings by copying
runner.yml.dist
torunner.yml
and changing relevant values, like your database credentials.
This will also:
- Symlink the theme in
./build/modules/custom/oe_media
so that it's available for the test site - Setup Drush and Drupal's settings using values from
./runner.yml.dist
. - Setup PHPUnit and Behat configuration files using values from
./runner.yml.dist
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 correctly symlinked.
If you don't want to re-run a full site setup for that, you can simply run:
$ ./vendor/bin/run drupal:symlink-project
- Install test site by running:
./vendor/bin/run drupal:site-install
Your test site will be available at ./build
.
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:
docker-compose up
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
:
docker-compose up -d
Then:
docker-compose exec web composer install docker-compose exec web ./vendor/bin/run drupal:site-install
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:
docker-compose exec web ./vendor/bin/grumphp run
To run the phpunit tests:
docker-compose exec web ./vendor/bin/phpunit
To run the behat tests:
docker-compose exec web ./vendor/bin/behat
Step debugging
To enable step debugging from the command line, pass the XDEBUG_SESSION
environment variable with any value to
the container:
docker-compose exec -e XDEBUG_SESSION=1 web <your command>
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/.
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.