drupal

Outline

1. Introduction
2. Infrastructure outline
3. Terraform concepts
4. Code overview
5. Applying the code

Introduction

I've been working with Drupal since 2015 so I've got a pretty good grasp on it and I feel I can confidently advise a client on how best to utilize it.

This is a continuation of a previous post. If you haven't read it I suggest that you do so before reading further, otherwise you won't understand the context.

This is the first part in a series of posts that I have written on this topic. In this first post I will discuss the reasons why I ported the module to Drupal 8 and some of the more basic module code (YAML files and forms). In the next post I will go over the Plugin system, how to write a custom Plugin, and how to implement the Batch API.

Introduction

I was recently given a requirement by a client in which they wanted content authors to be able to find and replace instances of words across potentially every piece of content in the site. This is a request that I've received in the past and have been able to solve the problem with relative ease. In Drupal 7 (D7) there is a module called scanner, which does exactly what they needed.

I gave a presentation on Drupal pre-reqs: What you need to know before you start learning Drupal at DrupalCamp Atlanta on October 22nd, 2016. See below for the abstract of the presentation, and all the resources, including the slides and screencast videos.

Abstract

Migrating content and its linkages between sites has always been one the more difficult tasks to master in the world of Drupal. In the past, site builders and developers would have to write lots of code to set up the migrations and field mappings. Migrating between Drupal sites is not quite as daunting of a task as migrating a site from another CMS, since many of the entities will be similar across sites, but is challenging none the less.

In Drupal, sometimes, you want to share user profiles with the world, but then they can also see the "History" and the "Member for" information about your users. If that information is not what you want to show the world, then all you have to do is implement hook_preprocess_user_profile and apply appropriate permissions to it.

Have you ever desired to have display of different View filter criteria depending on the user's role? There are two ways of achieving this, I will explain both the ways in this article. 

In following example, I want to show 4 search criteria to a user with administrator role: Event title, Date of Event, Location, Event status.  Further, I want to show two search criteria to all other roles: Event title and Location (shown in below images) . 

Welcome to the newly redesigned SpinSpire.com. It was on Drupal and it is still on Drupal, only better. We here at SpinSpire believe in eating our own dogfood. So we re-built our own site the way we would (re)build a client's site.