Drupalcamp Estonia - Drupal 7

596 views

Published on

Drupal 7 and way forward by Kristjan Jansen in DrupalCamp Estonia 2011.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
596
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Drupalcamp Estonia - Drupal 7

  1. 1. Drupal 7 anDway forwarDKristjan Jansenhttp://kika.trip.ee
  2. 2. we will talk about1 why Drupal 7?2 upgrade process3 Drupal 8 and beyond
  3. 3. 1why Drupal 7?
  4. 4. Visible changes
  5. 5. overlay and new themes
  6. 6. CCK (fields) in core
  7. 7. Images + ImageCache in core
  8. 8. new information architecture
  9. 9. lots of small improvements
  10. 10. under the hood
  11. 11. new database layer + drivers
  12. 12. Semantic web: rDfa
  13. 13. Testing framework
  14. 14. nice, but..D7 helps you get started more quickly on newprojects but what about upgrading from D6? why should I bother?
  15. 15. Security
  16. 16. Drupal development supports current (D7)and previous release (D6) fixes (including securityones) are applied to these releases, not ealier ones
  17. 17. D7 took three years to make, target for D8 is two years. This means D6 sites will be obsolete and likely insecure by late 2012
  18. 18. web is moving on
  19. 19. latest web technologies are beingintegrated with Drupal...but only for D7 and D8
  20. 20. Brave newinterfaces
  21. 21. Key contributed modules are rewritten for D7 and have next-gen user interface and functionality
  22. 22. Views
  23. 23. Media
  24. 24. Commerce (ex-ubercart)
  25. 25. Convinced?It’s oK not to be :)
  26. 26. 2upgrade process
  27. 27. Start with /upGraDE.txt
  28. 28. Drush makes things easier, here’s how to disable all no-core modules in 1 sec> drush pm-disable `drush pm-list--pipe --status=enabled --no-core` -y
  29. 29. If update.php failsphp max_execution_time 0 variablecheck.moduleGoogle for error messages
  30. 30. Trickierdata upgrades
  31. 31. D7 CCK module for migration
  32. 32. D7 references module
  33. 33. Image migration D6 image module D6 imagefield module D7 core image module  (D7 media module?)
  34. 34. Moduleupgrades
  35. 35. Is there a D7 version? Most popular modules are ported There is a steady process of D7 releases “long tail” of modules
  36. 36. ScenariosHave D7 portIn D7 coreno D7 port, has alternativeobsoleteno D7 port
  37. 37. no D7 portIs there a issue in a project? Contact (co)maintainer Sponsor port or DIy look for alternatives
  38. 38. Subscribe to releases rSS
  39. 39. Theme upgrades
  40. 40. who made your theme? Custom theme?Drupal contrib theme?Based on base theme?
  41. 41. Theme code has changed
  42. 42. porting alternativesport existing D6 theme to D7 find new base (Stark,starter kits) and reinterpret Create fresh new design
  43. 43. If your update.php is successful...
  44. 44. ..there’s still lot to do Input (text) formats Imagecache presets Views (partially) Blocks
  45. 45. upgradecase studies
  46. 46. a Simple blogB Big community site, 8k visitors per day
  47. 47. a Simple blog30 minutes (with Drush)to get module statuses and right versions
  48. 48. a Simple blog1 hour to debug errors
  49. 49. a Simple blog3 hours to port theme.Creating from scratch,reinterpret. 90% ready
  50. 50. B Big community site It took 2 hours to run update.php with 45k nodes and 250k comments
  51. 51. B Big community site But it failed
  52. 52. B Big community site remove all contrib modules, try again? Go for migrate.module?
  53. 53. It’s almost impossible to have 100% smooth dataupgrade using update.php D7 tried hard but it’s still buggy
  54. 54. D8 might have in-releaseupgrades only(8.0 to 8.5 etc)
  55. 55. 3 Drupal 8and beyond
  56. 56. D7 development process had lot of weaknesses It took a year too long lot of lessons learned
  57. 57. Core initiativesTo solve organizationaldevelopment problems
  58. 58. Split development into separate tracks withresponsible initiative owners five initial initiatives (there might be more)
  59. 59. Configuration Management web Services Design Internationalization HTMl5
  60. 60. CVS  Git To solve technicaldevelopment problems
  61. 61. Drupal.org, Github killer?
  62. 62. not yet, but the Git impact tonum. of commits is massive
  63. 63. new dev modelCore initiatives + Git helps toscale Drupal 8 development
  64. 64. There’s a hope that we do not need to wait another three years for Drupal 8
  65. 65. Thanks!

×