Drupal

DON'T HACK CORE! It's THE cardinal rule of Drupal. Like another rule, Don't eat yellow snow, it's inviolate...immutable...or is it? 

I was listening to Webchick's presentation on Upgrading YOUR Module to Drupal 8 (https://www.youtube.com/watch?v=wKdU2Q1NIZQ), following along with my own contributed module (https://drupal.org/project/node_theme) and when she reached a seemingly innocuous step

  • Installation:
    • drush dl drupalmoduleupgrader
    • cd drupalmoduleupgrader
    • composer install

I received the following response in my Mac terminal window

There are times when the connection to your Drupal DB will need to be via ssl, such as when using an external DB service like clearDB. How do you accomplish this with regards to the settings.php file?

Simple.

Add the following to your database array:

      'pdo' => array (

            PDO::MYSQL_ATTR_SSL_CERT => 'path-to-cert.pem',

            PDO::MYSQL_ATTR_SSL_KEY => 'path-to-key.pem',

            PDO::MYSQL_ATTR_SSL_CA => 'path-to-ca.pem',

To be, or not to be, that is the question. Shakespeare never quite gets around to answering it, though. In Drupal 7, a similar existential question arises regarding entity references: Is it, or is it empty? Unlike Will, we can answer this question.

I had an issue recently, where I was using a selector to add menu tabs to the edge of the content area. Getting them to appear wasn't the issue. Getting them NOT to appear on admin overlays was.

Pages

Subscribe to RSS - Drupal
©2005-2017 Ayen Designs. Underlying theme by Kiwi Themes.