openeuropa / oe_contact_forms
OpenEuropa Contact Forms module.
Installs: 62 847
Dependents: 3
Suggesters: 0
Security: 0
Stars: 0
Watchers: 19
Forks: 0
Open Issues: 3
Type:drupal-module
Requires
- php: >=8.1
- cweagans/composer-patches: ^1.4 || ^2
- drupal/contact_storage: ^1.3
- drupal/contact_storage_export: ^1.15
- drupal/core: ^10
- drupal/multivalue_form_element: ^1.0.0-beta6
- openeuropa/oe_corporate_countries: ^2.0.0-alpha8
- openeuropa/rdf_skos: ^1.0.0-alpha10
Requires (Dev)
- composer/installers: ^1.11
- drupal/core-composer-scaffold: ^10
- drupal/core-dev: ^10
- drupal/honeypot: ^2.1
- drush/drush: ^12
- openeuropa/code-review: ^2.0.0-alpha6
- openeuropa/task-runner-drupal-project-symlink: ^1.0-beta6
- phpspec/prophecy-phpunit: ^2
- dev-master
- 1.17.0
- 1.16.0
- 1.15.0
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 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.1
- 1.1.0
- 1.0.0
- 0.6.0
- 0.5.0
- 0.4.0
- 0.3.0
- 0.2.0
- 0.1.0
- dev-EWPP-4782
- dev-EWPP-0
- dev-EWPP-000-test
- dev-release-1.8.0
- dev-EWPP-2751
- dev-release-1.7.0
- dev-update-contact-storage
- dev-test
- dev-EWPP-1778
- dev-release-1.1.1
- dev-release-1.1.0
- dev-release-0.6.0
- dev-EWPP-176
This package is auto-updated.
Last update: 2024-09-25 11:34:43 UTC
README
This is a Drupal module that is an extension to drupal core contact forms and defines the European Commission corporate forms.
The OpenEuropa Contact Forms project provides storage for Contact messages in the form of fully-fledged entities using Contact Storage. This messages can then be automatically exported for each available Contact form.
Usage
Corporate contact form behaviour can be enabled on the contact form add/edit page, allowing form fields, confirmation message and email values to be defined.
Permissions
Granular permissions are exposed via contributed modules for handling contact forms and contact message entities:
- View contact messages
- Update contact messages
- Delete contact messages
- Export contact form messages
Development setup
Requirements
You can build the development site by running the following steps:
-
Install Virtuoso. The easiest way to do this is by using the OpenEuropa Triple store development Docker container which also pre-imports the main Europa vocabularies.
-
Install the Composer dependencies:
composer install
A post command hook (drupal:site-setup
) is triggered automatically after composer install
.
This will symlink the module in the proper directory within the test site and perform token substitution in test configuration files such as behat.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 be 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:
```bash
$ ./vendor/bin/run drupal:site-install
The development site web root should be available in the build
directory.
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.
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
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:
$ docker-compose exec sparql ./vendor/bin/robo purge
Or, if you can run commands on your host machine:
$ ./vendor/bin/run sparql:purge
Import default data:
$ docker-compose exec sparql ./vendor/bin/robo import
Or, if you can run commands on your host machine:
$ ./vendor/bin/run sparql:import
Reset all data, i.e. run purge and import:
$ docker-compose exec sparql ./vendor/bin/robo purge
$ docker-compose exec sparql ./vendor/bin/robo import
Or, if you can run commands on your host machine:
$ ./vendor/bin/run sparql:reset
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.