Just-in-time provisioning of Drupal user accounts based on SAML attributes (configurable). Automatic role assignment based on SAML attributes (configurable). Dual mode - support for traditional Drupal accounts and SAML-authenticated accounts at the same time (configurable).
just be the people who build Drupal and let the rest go by the wayside? We have spent the vast majority of our time together largely operating under that last banner, but that doesn’t mean that we have no shared values. It just means that they largely go unstated. Which is funny because I think if I were to take a poll of the people reading this, we’d find that on a lot of these social and organizational issues our heads are pretty well aligned. Here are some examples. Do you think the diversity of our community is important?
This is not a module, it's a Drush command that makes it possible to check for known indications of your site having been exploited with the vulnerability fixed in SA-CORE-2014-005. See also SA-CORE-2014-005 FAQ Greg Knaddison's "Your Drupal site got hacked. Now what?" Bevan Rudge's workflow chart
All nodes work with views so anything that generates events as separate nodes will work with views.
Is error reporting on and display errors on in development and off in production? Do not suppress errors in your code. Implement a logging framework. Use a caching strategy. Keep in mind and use programming design patterns and best practices. Use tests in your code and try to automate running these tests every time a change occurs in the code base. Review or at least audit team members’ code. Practice defensive programming. Learn and use OOP principles correctly. Have a solid workflow and processes for developing and deploying code. Differentiate between read / write database queries.
Traits: Just gimme the codez Enter traits. Traits don't imply a relationship. They're purely code reuse. At runtime, traits no longer exist. They say nothing about an object that uses them, how they behave, what you can do with them, or anything else. They are purely code reuse. In that sense, they are completely orthogonal to interfaces; whereas an interface is purely interface reuse, a trait is purely code reuse.
The Mail Editor module lets you edit the bodies and subjects of all emails that go out from your site to your users through Drupal's drupal_mail() function. You are able to edit any email body text based on which email it is and which language it is being sent for. You may use token variables in your templates to better customize dynamic email text. Mail Editor has special support built-in for the User core module and the LoginToboggan module. Enable the Locale core module to activate non-English and even multi-lingual email template translation.
Lets you theme your messages the same way you theme the rest of your website.
Kalabox is a free, integrated workflow solution for Drupal developers. It’s the thing that connects all your things -- including your Pantheon account -- to provide a complete desktop-to-live workflow loop. First developed by Kalamuna as an internal tool, people all over the world now use it to code, test and go live faster than ever.
Find out what modules are installed on any Drupal website.
