Planet Drupal

Subscribe to Planet Drupal feed - aggregated feeds in category Planet Drupal
Updated: 22 min 4 sec ago frontpage posts: Curso online de Experto en Drupal 7. Pruébalo gratis!!

Fri, 09/01/2015 - 13:42

A qué esperas para unirte al curso más completo de Drupal 7? Si tienes dudas, ahora puedes probarlo gratis durante una semana!

Y si quieres continuar con el curso completo, tendrás un 10% de descuento aplicando el cupón CURSOS10.

El curso de Experto en Drupal 7 incluye Site Building y Development y se compone de 60 unidades en 3 niveles: Inicial, Intermedio y Avanzado. Después de completar los tres módulos tendrás que desarrollar un Proyecto Final. La duración total del curso es de 7 meses con 420 horas certificadas, pero puedes acortar este tiempo con mayor esfuerzo y dedicación.

Aunque esta acción formativa requiere un esfuerzo importante, ahorrarás mucho tiempo en comparación con estudiar Drupal por tu cuenta, sin dejarte nada en el camino y ganando muy pronto en solvencia para afrontar cualquier proyecto en Drupal.

Ten cuidado, si lo pruebas querrás continuar!

Categories: Elsewhere

Amazee Labs: Zurich joins the Drupal Global Sprint Weekend 2015

Fri, 09/01/2015 - 13:35
Zurich joins the Drupal Global Sprint Weekend 2015

On the weekend of 17. & 18.01.2015, dozens of Drupal contribution sprints will be taking place across the globe. Amazee Labs invites all of you interested in learning, hacking and improving Drupal to join us for two days of pure sprinting at our offices in Zurich.

  • Date: 17. & 18.01.2015
  • Time: 9:00 a.m. - open end
  • Location: Amazee Labs, Förrlibuckstrasse 30, 8005 Zürich
  • Food & Drink: provided
  • Registration: RSVP here

What can I expect from sprinting with you?

  • Get up to speed with the Drupal 8 and dive into coding new patterns
  • See how far you can get with the much improved site building tools in Drupal 8
  • Submit your first Drupal patch as a contributor
  • Help out in a Drupal core initiative
  • Discuss hard problems face-to-face with other experienced Drupalistas
  • A sprint place with enough food and drinks to get things done
  • Be your own client and have fun :)

Who can contribute?

Coders, designers, front-end developers, designers, project managers, user experience experts, clients, basically anyone who wants to improve Drupal, are welcome to the sprints.

Regardless of your knowledge level, if you have built a site in Drupal, you can contribute and are warmly welcomed.

What can I work on?

