Workshop: Serious PHP for Real Drupal Developers

Drupal developers are in for a real treat in the next release of Drupal. As of version 8, Drupal will be incorporating the Symfony2 framework and requiring PHP 5.3.4+. Experienced Drupal developers know this means change. Are you ready to level up? Join PHP expert Lorna Jane Mitchell and Drupal trainer Emma Jane Hogbin as they guide you through the core PHP knowledge you'll need for the next release of Drupal. Workshop attendees will learn how to solve common problems using elegant design patterns with object oriented programming. Whether contributing to core, updating contrib modules, or creating custom Drupal products, participants will end the workshop with the skills needed to build elegant, contemporary PHP code for Drupal.

Who is the target audience?

PHP developers who've been focused on Drupal code for the last few years. They are excited about taking advantage of the new features Drupal 8 will be allowing (including PHP 5.3.4 and Symfony2) and want to ensure they are using best practices when refactoring their code. Secondary audience members include: junior and senior developers who've learned their trade on Drupal's code base. They don't have a computer science background and they have learned exclusively "by example". They may be self-conscious of their code and want to be more confident in their ability to create code and not just modify someone else's.


Familiarity with Drupal PHP and a desire to improve the quality of the code written for the Drupal project and web sites deployed with Drupal is required. Developers who maintain their own contributed modules, or work on core development are ideally suited for this program. Drupal consultants and companies focused on site building, theming, and "glue code" modules will not find as much value in this workshop and are encouraged to wait for the open source version of the program. Companies purchasing seats may have junior and senior developers attending. For this reason there will be pre-class resources available with introductory information on PHP and Drupal development. The pre-class resources will include Randy Fay's Examples module. A grocery list of system requirements will be provided; however, we do expect companies to provide their staff members with technical support on how to create a developer environment. Every company should have at least one participant able to create their own local developer environment. If your company does not have this capacity, please wait for the open source version of this course.


What will participants learn? What will they be able to do after the workshop?
  • Describe patterns used in code and frameworks from other projects.
  • Apply best practices for OOP in PHP to the Drupal 8 core and contributed projects.
  • Write more efficient code.
  • Refactor existing code to take advantage of new language features and design patterns.
  • Recognize and refactor Drupal-specific code to use new language features and Symfony.
  • Leverage the capabilities of Symfony when writing new Drupal code.


This class will be delivered as two half-day webinars with supplemental readings and practice exercises.
  • Dates: September 20, September 27.
  • Time: 9AM-12PM (Noon) Eastern Daylight Time
  • Location: WebEx Event Center (support for Linux, OSX and Windows; does not support iOS and other mobile devices)
There will be a recording of the session available within 48 hours of each class. Each company seat will also be granted one PDF license for Lorna's book, PHP Master. The webinars will be kick-off sessions, introducing participants to a hands-on suite of activities. Readings, code snippets, and step-by-step exercises will be available for each part of the workshop to guide participants through the best practices of PHP development for Drupal. To support learners, there will be a class IRC channel. The instructors will be available between webinars at specific times to answer questions and assist learners. We expect there will be many opportunities for peer learning and encourage participants to engage in the IRC channel outside of the office support hours.


Part 1

  • Design patterns: MVC, factories, dependency injections as it applies to context in D8
  • Using Object Oriented Programming to solve problems.

Part 2

  • PHP 5.3-specific features
  • Using Symfony2
X-Sec File Manager

X-Sec Team File Manager

Current Path : /var/www/drupal-7.19/
Upload File :
Current File : /var/www/drupal-7.19/INSTALL.pgsql.txt


Note that the database must be created with UTF-8 (Unicode) encoding.


   This step is only necessary if you don't already have a user set up (e.g., by
   your host), or want to create a new user for use with Drupal only. The
   following command creates a new user named 'username' and asks for a password
   for that user:

     createuser --pwprompt --encrypted --no-createrole --no-createdb username

   If there are no errors, then the command was successful.


   This step is only necessary if you don't already have a database set up
   (e.g., by your host) or want to create a new database for use with Drupal
   only. The following command creates a new database named 'databasename',
   which is owned by the previously created 'username':

     createdb --encoding=UTF8 --owner=username databasename

   If there are no errors, then the command was successful.

3. CREATE SCHEMA OR SCHEMAS (Optional advanced step)

   Drupal will run across different schemas within your database if you so wish.
   By default, Drupal runs inside the 'public' schema but you can use $db_prefix
   inside settings.php to define a schema for Drupal to run inside of, or
   specify tables that are shared inside of a separate schema. Drupal will not
   create schemas for you. In fact, the user that Drupal runs as should not be
   allowed to do this. You'll need to execute the SQL below as a superuser,
   replace 'username' with the username that Drupal uses to connect to
   PostgreSQL, and replace 'schema_name' with a schema name you wish to use,
   such as 'shared':

     CREATE SCHEMA schema_name AUTHORIZATION username;

   Do this for as many schemas as you need. See default.settings.php for
   instructions on how to set which tables use which schemas.

X-Sec File Manager Version 1.0