Contact us or author and report

By Daniel Berthereau Add a site page block with a ”Contact us” form, a link to report an issue on a resource and manage messages from admin.
Download 3.3.8.12

Contact us (module for Omeka S)

New versions of this module and support for Omeka S version 3.0 and above are available on GitLab, which seems to respect users and privacy better than the previous repository.

Contact us is a module for Omeka S that allows to add a site page block with a "Contact us" form. The messages are sent by email to the admin but can be read directly in the interface too. The form is fully available by api too, so it can be used by a third party client. It's possible to send a mail to the author of a resource too.

Installation

First, install the two optional modules Generic and Blocks Disposition.

Uncompress files and rename module folder ContactUs. Then install it like any other Omeka module and follow the config instructions.

See general end user documentation for Installing a module.

Quick start

The form can be placed anywhere in the site.

Config

Fill the options in the main settings, the site settings and the page block.

For subjects and messages, you can use placeholders for customization. They should be wrapped with { and }: "from", "email", "name", "site_title", "site_url", "subject", "message", "ip", "newsletter". When there is a resource, you can use too "resource_id", "resource_title", "resource_url", and any property term, like "dcterms:date". Note that the property should exist in all cases, else it won't be filled.

Static pages

Create a site page and add the block "Contact us".

The simple antispam is a simple list of questions and answers for the visitor.

The block is themable: copy the file common/block-layout/contact-us.phtml in your theme.

When submitted, the site admin will receive the email, and a confirmation email will be sent to the visitor.

If you want to use the "Contact us" page in all your sites, you can use the module Block Plus, that has a special block to duplicate a page in multiple places.

Resource pages

The form is displayed automatically on item set, item or media show pages. The settings can be set for each site.

To manage the display more precisely, use the module Blocks Disposition, or add the following code in your theme:

echo $this->contactUs(['resource' => $resource]);

The partial is themable: copy the file common/contact-us.phtml in your theme.

Admin interface

The contact us list of message is available in the left sidebar and can be managed: mark read, set spam, delete.

Development

Testing

Install Omeka with dev dependencies first.

# From module directory.
composer install
../../vendor/bin/phpunit --testdox --configuration /var/www/html/modules/ContactUs/test/phpunit.xml

Api

Any user can create a message:

curl -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' -i 'https://example.org/api/contact_messages?key_identity=xxx&key_credential=yyy&pretty_print=1' --data '{"o:email":"alpha@beta.com","o-module-contact:body":"message"}'

Or with a file (via a form):

curl -X POST -H 'Accept: application/json' -i 'https://example.org/api/contact_messages?pretty_print=1' -F 'data={"o:email":"alpha@beta.com","o-module-contact:body":"message"}' -F 'file[0]=@/home/user/my-file.jpeg'

Or with a base64-encoded file inside the json payload:

curl -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' -i 'https://example.org/api/contact_messages?key_identity=xxx&key_credential=yyy&pretty_print=1' --data '{"o:email":"alpha@beta.com","o-module-contact:body":"message","file":[{"name":"filename.txt","base64":"T21la2EgUw=="}]}'

Available keys are: - o:owner: generally useless, because the user is already authenticated. - o:email: required for anonymous people. - o:name - o-module-contact:subject: recommended. - o-module-contact:body: required message. - o-module-contact:newsletter: true or false. - file: only one file is currently managed. Useless when the file is sent via a posted form.

The owner or the email is useless when the user is already authenticated and is skipped in that case, except if the user has the right to change the owner of a message.

TODO

  • [ ] Fix consent label.

Warning

Use it at your own risk.

It’s always recommended to backup your files and your databases and to check your archives regularly so you can roll back if needed.

Troubleshooting

See online issues on the module issues page on GitLab.

License

This module is published under the CeCILL v2.1 license, compatible with GNU/GPL and approved by FSF and OSI.

In consideration of access to the source code and the rights to copy, modify and redistribute granted by the license, users are provided only with a limited warranty and the software’s author, the holder of the economic rights, and the successive licensors only have limited liability.

In this respect, the risks associated with loading, using, modifying and/or developing or reproducing the software by the user are brought to the user’s attention, given its Free Software status, which may make it complicated to use, with the result that its use is reserved for developers and experienced professionals having in-depth computer knowledge. Users are therefore encouraged to load and test the suitability of the software as regards their requirements in conditions enabling the security of their systems and/or data to be ensured and, more generally, to use and operate it in the same conditions of security. This Agreement may be freely reproduced and published, provided it is not altered, and that no provisions are either added or removed herefrom.

Copyright

  • Copyright Daniel Berthereau, 2018-2022 (see Daniel-KM on GitLab)
Version Released Minimum Omeka version
3.3.8.12August 22, 2022 [info]^3.1.0
3.3.8.10May 30, 2022 [info]^3.1.0
3.3.8.9May 16, 2022 [info]^3.1.0
3.3.8.8March 21, 2022 [info]^3.1.0
3.3.8.7March 07, 2022 [info]^3.1.0
3.3.8.4March 01, 2021 [info]^3.0.0
3.3.8.3February 08, 2021 [info]^3.0.0
3.3.8.2January 04, 2021 [info]^3.0.0
3.3.8.1January 04, 2021 [info]^3.0.0
3.3.8October 26, 2020 [info]^3.0.0
3.0.8March 15, 2020 [info]^1.2.0 || ^2.0.0
3.0.7February 23, 2020 [info]^1.2.0 || ^2.0.0
3.0.6November 24, 2019 [info]^1.2.0 || ^2.0.0
3.0.5November 04, 2019 [info]^1.2.0 || ^2.0.0
3.0.4November 03, 2019 [info]^1.2.0 || ^2.0.0
3.0.2July 21, 2019 [info]^1.2.0