Download the PHP package openeuropa/oe_content without Composer

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

OpenEuropa Content

This is a Drupal module that contains the European Commission corporate entity types.

The module uses the RDF SKOS module to provide SKOS modelling for the Publications Office taxonomy vocabularies. These are directly made available in the dependent RDF triple store.

All content types are organised into sub-modules. These content types can be set to be translatable by overriding the language.content_setting configuration.

This module provides a sub-module (oe_content_entity) with a set of Corporate content entities to be used. Check out the README of the module.

Table of contents:

Requirements

This depends on the following software:

Installation

Install the package and its dependencies:

It is strongly recommended to use the provisioned Docker image for Virtuoso that contains already the OP vocabularies. To do this, add the image to your docker.compose.yml file:

Otherwise, make sure you have the triple store instance running and have imported those vocabularies.

Next, if you are using the Task Runner to set up your site, add the runner.yml configuration for connecting to the triple store. Under the drupal key:

Still in the runner.yml, add the instruction to create the Drupal settings for connecting to the triple store. Under the drupal.settings.databases key:

Then you can proceed with the regular Task Runner commands for setting up the site.

Otherwise, ensure that in your site's setting.php file you have the connection information to your own triple store instance:

Usage

OpenEuropa Content

If you want to use OpenEuropa Content, enable the module:

OpenEuropa Corporate Site Info integration

This module provides an integration with the OpenEuropa Corporate Site Information module.

When creating a new node if the fields "Content Owner" and "Authors" are avilable they will be automatically populated with the values configured as "Default content owner" in the "Basic site settings" provided by the OpenEuropa Corporate Site Info module.

Development setup

Requirements

Initial setup

You can build the test site by running the following steps.

This will also symlink the theme in the proper directory within the test site and perform token substitution in test configuration files such as behat.yml.dist.

Your test site will be available at ./build.

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:

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/.

Working with content

The project ships with the following Task Runner commands to work with content in the RDF store, they require Docker Compose services to be up and running.

Purge all data:

Or, if you can run commands on your host machine:

Import default data:

Or, if you can run commands on your host machine:

Reset all data, i.e. run purge and import:

Or, if you can run commands on your host machine:

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_content with dependencies

PHP Build Version
Package Version
Requires php Version >=8.1
cweagans/composer-patches Version ^1.7 | ^2.0
drupal/core Version ^10
drupal/datetime_range_timezone Version ^1.0.0-alpha3
drupal/linkit Version ^6.0.0-beta4
drupal/maxlength Version ^3.0.0-beta1
openeuropa/oe_media Version ^1.23.1
openeuropa/rdf_skos Version ^1.0.0-alpha10
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_content contains the following files

Loading the files please wait ....