We will split into groups and work on Drupal core issues. Bring your laptop. For new folks: you can get a head start also by making an account on, setting up your dev environment ( and developers can install git before coming and git clone Drupal 8 core.

A great way to get started with contributing to Drupal core is to get involved with an initiative. We'll have local folks present with knowledge about Multilingual, Rules, CMI etc. Also check out the Drupal core initiatives and topics!

The following sprint topics have been proposed already:

Registration: RSVP here

Categories: Elsewhere

Drupal core announcements: Changes to Drupal 8 that affect admin theme maintainers

Fri, 09/01/2015 - 13:01

Happy Friday! I maintain the admin theme in Drupal 8 core: Seven. There have been many changes to Seven in Drupal 8 that affect the relationship between admin themes and modules, and how the admin UI is generated.

I've always thought that the strategy we've put in place are going to have a positive impact on maintainers of contrib admin themes, but I've never sought out feedback directly. I am now!

Object oriented CSS

We now have CSS standards in Drupal 8. All CSS in core is being rewritten and restructured inline with those standards. They are heavily influencds by the principles of OOCSS, SMACSS, BEM, and the writings of Nicolas Gallagher.

The Seven theme, with the introduction and evolution of the Seven Style Guide, embraced these principles from design down to implementation. As all modules with administrative UIs are tested against Seven, the architecture and design of Seven influences all contrib admin themes.

Reusable admin CSS components

Taking influence from frontend frameworks such as Bootstrap, Seven's design is now split into components, instead of per page overrides and designs.

This creates a 'visual api' of sorts that modules hook into and reuse to create the admin UI they need without having to write any CSS. It also ensures a greater consistency throughout Drupal's UX.

One common example are buttons, the classes .button, .button--primary, .button--danger, .buttoner--small can be applied to any element.

Another is the heading classes. Classes like .heading-a, .heading-b, heading-c</code mimic the hierarchy of the <code>h1, h2, h3 elements. You can pick the font sizes that look right for your page without affecting accessibility or overriding it in CSS.

We also have reusable classes to control layout. Using classes like .layout-column.half, .layout-column.quarter, .layout-column.three-quarter will layout your page for you. Classes such as .leader, .leader-double, .leader-triple will add spacing above an element that matches the base leading of Seven, while .trailer, .trailer-double, .trailer-triple will add spacing below.

Another low level component are the color classes, .color-success, .color-warning, .color-error allow you to reuse colors defined in the Seven styleguide, without a tool like Sass or CSS variables.

Less admin CSS in modules

With a full library of reusable CSS components, contrib modules will need to write less CSS. From my point of view, this is a big win for contrib admin theme maintainers, who have to write a lot of custom CSS to override custom CSS in some complex modules, and it's harder to tell if modules are broken because of the changes in the admin theme.

I'm hoping that admin theme maintainers will be able to override just the reusable components and have better coverage of core and contrib modules.

Ongoing work

We are still working on converting a lot of custom CSS into reusable components, and will continue to build the library of components after Drupal 8s release.

Feedback please!

Admin theme maintainers, are there any problems or pitfalls you see with this approach? I would like to know.

Categories: Elsewhere

Appnovation Technologies: How to add JS and CSS assets to a Drupal 8 theme

Fri, 09/01/2015 - 08:21

In one of my previous posts I wrote about creating a Drupal 8 theme and declaring assets (JS and CSS) associated with it.

var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Categories: Elsewhere

LevelTen Interactive: Drupal 8 Videos You Need To Watch

Fri, 09/01/2015 - 07:00

I searched far and wide to bring you great Drupal 8 presentations. These videos provide great examples of where Drupal is headed, why change is important and what you can expect from Drupal 8 and beyond.

... Read more

Categories: Elsewhere

Akshay Kalose: Drupal 8: RDF UI ( Mappings)

Fri, 09/01/2015 - 06:29

RDF UI is a module for Drupal 8 created by Sachini Aparna Herath for her Google Summer of Code 2014 project. RDF stands for Resource Description Framework; it provides a standardized model for data interchange. This module enables you to easily create mappings of Things to Drupal Content Types and Fields. RDF UI will embed these specified mappings in the HTML as RDFa once your content is published. This blog post was made for Google Code-In 2014 to test and review RDF UI.


RDF UI can be easily installed using the Drush command line tool for Drupal. You may want to select installing the development version, as that will be the closest to running with the latest Drupal 8 development version:

drush dl rdfui --select


This section is about my experience upgrading RDF UI to the latest Drupal 8. This module was created over the summer, when GSoC takes place. As a result, it wasn’t compatible with the latest Drupal 8 development release, Beta 4.

I started upgrading from the stable version, and by the time I realized there was a development version, I had already done much of the upgrading, so I integrated the changes from that branch into my upgrade while still keeping most of mine similar to how it was before.

Some of the things I had to upgrade were: moving the attached CSS to a library, re-factoring the Form State from an array to an object, and accounting for the fact that Drupal\views_ui\OverviewBase was merged into Drupal\views_ui\DisplayOverviewBase. I also have included minor improvements here and there in the code.

One problem I encountered while using the sub module was that the default Data Type was text. However in the latest Drupal 8, this is the formatted text, and the plain text was needed, so this was fixed by changing the default from “text” to “string“:

diff --git a/rdf_builder/src/Form/ContentBuilderForm.php b/rdf_builder/src/Form/ContentBuilderForm.php index 6d2001a..c3cc50c 100644 --- a/rdf_builder/src/Form/ContentBuilderForm.php +++ b/rdf_builder/src/Form/ContentBuilderForm.php @@ -64,8 +64,8 @@ class ContentBuilderForm extends FormBase { public function __construct() { $this->converter = new SchemaOrgConverter(); $this->datatype_field_mappings = array( - '' => 'text', - '' => 'text_long', + '' => 'string', + '' => 'string_long', '' => 'integer', '' => 'file', '' => 'file', @@ -470,6 +468,6 @@ class ContentBuilderForm extends FormBase { return $this->datatype_field_mappings[$datatype]; } } - return 'text'; + return 'string'; } }

The full upgrade patch can be viewed at this Issue on RDF UI.


As said on the project page, integration of mappings in Content Types is seamless. In the “Add Content Type” form you can choose which Type this Content Type will be:

Once you fill this out and reach the “Manage Fields” page, you need to create you new fields. You can then click the “RDF Mappings” tab to assign these fields their property:

Now you are ready to go ahead and create your content. Once created and published, the node should show the fields and the html should contain the Type in the article tag and Properties in the field-items divisions:

RDF UI Builder!

RDF UI also comes with a very helpful sub module named: RDF UI Builder. Want to shorten up all the steps above in creating mapped Content Types? This sub module comes in handy for that very purpose.

Once this module is enabled, you can find the new “+ Add Content Type” button next to the original “+ Add content type” button:

After selecting which Type you want to use, you are redirected to the next page where the only thing you need to do is select which fields you want, and they will automatically be created and mapped for you!

That’s it, now you can go off and create content for that type.


Sachini Aparna Herath, with the help of her mentors Stéphane Corlosquet and Kevin Oleary, has created a great module for Drupal 8. RDF UI fits in with the rest of Drupal, and can be used to quickly create content types or fields and assign them Types and Properties. This can help any site owner to provide “semantic rich data” on their web pages.

One improvement I can suggest is that the Type should default as date only in Drupal. As of right now both and convert into Drupal datetime. This may be because Drupal does not have Date and DateTime options in the drop down. If this is the case, this improvement would be for Drupal Core to move selecting DateTime or only Date to the main select menu before selecting Date and then choosing for a new field.

From a Google Code-In perspective, this task had many obstacles which I had to go through to upgrade the module to be working with the latest Drupal 8 version, Beta 4, and I am glad as I keep learning more with the more problems I face. It is also the first time I have created a change record, because one of the errors received had not been included in the list of changes.

The post Drupal 8: RDF UI ( Mappings) appeared first on Akshay Kalose.

Categories: Elsewhere

Károly Négyesi: static methods

Fri, 09/01/2015 - 06:27

Here's something I learned from Wim Leers: the static keyword has a bad rep in PHP but that's because static variables can be problematic. static methods, especially protected static methods on the other hand are useful to indicate and enforce a method not changing the state of the object.

Categories: Elsewhere

Forum One: Forum One to Host Global Sprint Weekend in DC

Thu, 08/01/2015 - 23:49

Want to join me for a marathon next weekend?

As part of a worldwide effort known as the Drupal Global Sprint Weekend, hundreds of coders from around the world are joining together in a united effort to complete a marathon task: the launch of the next generation of the world’s most popular open-source platform, Drupal 8.

To participate in this massive movement and contribute to the Drupal Community, Forum One is hosting a local Code Sprint in downtown Washington, DC on Saturday, January 17th. Sign up here »

Never been to a code sprint before? No worries; we’re pros at these events! Here’s what you can expect:

What is a code sprint?

A code sprint is when developers get together and write code. There’s minor instruction and some ad hoc mentoring, but mainly the focus is just uniting developers and hammering out code together. That’s all there is to it!

How will this event work?

Our developers will work with you to find Drupal 8 core issues for you to focus on. You won’t need to research anything on your own, but you will need to bring your own laptop, and it helps a lot if you set up your development environment beforehand. For instructions on how to get set up and for additional details like the event agenda, visit the RSVP page »

Why should I attend?
  • You’ll meet other DC area developers!
  • You’ll roll up your sleeves and become a bona fide Drupal 8 Core Contributor!
  • You’ll learn from our on-site mentors and fellow developers!
  • You’ll earn tons of karma by furthering the mission of the open-source development model!
  • It’s totally free!

Intrigued? Excited? Can’t hardly contain your enthusiasm? Awesome! Sign up for this free event and join me and the DC open-source developer community as we take on this marathon effort and get 26.2-ish miles closer to bringing Drupal 8 across the finish line.

Categories: Elsewhere

Mediacurrent: How to prettify the output from your remote drush commands

Thu, 08/01/2015 - 22:55

Have you noticed how the output from your remote drush commands wraps at awkward lengths? This is especially annoying with features commands:

Well, here's a quick fix! Throw this snippet into your drush alias. It adds a "shell-alias" that executes the features-list command with the --tty SSH option.

Categories: Elsewhere

DrupalOnWindows: Installing Drupal on Windows and SQL Server

Thu, 08/01/2015 - 20:13

This article explains how to install Drupal on IIS and SQL Server with the basic performance settings. It is aimed at understading the different pieces that compose the environment needed to run Drupal on Windows and intended to audiences that have at least an intermediate level of confidence with Windows, IIS and SQL Server.

Language English
Categories: Elsewhere

Drupal Easy: Nimble Training

Thu, 08/01/2015 - 18:36

Since we have ramped up our training business over the past months, I've been teaching a lot of Drupal to a lot of different types of people with various backgrounds, goals and motivations. As diverse as they may be, from private client training engagements for some of the largest Drupal shops to our own 12-week Drupal Career Online to now providing the technical curriculum for Acquia U, one training element that spans audiences and is continually driven home is the importance of being nimble.


read more

Categories: Elsewhere

Acquia: Explaining Drupal, the pragmatic choice – meet David Aponovich

Thu, 08/01/2015 - 16:48
Language Undefined

David Aponovich knows the web content management business far beyond just the "Drupalsphere". I was thrilled when he joined Acquia from Forrester Research in 2014, since I believe his voice, experience, and insight can help convince more businesses of the benefits of using Drupal, especially given the upcoming release of Drupal 8. He and I sat down at DrupalCon Amsterdam – David's first Drupal community event – and talked about digital transformation from the "information superhighway" to today, corporations and open source software as a pragmatic choice, and how the definitions of cooperation and competition are changing in business today.

Categories: Elsewhere

Cheppers blog: Busy January at Cheppers

Thu, 08/01/2015 - 16:11

First of all - Happy New Year everyone! 2015 will be a fantastic year and we at Cheppers are ready to kick off! Let's see how we are going to start the year.

Categories: Elsewhere

Blink Reaction: Part Four: IDE Integration

Thu, 08/01/2015 - 15:32

At this point we have our VM running and performance tuned. Now that we have a synced directory on our host machine, it’s easy to see how we copy our site onto the VM. You may have already done this, and that’s okay! Let’s integrate the VM with our IDE so we can push our changes much more easily.

Categories: Elsewhere

Drupalize.Me: Being Prepared When Everything Goes Wrong

Thu, 08/01/2015 - 15:02

We recently completed making updates to our incident response plan for Drupalize.Me and I wanted to share some of what we learned along the way, and help you write your own. An incident response plan is all about being prepared. So that in the moment, under pressure, when everything that could possibly go wrong is going wrong, you can remain calm, cool, and level-headed. If you've ever had to write a social media message, or respond to a support request during an un-planned site outage you know how easy it can be to misstep—even if your intentions are good.

Categories: Elsewhere

Code Karate: Drupal 7 Smart Trim: An simple way to shorten long text areas

Thu, 08/01/2015 - 14:45
Episode Number: 189

The Drupal 7 Smart Trim module allows you complete control over how you want text to be displayed when shortened. Put another way this is the module to use if you want to display a teaser or a beginning part of a longer text area.

Once installed you are able to set a variety of things. These include: shorten length by either words or characters, what to display for the ellipse (...), if you want a "read more" link to appear and what you want the link to say and lastly if you prefer to use the Drupal summary option.

Tags: DrupalFieldsViewsDrupal 7Site BuildingDrupal Planet
Categories: Elsewhere

Wunderkraut blog: Iterative and incremental Drupal development

Thu, 08/01/2015 - 11:54

Iterative development process works well for software development in general. Using a process like Scrum can however cause some problems with a high productivity platform like Drupal. With Drupal you already have a working product very early in the process, you tweak the details and in the end have an improved version. With Drupal features are cheap and details are expensive.

We like to experiment with our process and to improve it. With a company full of agile experts, trainers and coaches there are plenty of discussions around the topic. One of the recent ones has been on moving from just one definition of done to having one for each iteration of a feature. This should give us better visibility for progress and provide earlier decision points for the customer.

Why do we need this?
  1. Make sure we don't do what the customer asks but what the customer needs. It's our job to meet the business need of a customer, we should be able to offer alternative solutions to the customer instead of just going for the most obvious or the "Drupal standard" one.
  2. Keep better control over the project budget. We are good at delivering the highest priority items first, but not always great at knowing what's good enough. This approach will move the work to the next story before the previous story is implemented perfectly. The goal is to add more clarity on when good is better than perfect.
  3. Help the team members work together in a more effective way. When we work on different stages of multiple stories simultaneously it's easy to lose track of progress. Having a clear process should help us not to do important steps too late and keep the communication simpler.
  4. Allow customers more time to react on the primary decisions by pushing detailed decisions to later in the project. When the customer knows what level of detail we are dealing with they should have easier time on deciding how much time they should use on it.

In the end of the day most of our customers just care about getting the job done in the most efficient way possible. It’s not so much about technology, design or methodology to get there, it’s much more about the results.

How should we do it?

By combining iterative and incremental process into what I call development waves. It's nothing radically new, just combining many things we already do into a process and documenting it.

The basic idea is to approach a project with increments and iterations. Increments will add functionality and iterations will improve functionality. Instead of trying to get a story done-done in a sprint we will have different definitions of done for different iteration tasks. This is intended to help us find better ways of meeting the why of a story, keep the project moving forward faster and allow more innovation during the project.

The cooperation between team members should also improve with each story being split always to similar tasks based on iterations. We can also use the same methodology for epic stories and tasks.

Sprints move through increments and iterations of them in waves. In some cases multiple iterations will be done in a sprint, in some just one. Instead of working to reach the definition of done for a full story the team works to reach definition of done for each iteration of a story. This removes a lot of the extra overhead needed for quality assurance while we are still not 100% sure what the final implementation will look like. When the PO changes her mind or the team figures out a better way of delivering the story less work is wasted.

To help balance the workload of team members stories are not in sync for their iteration level. One story in a sprint may only have concept level work done on it, another user experience design and third MVP implementation. This will replace the sprint scouting we do today and make the communication around it easier. It should also make progress more visible and estimation of tasks easier when every story is always split to iteration tasks.

The goal for any project should not be to complete 100% of the backlog. Usually if that happens time has already been wasted on low value items and the same time would be better spent on either improving the quality of higher value stories or coming up with new ideas.

When a release of a project is done we have always completed the most valuable stories for that release and also done some scouting for the future. There may be some time wasted with getting started on stories that will not be implemented, but on the other hand we should be able to make incredible savings on other stories by coming up with more effective ways of implementing them.

Image credit: Henrik Kniberg, What is Scrum

The approach is to build something visible and useful as early as possible. This is true both for iterations and increments. Everything we build should immediately have some value to it and we should be able to explain that value to the customer at any point.


In the next post I'll define different iterations and how to do them.

Categories: Elsewhere

KatteKrab: The Great D8 Chook Raffle

Thu, 08/01/2015 - 11:06
Thursday, January 8, 2015 - 21:06The Drupal Association board approved a new initiative to help get Drupal 8 done.  It's called the D8 Accelerate fund. We also agreed to personally help do fundraising to support the program.  So I'm running a chook raffle.  For those of you who don't know what that is, Wikipedia gives a decent introduction.   The Drupal Association is working with the Drupal 8 branch maintainers to provide Drupal 8 Acceleration Grants. The goal is to fund work that will positively impact the release date. Drupal 8 has had over 2,400 contributors to date, which is more than any release so far. We hope that this initiative will encourage even more people to join the effort to get D8 done.   I'm about to launch a pozible campaign.  Stay tuned!      
Categories: Elsewhere

Yuriy Gerasimov: Render custom button

Thu, 08/01/2015 - 09:19

Sometimes for our front-end development we need to have very granular control about how our form buttons being rendered. So instead of standard drupal markup we want to have something like

<button class="bird-guide-zip-submit button pea-green"> <span class="hide-for-medium hide-for-large hide-for-xlarge"> <i class="icon-magnifier"></i> </span> <span class="hide-for-tiny hide-for-small">Ok</span> </button>

You would think that something like:

$form['submit'] = array( '#type' => 'button', '#value' => '<span class="hide-for-medium hide-for-large hide-for-xlarge"> <i class="icon-magnifier"></i> </span> <span class="hide-for-tiny hide-for-small">' . t('Ok') . '</span>', '#attributes' => array( 'class' => array('bird-guide-zip-submit', 'button', 'pea-green'), ), );

would do the job but that is not the case as #value is being sanitized (that is great from security perspective). In order to change this behavior for one particular button we should use

'#theme_wrappers' => array('mymodule_button'),

And then define your custom theming function

/** * Implements hook_theme(). */ function mymodule_theme() { return array( 'mymodule_button' => array( 'render element' => 'element', ), ); }   /** * Custom button theming function. */ function theme_mymodule_button($variables) { $element = $variables['element'];   $element['#attributes']['type'] = 'submit'; element_set_attributes($element, array('id', 'name')); $element['#attributes']['class'][] = 'form-' . $element['#button_type']; return '<button' . drupal_attributes($element['#attributes']) . '>' . $element['#value'] . '</button>'; }

Be aware that when you use this technique you take responsibility for making sure you do not display any potentially harmful html in the #value as you do not sanitize it.

Tags: drupal planetdrupal 7
Categories: Elsewhere

Modules Unraveled: 128 The Z-Ray Developer Bar with Daniel Berman - Modules Unraveled Podcast

Thu, 08/01/2015 - 09:15
Published: Thu, 01/08/15Download this episodeZ-Ray
  • So, let’s start out with the basics. What exactly is Z-Ray?

    • So Z-Ray is a cool new tech that we introduced just a few months back which gives developers deep insight into all the PHP elements constructing their page, including Drupal-specific elements.
    • It’s basically a toolbar that’s displayed right in front of you in your browser. No code changes needed. You don’t have to configure anything. Just open your app in a browser and you’ll see Z-Ray at the bottom of the page!
  • How does is work? Is there a module that you have to install on your site?

    • No. It’s not a module. Without going into too much detail: Z-Ray collects info while your app is being processed on the server side, and once the request is completed, Z-Ray’s JavaScript code is injected into the response with all the collected data.
    • There are other mechanisms at work, such as Ajax support, but as a whole that’s all there is to it. It’s also the limit of my technical understanding of how it works :-)
  • So what info does Z-Ray display? What are it’s main features?
    Well. There’re so many features in Z-Ray, and I don’t think we have the time to go over them all, but to mention just a few.

    • Z-Ray gives you info on SQL queries. You’ll see a query’s bound value, the result of the query, how long the query took, and how many rows in your code are affected by the query.
      You can even see a backtrace of the query to get the larger picture on how your code was executed.
    • Z-Ray also gives you all the errors generated by PHP itself, or those created by its core functions. You can also see errors for silenced expressions. Exceptions are also displayed.
    • What do we have for Drupal devs? Z-Ray will give you a list of loaded Drupal modules with invoked actions and hooks, a list of called Drupal functions, a list of used Drupal forms on the page, and some general user info.
    • We’re especially excited about Z-Ray Live! Until now we’ve spoken about using Z-Ray in a browser, right? But what if you’re developing APIs or a mobile app? No browser there. So Z-Ray Live! is a new feature accessible via a dedicated page in the Zend Server UI, with an embedded Z-Ray.
      So as soon as this page is loaded, Z-Ray records and displays any request made to the web server, never mind where its coming from - whether from a browser, a mobile device or a web-service client.
    • One of the coolest things about Z-Ray is that you can plug in your own customized extension. Even people in Zend itself have begun developing their own extensions so its pretty viral.
      By the way, all the code for the Drupal extension is available on Github, so feel free to fork it and send us a pull request.
    • There’s integration with IDEs, session and cookie data, request info, and so much more to talk about.
  • Is Z-Ray just for development? Or should it be used in production too?

    • Z-Ray was designed to be used both in dev and prod. While in development it works on every request, in production you can manually use Z-Ray using specially created access tokens. And it also periodically saves snapshots for important URLs - like the slowest requests on your web server, most time consuming requests, and so on. And again - with no changes to your code and no real implication on end-user experience or server performance.
  • OK, if I want to give it a shot, what does the installation process look like?

    • Z-Ray’s bundled with Zend Server, so to use Z-Ray you would need to download and install Zend Server - a total no brainer. Just like installing any other PHP stack.
  • So, how do you see Z-Ray helping Drupal developers?

    • At Zend we like to talk about left-shifting. This basically means that Z-Ray helps developers hit issues very early in the development cycle and way before going to staging and production.
    • We all know that getting clarity on all the Drupal elements working under the hood is extremely hard and takes loads of time. So at the end the day we believe that Z-Ray gives Drupal devs the visibility they need to properly profile their apps, identify bugs very early, and troubleshoot them.
Episode Links: Zend Server Z-RayDrupal Demo of Z-BarZend WebsiteZend Server Online HelpZ-Ray on YouTubeZ-Ray Drupal Extention on GithubDaniel on TwitterEmail DanielTags: ServerDevelopmentPerformanceplanet-drupal
Categories: Elsewhere