Your SlideShare is downloading. ×
Drupal Deployment Troubles and Problems
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Drupal Deployment Troubles and Problems


Published on

Drupal Camp Kyiv2010 ( presentation about Troupbles and Problems during Deployment Drupal projects

Drupal Camp Kyiv2010 ( presentation about Troupbles and Problems during Deployment Drupal projects

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Drupal DTP
    Troubles and Problems
    @landike (Andrii Lundiak)
  • 2. Deployment steps
  • 3. Steps level
  • 4. What we have today to discuss
    Hosting environment worries
    First install steps
    Magic php.ini
    This very helpful .htaccess file
    We all like settings.php
    Strange unbelievable error messages
    Let find more Troubles and more Problems and Ways how to fix them.
  • 5. Useful MySQL stuff
    • mysqlimport --password=mypass --user=myuserdbname dbname.sql;
    • 6. mysql -h DBSERVER -p -u username dbname < dbname.sql
    • 7. mysqldump-u username -p dbname > dbname.sql
    • 8. mysql -h DBSERVER -p -u username dbname > dbname.sql
    Usemysql.cnffile to run easier
    user = myuser
    password = mypass
    host = DBSERVER
    database = dbname
    mysql< dbname.sql
  • 9. Log Files
    It's good to know what we have on hosting server and especially where Log files are.
    To access the files directly on the server, on some Unix shells, you can type the following command:
    tail -f /var/log/apache2/error.log
    To check that you are looking at the right file, you may wish to type the following commands to find where the log files are.
    grep 'ErrorLog' /etc/apache2/*
    grep 'ErrorLog' /etc/apache2/*/*
  • 10. Error Reporting
    If error reporting is turned off, you could be getting a fatal error but not seeing it. On a production site, it is common to have error reporting turned off.
    Take care to have in index.php:error_reporting(E_ALL);ini_set('display_errors', TRUE);ini_set('display_startup_errors', TRUE);
    this will help in debug/test mode
  • 11. Install and Go
    Create Database … and enjoy easy installation
    If some php settings are not in properly state, install process will tell you (about register_globals, mbstring.http_output, safe_mode, etc.)
  • 12. php.ini magician
    How to override php settings:
    value of a configuration option in php.ini
    .htaccess directives
    using ini_set() in settings.php
    or use control panel on your hosting server
    or call to admin person
    or change hosting server 
  • 13. Another way to override
    If you have access to php.ini it’s AWESOME, and It’s great if you have your own php.ini near by www
    On some hosting servers such kind of option is used to enable using local php.ini file:
    ssuPHP_ConfigPath /hsphere/local/home/sitelocation
    This setting must be located in .htaccess file
    And php.ini file must exists in /hsphere/local/home/sitelocation/php.ini
  • 14. Allowed memory size …
    Fatal error: Allowed memory size of X bytes exhausted (tried to allocate Y bytes)...
    Increase PHP's memory limit, up to 16MB or 24M or 32MB or especially 96MB for a site with built-in image processing using ImageAPI GD
    memory_limit = 16M in your php.ini file.
    php_valuememory_limit 16Min your .htaccessfile
    ini_set('memory_limit', '16M'); in your settings.php file
  • 15. Execution time of 30s exceeded
    “Fatal error: Maximum execution time of 30 seconds exceeded in … on line XXX”
    The default PHP timeout defined in php.ini is 30 seconds. This is too short for some activities like listing/enabling modules.
    max_execution_time 120; (php.ini)
    php_valuemax_execution_time 120 (.htaccess)
    ini_set(‘max_execution_time’, ‘120’) (settings.php)
    Set “max_execution_time “ = 3000 and Enjoy  (is very useful in testing stage)
  • 16. Dear friend - .htaccess
    .htaccess was not uploaded (Access Denied message, Disabled Clean urls)
    • RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
    “PHP: Error parsing …” - () was in .htaccess comments ->
    • # RewriteCond %{HTTP_HOST} ^$ [NC]
    • 17. # RewriteRule ^(.*)$$1 [L,R=301] ->
    • # RewriteCond %{HTTP_HOST} ^$ [NC]
    • 18. # RewriteRule ^(.*)$$1 [L,R=301]
  • Lovely settings.php
    $cookie_domain = '';
    • Drupal automatically generates a unique session cookie name for each site, based on full domain name
    • 19. This option is used in CKFinder configuring
    • 20. Do not miss it, going from dev-server to production-server
    Take care about file permission and $db_url and $update_free_access
    Don’t forget, if you have $db_prefix, you should use {table} in SQL query build
  • 21. WSOD (White Screen Of Death)
    "Invisible" Errors or Blank Pages, how to fix:
    SELECT * FROM watchdog LIMIT 20;
    Easy manual quick-fixing
    • rename couple of modules step-by-step
    • bench_chart.module, wsod_emergency.php, wsod.module
    Increase CPU limit on hosting server
    • With low level (3-5%) some heavy pages will be “blank”
  • Another silly mistakes
    Whitespace at the Begin and End of a PHP File
    • See more about <? and <?php in short_open_tag “php configuration option” information
    • 22. God, bless IDEs, which remove trailing whitespace. Or you should take care with your coding 
    “You are not authorized to access this page”
    • browser multi tab access
    • 23. block settings changes
    • 24. admin/build/themes on slow hosting
    To fix this issue: call drupal_flush_all_caches(); anywhere
  • 25. Disabling Modules
    Via the Module Administration Page in the UI
    Administer > Site Building > Modules … Uncheck and Save
    Via the Database
    If your WSOD is caused by a specific module and you cannot access the module admin page, go to system table, set status to 0 and then clear the cache table
  • 26. You should have cron
    There are many ways to configure cron (curl, lynx, wget, even GET), but …
    Here is real “drupal” way:
    Change file permission for scripts/ (chmoda+x scripts/
    Use in crontab file (or in Hosting Control Panel) this command:
    /home/account/www/scripts/ --root /home/account/www http://default/cron.php
    PS. Cron is used by many modules:
    Update, Event, Aggregator, Search, Notifications, Send, Image watermark, Watchdog and other which must run time-related tasks.
  • 27. Suggestions Before Deployment
    Be afraid free hosting with additional ads
    • admin/build/[modules|menu] doesn’t run
    • 28. admin/build/themes run with errors
    • 29. JavaScript/AJAX/XMLHttpRequest errors
    These actions would be great to do before/during/after deployment:
    TRUNCATE TABLE watchdog;
    drupal_flush_all_caches(); or “Clear Cached Data”
    "Rebuild Permissions" in Post Settings page
    “Re-Index site”
  • 30. Think at first || rapid development
    Masquarade module
    Devel/Themer module
    Drush module
    “TEASER break” button in rich editor an Node-System
    Use professional IDE
  • 31. References
    Drupal Deployment Checklist (!!)
    General information about cron with Drupal
    Advanced Cron Modules
    • +++
    Dtools module (WSOD tablet)
    Advanced PHP Error Handling via htaccess (!!!)
    Stupid htaccess Tricks (!!!)
    Drupal Tweaks (helping with allocation of php memory size)
    Drush - Drupal Shell utility
    • || ||
    Automating Drupal Deployment with drush_make and Features (!!!)
    Install with Drush (!!! – GREAT short list of command to install)
  • That’s all
    Send me email. I’m here
    Follow me in twitter @landike
    Call me via Skype – lan_researcher
    See my “media” updates on
    drupal user – LAN_DRUPAL