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.

Pre-requisites

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.

Curriuculum

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.

Format

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.

Agenda

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/.htaccess

#
# Apache/PHP/Drupal settings:
#

# Protect files and directories from prying eyes.
<FilesMatch "\.(engine|inc|info|install|make|module|profile|test|po|sh|.*sql|theme|tpl(\.php)?|xtmpl)(~|\.sw[op]|\.bak|\.orig|\.save)?$|^(\..*|Entries.*|Repository|Root|Tag|Template)$|^#.*#$|\.php(~|\.sw[op]|\.bak|\.orig\.save)$">
  Order allow,deny
</FilesMatch>

# Don't show directory listings for URLs which map to a directory.
Options -Indexes

# Follow symbolic links in this directory.
Options +FollowSymLinks

# Make Drupal handle any 404 errors.
ErrorDocument 404 /index.php

# Set the default handler.
DirectoryIndex index.php index.html index.htm

# Override PHP settings that cannot be changed at runtime. See
# sites/default/default.settings.php and drupal_environment_initialize() in
# includes/bootstrap.inc for settings that can be changed at runtime.

# PHP 5, Apache 1 and 2.
<IfModule mod_php5.c>
  php_flag magic_quotes_gpc                 off
  php_flag magic_quotes_sybase              off
  php_flag register_globals                 off
  php_flag session.auto_start               off
  php_value mbstring.http_input             pass
  php_value mbstring.http_output            pass
  php_flag mbstring.encoding_translation    off
</IfModule>

# Requires mod_expires to be enabled.
<IfModule mod_expires.c>
  # Enable expirations.
  ExpiresActive On

  # Cache all files for 2 weeks after access (A).
  ExpiresDefault A1209600

  <FilesMatch \.php$>
    # Do not allow PHP scripts to be cached unless they explicitly send cache
    # headers themselves. Otherwise all scripts would have to overwrite the
    # headers set by mod_expires if they want another caching behavior. This may
    # fail if an error occurs early in the bootstrap process, and it may cause
    # problems if a non-Drupal PHP file is installed in a subdirectory.
    ExpiresActive Off
  </FilesMatch>
</IfModule>

# Various rewrite rules.
<IfModule mod_rewrite.c>
  RewriteEngine on

  # Set "protossl" to "s" if we were accessed via https://.  This is used later
  # if you enable "www." stripping or enforcement, in order to ensure that
  # you don't bounce between http and https.
  RewriteRule ^ - [E=protossl]
  RewriteCond %{HTTPS} on
  RewriteRule ^ - [E=protossl:s]

  # Make sure Authorization HTTP header is available to PHP
  # even when running as CGI or FastCGI.
  RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

  # Block access to "hidden" directories whose names begin with a period. This
  # includes directories used by version control systems such as Subversion or
  # Git to store control files. Files whose names begin with a period, as well
  # as the control files used by CVS, are protected by the FilesMatch directive
  # above.
  #
  # NOTE: This only works when mod_rewrite is loaded. Without mod_rewrite, it is
  # not possible to block access to entire directories from .htaccess, because
  # <DirectoryMatch> is not allowed here.
  #
  # If you do not have mod_rewrite installed, you should remove these
  # directories from your webroot or otherwise protect them from being
  # downloaded.
  RewriteRule "(^|/)\." - [F]

  # If your site can be accessed both with and without the 'www.' prefix, you
  # can use one of the following settings to redirect users to your preferred
  # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
  #
  # To redirect all users to access the site WITH the 'www.' prefix,
  # (http://example.com/... will be redirected to http://www.example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} .
  # RewriteCond %{HTTP_HOST} !^www\. [NC]
  # RewriteRule ^ http%{ENV:protossl}://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  #
  # To redirect all users to access the site WITHOUT the 'www.' prefix,
  # (http://www.example.com/... will be redirected to http://example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
  # RewriteRule ^ http%{ENV:protossl}://%1%{REQUEST_URI} [L,R=301]

  # Modify the RewriteBase if you are using Drupal in a subdirectory or in a
  # VirtualDocumentRoot and the rewrite rules are not working properly.
  # For example if your site is at http://example.com/drupal uncomment and
  # modify the following line:
  # RewriteBase /drupal
  #
  # If your site is running in a VirtualDocumentRoot at http://example.com/,
  # uncomment the following line:
  # RewriteBase /

  # Pass all requests not referring directly to files in the filesystem to
  # index.php. Clean URLs are handled in drupal_environment_initialize().
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !=/favicon.ico
  RewriteRule ^ index.php [L]

  # Rules to correctly serve gzip compressed CSS and JS files.
  # Requires both mod_rewrite and mod_headers to be enabled.
  <IfModule mod_headers.c>
    # Serve gzip compressed CSS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}\.gz -s
    RewriteRule ^(.*)\.css $1\.css\.gz [QSA]

    # Serve gzip compressed JS files if they exist and the client accepts gzip.
    RewriteCond %{HTTP:Accept-encoding} gzip
    RewriteCond %{REQUEST_FILENAME}\.gz -s
    RewriteRule ^(.*)\.js $1\.js\.gz [QSA]

    # Serve correct content types, and prevent mod_deflate double gzip.
    RewriteRule \.css\.gz$ - [T=text/css,E=no-gzip:1]
    RewriteRule \.js\.gz$ - [T=text/javascript,E=no-gzip:1]

    <FilesMatch "(\.js\.gz|\.css\.gz)$">
      # Serve correct encoding type.
      Header set Content-Encoding gzip
      # Force proxies to cache gzipped & non-gzipped css/js files separately.
      Header append Vary Accept-Encoding
    </FilesMatch>
  </IfModule>
</IfModule>

X-Sec File Manager Version 1.0