1 / 72

Drupal and the CMS Project

Drupal and the CMS Project. Lesson Learned #1. Keep your modules updated, especially when there are security concerns in the update notes. Update Status Email.

amalie
Download Presentation

Drupal and the CMS Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Drupal and the CMS Project

  2. Lesson Learned #1 • Keep your modules updated, especially when there are security concerns in the update notes

  3. Update Status Email • From: <drupal-admin@yoursite.com>Date: Thu, Dec 2, 2010 at 3:39 PMSubject: New release(s) available for <Your Site Name>To: kolafson@uwaterloo.caThere are security updates available for one or more of your modules or themes. To ensure the security of your server, you should update immediately!See the available updates page for more information:http://www.yoursite.com/admin/reports/updates

  4. Update Status Report

  5. Lesson Learned #2 • Set up a cron job or Windows scheduled task to hit cron.php on your Drupal installation at regular intervals • Usually every hour

  6. The Drupal /sites folder • When you install Drupal, the /sites folder contains 2 directories, “all” and “default” • You can host additional sites by making new directories in the /sites folder with the name of the site and copying the settings.php file there from the default directory • For instance, /sites/krisbase.com

  7. The Drupal /sites folder • Modules and themes you want available to every site go in the /sites/all/modules and /sites/all/themes folders • Modules you only want available to a specific site go in that site’s modules and themes folders • ex. /sites/krisbase.com/modules

  8. Lesson Learned #3 • Don’t modify the Drupal Core files • (Don’t touch anything outside of the /sites directory)

  9. The End of the Road

  10. Hooks in Drupal • foo_bar() • “foo” is the name of the module • “bar” is the name of the hook • uwblogs_block()

  11. Theme Developer Module

  12. Lesson Learned #4 • There is a module for that! • Most common needs already have one or more modules built to address them

  13. Drupal Inline Image Solutions • Linodef + • LinodefTaglists + • Linodef WYSIWYG + • WYSIWYG

  14. Drupal Inline Image Solutions • Image + • Image Assist + • WYSIWYG + • TinyMCE

  15. Drupal Inline Image Solutions • Imagefield + • Imagefield Assist + • Imagecache

  16. Drupal Inline Image Solutions • Imagebrowser (v1) + • Image + • ImageCache + • FCKEditor

  17. Drupal Inline Image Solutions • Imagebrowser (v2) + • WYSIWYG + • ImageCache + • Views

  18. Drupal Inline Image Solutions • Inline

  19. Drupal Inline Image Solutions • Insert + • WYSIWYG + • ImageField + • ImageCache

  20. Drupal Inline Image Solutions • Media + • Styles + • WYSIWYG + • CKEditor

  21. Drupal Inline Image Solutions • Nodereference Explorer, + • Insert + • WYSIWYG

  22. Drupal Inline Image Solutions • Prosepoint Modules

  23. Drupal Inline Image Solutions • WYSIWYG + • CKEditor (js) + • WYSIWYG Image Upload

  24. Drupal Inline Image Solutions • WYSIWYG + • CKEditor (js) + • CKFinder

  25. Drupal Inline Image Solutions

  26. Module Description

  27. Bug and Issue Queues

  28. Project Information (good)

  29. Project Information (yikes!)

  30. Sometimes modules don’t play nicely together

  31. Now what?

  32. Lesson Learned #5 • Contributed modules go in the /sites/all/modules folder • or /sites/<sitename>/modules • not in /modules folder with the core modules that ship with Drupal

  33. Enabling Modules with Drush • Navigate to one of your Drupal sites in the shell • drush dl <module_name> downloads the most recent production version of the module • drush en <module_name> enables it • You can also disable modules with drush, which is handy if you have a WSOD and can’t access your admin menu

  34. Drush .make Files

  35. Drupal Commons

  36. Managing News

  37. Open Atrium

  38. Blog Requirements • Bloggers should be able to tag their posts • Should be simple using the Drupal Taxonomy module • Tags should have auto-complete functionality and bloggers should only see the suggestions that they previously entered • Blogs should share some taxonomies

  39. Blog Requirements • Bloggers should be able to use a WYSIWYG editor so they can style their posts without HTML knowledge • Bloggers should be able to upload photos and place them where they want in their posts

  40. Blog Requirements • Users should be allowed to comment on blog posts if the blogger allows it • Users should be able to login with CAS • The Blogger’s real name should appear beside their posts, not their username

  41. Blog Requirements • The blog must meet accessibility standards • Blog owners should be allowed to customize their banner image • Blog owners should be able to add pages to their blogs (ex. About Us)

  42. Blog Requirements • Blogs should be allowed to have more than one blogger • For instance a blog for a research lab may have several people posting to it • The blog owner should have the ability to moderate these posts

More Related