Drupal 8: geolocation base fields on custom entity types

I had a requirement to be able to record lots of different types of "Point of Interest", that will require varying fields but have a common requirement to store location across them all. So, my solution would be to create a custom content entity type that supported bundles, where the base entity type had geolocation (and a couple of other things) as base fields.

To achieve the scenario above, I created a content entity class as below:

Simple OAuth 8.x-2.x

Simple OAuth is an implementation of the OAuth 2.0 Authorization Framework RFC. Using OAuth 2.0 Bearer Token is very easy. See how you can get the basics working in less than 5 minutes! This project is focused in simplicity of use and flexibility. When deciding which project to use, also consider other projects like OAuth, an OAuth 1 implementation that doesn't rely on you having https in your production server.

Media + CKEditor + Media CKEditor recipe for setup

---
# This is a drush make file for a media_wysiwyg setup using the CKEditor
# module.
#
# Build this recipe with this drush command:
# drush make /path/to/this/file --no-core /path/to/destination/folder
#
# After downloading and moving files into place, here are the manual steps
# needed to set everything up:
#
# 1. If Drupal is not already installed, install Drupal with the standard
#    profile: drush site-install
# 2. Enable these modules:
#    - media_ckeditor
#    - token
#    - media_oembed

Setup Cron Jobs

What's particularly interesting in DRD is to have an overview on domains, their status and their project update information. To keep all this up-to-date automatically, the following set of cron jobs is a possible recommendation:

Webform 8.x-5.x: How to move status messages under the progress bar

You can add '#type': status_messages to your form elements' source view. (see the attached webform)

This approach will create duplicate messages. (see below)

Pages

Subscribe with RSS Subscribe to RSS - Intermediate