DrupalCon 2011: Feedback ENTICE meeting 8 April 2011 Silvia Tomanin DG-CO

DrupalCon April 20112DrupalCon 2011: Feedback Website: Session list: Videos: %20chicago% %20chicago% sessions for coders. Next DrupalCon: London Aug 2011London Aug 2011

Session 1: development Introduction to module development Often you don't need to start from scratch: remember to check if there's already a module that is doing what you need or part of it. Recommendations (use Devel, optimized API search) Introduction on Drupal hooks 8 April 20113DrupalCon 2011: Feedback

Session 2: security Drupal security for coders Read the documentation Handle strings safely (check_url(), check_plain(), check_markup(), filter_xss()) User protect module Secure code review module (dev)Secure code review module 8 April 20114DrupalCon 2011: Feedback

Session 3: from D6 to D7 Coder Module: easily port modules to D7 Coder is for code review. Do you need to port a D6 module to D7? Use coder upgrade module, it helps. Automatic conversion of many functions from D6 to D7. Careful: still work in progress (beta6 released). 8 April 20115DrupalCon 2011: Feedback

Session 4: testing Automated testing and Drupal Simpletest is D7 core. How to run Simpletest: Via UI Via Drush How to write and run a test Other tools: Yslow, GooglePageSpeed, NetExport (for Firebug), Jmeter, Selenium 8 April 20116DrupalCon 2011: Feedback

Session 5: performaces Drupal module coding: leaner techniques for faster websites PHP performances: n of source files, memory utilization (deallocate unneeded structures!), db queries (use static cache, load in variables, use exportable configurations > CTools). Use PHP 5.3 (better performances) Do not split very small modules! 8 April 20117DrupalCon 2011: Feedback

Session 6: performaces Test, tune, tweak, hack, repeat: industrial- strenght performance and scalability Testing Xdebug, Tracelytics, Coder review Tuning &Tweaking Refactoring: reduce node loads, reduce dependencies on views, pass by reference to reduce memory, optimize css Hacking core : don’t do it if possible! 8 April 20118DrupalCon 2011: Feedback

Session 7: usability Drupal usability for developers: how to get real people to love your work Don’t do it alone: check the guidelinesguidelines D7 dashboard (many improvements from D6) D7 modules: Signup (ex. allows users to associate themselves with a node), Views (ex. how to display contextual links), CTools 8 April 20119DrupalCon 2011: Feedback

Session 8: Git Git on Drupal.org How to configure Git to contribute to the Drupal community Git documentation No need for approval for new Drupal projects Possibility to assign different roles for different Drupal users to contribute at the same project 8 April DrupalCon 2011: Feedback

Session 9: Drush Advanced Drush What is it? Drupal command line $drush site-install $drush clear-cache $drush pml --type=module --status=enabled --no-core Scripting with Drush New commands $drush node-show 3 / $drush node-delete 3 (--json) $drush node-edit 3 8 April DrupalCon 2011: Feedback

Session 10: search Attain Apache SOLR coding chops How to configure and run SOLR on localhostSOLR Fields and Dynamic Fields schema Solr integrations for Drupal: differences and versions available ApacheSolr integration (beta4 for D7) can do multi-site searches 8 April DrupalCon 2011: Feedback

Session 11 Aphorism of API design Use watchdog for faster debugging! Fail early, fail often: constrain input Again, do not implement something already existing Use standards Use simpletest for testing 8 April DrupalCon 2011: Feedback

Session 12 Views for hackers How to code views: conceptual overview Views: file and folder structure Difference between filters and arguments Examples Pretty advanced: if you need a plugin for views it’s better waiting for someone else to write it. 8 April DrupalCon 2011: Feedback

Questions? ? 8 April DrupalCon 2011: Feedback