jordanpagewhite - Drupal Planet

Non-admin roles adding/editing content using admin theme

Mon, 25 Jan 2016 00:00:00 +0000

I ran into a recent surprise while working with some content editors on an academic catalog website. I sat down with them to walk through some issues they experienced with speciic content editing tasks. To my surprise, when they went into the Edit view, ex. /node/1/edit, the university theme was still being used instead of the admin theme (I think I was using Seven or Admininal). I was pretty sure that I clicked the checkbox to use the admin theme on content editing pages on the Admin > Appearance page. Let me paste a screenshot below.

Drupal Features, Deployment Module, and Drush Aliases

Fri, 22 Jan 2016 00:00:00 +0000

Features allows you to bundle entities, and their configurations, into a feature module that is written to code. So, what is so great about that? Can't you accomplish the same functionality by building out your views, content types, etc. through the Drupal admin UI. Yes, you can, but all of the entities and configuration will be saved in the database, as opposed to in code. Saving your entities and configuration to code is an immense benefit, if not necessary, for Drupal sites that are deployed across multiple environments, and even more if there are multiple developers working on the site.

Drupal 8, hook_form_alter()

Mon, 18 Jan 2016 00:00:00 +0000

I am developing a Drupal 8 site right to manage scholarships and scholarship applications at the university. I wanted to add a bunch of custom fields to User and group them with the field_group module, but field_group generated an error that caused White Screen of Death (WSOD) upon adding a field group. I reported the error to the module maintainer, but he seemed to denounce the possibility that it generated an error in his response to me.