Drupal

It is a lot of work making tutorials for Drupalize.Me and keeping our production quality high. Why do we do it? For many reasons: 1) we love our jobs, 2) we love Drupal, and 3) most importantly, we understand our members pay for quality and we want to deliver. We are constantly reviewing this process and coming up with ideas of how we can improve our quality and efficiency. The process above is never set in stone—it is a guide—and that guide is used to see how and where we can make even better tutorials for our members.

The problem(s) of Full virtual servers: - Consume another layer of system memory. - IO is slower than the actual real system and makes Drupal sluggish to respond. - Are very complex to configure. - Drupal needs faster automated deployments solutions. - Costumers need full shell access, with services admin. The proposed solution: - Linux containers with vagrant & docker automatic deployments.

The RS/RT project provides a “create once, serve many” option that also provides the user with a level of privacy that generally face-to-face reference interviews cannot. The product was designed from a user’s stand point. Understanding that many service seekers have little experience with technology, we designed a clean and simple interface, requiring only a few actions to progress to the next step. We worked with a 4th grade reading level and provided 3 language options (English, Spanish, and Haitian Creole).

There are times in Drupal 7 when the registry gets hopelessly hosed and you need to rebuild the registry (a list of PHP classes and the files they go with). Sometimes, though, you can't do this regular cache-clear activity because some class is required when the system is trying to bootstrap

@tedbow if you download the latest (Aug 8) Dev release of field_collection and re-apply this patch it works http://t.co/3wyNNJqJ