Planet Drupal

Subscribe to flux Planet Drupal
Drupal.org - aggregated feeds in category Planet Drupal
Mis à jour : il y a 51 min 7 sec

Drupal Easy: Drupal Goes to College

mar, 07/04/2015 - 22:04

DrupalEasy is so excited to announce that we are teaming up with Stetson University to present the first comprehensive, university-based Drupal career professional development program in Florida! The Drupal Career Certificate Program (DCCP), which is built on DrupalEasy’s Drupal Career Starter Program curriculum, marks an official entrance to the Drupal talent pipeline through the US higher education system. The DCCP, now part of the university’s Boundless Learning programs, will be officially announced at Florida DrupalCamp 2015!  The first course will kick off this Fall at the Stetson Celebration Center located right in the middle of Florida's High Tech corridor on the outskirts of Orlando.

-->

read more

Catégories: Elsewhere

Drupalpress, Drupal in the Health Sciences Library at UVA: equipment booking system — simplify(ing) comments

mar, 07/04/2015 - 20:52

We don’t have a lot of feedback about how our patrons are using the current equipment booking system. There may be information that users could share with one another (and the library) if given a mechanism to do so. So as part of the new booking system implementation in Drupal, we set a task of including a commenting feature. Each reservable piece of equipment stands alone as a node so all we have to do is turn on commenting, right?

Basically.

But there are a couple of things that are worth noting about that.

If you’re enabling comments on a content type, it’s probably a good idea to consider who can view (and post comments to) that content. That’s all in the permissions table.

In our scenario, we didn’t want unauthenticated comments and we didn’t want to restrict the individual equipment pages (e.g. the page for iPad copy 2) to any kind of login. The request to reserve equipment from that page would trigger the login.

The snippet from the permissions table below shows how we adjusted the comment access. Note that these will be permissions that will apply anywhere else on we’re using comments on our site … we’re not currently, but if we do in the future we’re fine with this access level.

Once authenticated, the comment form defaults to give users a text format selection option. There are advantages to users selecting a WYSIWYG format This too can be handled in the text format configurations or even the permissions table. An easier way is with the Simplify module.

Simplify gives you an interface to hide a bunch of stuff that may be noisy to users adding content — publishing options, path settings, etc.

And for comments it lets you hide text formats.

The finished product:

Catégories: Elsewhere

Red Crackle: Why We Chose Drupal Organic Groups: A Comparative Study

mar, 07/04/2015 - 19:30
This article explains why we went ahead with Organic Groups for one of our Drupal projects. As part of our research, we did a detailed analysis of the following platforms: Organic Groups, Open Atrium, Drupal Commons, Open Scholar and Domain Access. We have listed the positive and negatives in the article. You will understand why we finally decided to go with Organic Groups. Follow this article to make informed decisions while choosing a platform for your business needs.
Catégories: Elsewhere

Mediacurrent: Mediacurrent Dropcast: Episode 3

mar, 07/04/2015 - 18:40

This week on the show we will be discussing the new Configuration Management system in Drupal 8 based on an article by Victor Kane, and once again dive into RESTFUL Drupal, or Headless as the cool kids say, based on a blog post from Joris Snoek. We’ll go over some Drupal 8 news and once again Ryan will bring it home the Closing Bell.

Catégories: Elsewhere

Free Energy Media: Drupal and WordPress as a RESTful Backend for iOS and Android Apps or the Web of Things

mar, 07/04/2015 - 16:43


The future of the web is inarguably mobile. Mobile use is clearly increasing as people spend more time on their phones, and the rate that people are using dedicated mobile apps rather than their mobile browser is also increasing. But with web services, mobile apps can integrate popular web-based content management systems and in the process save hundreds of development hours while providing enhanced user experience for both the end user and web editors. This also creates tremendous, largely untapped business opportunity for agencies.

Drupal and WordPress power 2.1% and 23.3% of the web, respectively. There are many contrasts you can make to decide “which is better,” but in the end it comes down to the question of “what is the right tool for the job?” Drupal runs a smaller percentage of the web so it is targeted less by hackers, thus making it less vulnerable. In Drupal all contributed code or “modules,” are peer reviewed at http://drupal.org, helping to ensure quality and stability. Conversely, because of the smaller community and the strict review process there are less modules that get released than WordPress “plugins.” This puts Drupal at a distant second in the volume of contributed plugins/modules that are available. Still, Drupal 8 (the next release of Drupal), shows foresight into the future direction of the web, taking into account “the web of things” or to many web developers the “elephant in the room” Mobile Apps.

Drupal has fully mature projects that turn it into a powerful backend or RESTful “web service” that can be used to provide data to mobile apps via API calls. Drupal 8 comes with the very powerful and stable “Services” module built into D8 core, meaning it will come bundled in every new site of Drupal 8.

To put it simply, your Drupal or WordPress website could be powering the next best mobile app. “The web of things” is another way to say web services, the things that make the apps we use every day “do” things or “talk to” things. Snapchat for example is a popular app, but the native code, the kind written by an iOS or Android developer in the languages Java or Objective C, is quite simple. The heavy lifting is done by a web server somewhere which exposes data through “REST endpoints”;” this web server could be a web app like Drupal or WordPress running the ubiquitous language PHP.

PHP runs on about 75% of websites today, it can be looked at as a big ship – it takes a while for it to turn around (incorporate latest innovations) but it eventually does. While newer languages innovate quicker, PHP has proved to have a dedicated community that eventually does evolve with the times. For these reasons PHP is here to stay.

There are a variety of methods to utilize Drupal or WordPress to create an app that can be purchased on the iOS and Android app stores. For larger budget projects or projects started from scratch, the best method is to code the entire front-end presentation layer of the app in a native language, then use a web service to pull data in from a Drupal/Wordpress web app on “the cloud.” Some people may be able understand this by thinking in the terms of “feeds,” though the technology is quite different. The benefits are clear — you could have a powerful website and also a mobile app for less effort than it would cost to develop each individually with completely unique data sources. It also allows editors to login to their familiar Drupal/Wordpress editors and push out content that will then go to the app and website simultaneously.

Another hybrid method I developed which is very useful for smaller budget projects and for websites that already exist, is to create an API only for the login interface. I created a very simple API and native front-end to handle the login and password reset functionality. The rest of the app is a web view or “wrapper,” meaning that after you login, you just see the website. What makes this so cool is that it does feel quite “appy.” The native feel is enhanced by native navigation and custom offline messaging. After the user enters their email and password into the native interface they never have to login again, thus giving an experience identical to an app in every way. They simply click the icon on their homescreen and they are in. What is happening behind the scenes is that the email and password are getting saved and the user is being logged into the website via the API every time they click the icon.

Through the growth of RESTful web services we can have it all. We can build both web and mobile apps with greater ease than ever before, by simply reusing the same backend infrastructure for multiple platforms.

Catégories: Elsewhere

Drupal Easy: DrupalEasy Podcast 149: Magnetic Pants (Erik Baldwin and Mike Herchel, Florida DrupalCamp 2015)

mar, 07/04/2015 - 15:19
Download Podcast 149

Erik Baldwin (BLadwin) and Mike Herchel (mherchel), two of the featured speakers for Florida DrupalCamp join Ted Bowman and Mike Anello to talk about their sessions, the other featured speakers, and the wide-range of other activities going on around this weekend's camp. We also pay our respects to Aaron Winborn, discuss content types and other entities, D8 Accelerate, and a host of other Drupal-related topics from the past few weeks.

read more

Catégories: Elsewhere

Drupalize.Me: Backbone.js and Underscore.js in Drupal 8

mar, 07/04/2015 - 15:05

The Drupal 8 development cycle has definitely been a long one. There are several exciting features on the way, but the improvements to the authoring experience in Drupal 8 have definitely drawn a lot of attention. (I know Amber is clamoring for in-place editing for this blog.) The Spark project is the home to much of this work. Several new core modules that contribute to these improvements (Contextual, Quickedit, Toolbar, CKEditor and to a lesser extent, Tour) leverage a pair of popular javascript libraries Backbone.js and Underscore.js.

Both Backbone.js, and its dependency Underscore.js were committed to Drupal 8 two years ago! Let's take a quick look at both Backbone.js and Underscore.js, how they're used in core, and how you might be able to use them to simplify some javascript for your site.

Catégories: Elsewhere

Zivtech: Accessibility in Drupal Themes

mar, 07/04/2015 - 13:00

We at Zivtech care about accessible websites and strive to make our projects usable by the widest range of people possible. We aim to produce websites that adhere to Section 508 standards and WAI-ARIA guidelines.

Sometimes a client has specific needs for compliance, like a government or university website. In general though, accessibility should be a goal for any website, so that users of any ability can meaningfully interact with the Internet.

With that in mind, you may find yourself focussing on ensuring old browser support, like IE (Internet Explorer) 10 or earlier. You want the widest audience using your website. Yet worldwide browser statistics show IE 8 at around 3-4% usage over the last year. Since IE 9 and 10 auto update to IE 11, their usage is nearly non-existent at this point. (note: Some clients need old browser compliance, but that is less often the case.) At the same time, it's possible that more of your website visitors have low vision. Thus it's arguable you'll get a higher return on your development dollars if you prioritize accessibility rather than IE 8 support.

To provide accessible websites, Zivtech produces a contributed starter theme for Drupal called Bear Skin. It was recently updated to include more accessible markup, and is free for use.

Accessibility in the Bear Skin theme

We made our Drupal theme more accessible by focussing on three major sets of updates: semantic markup, 508 compliance, and ARIA. The first two sets, markup and 508 compliance, are really the "low hanging fruits." They provide great enhancements, but require the least effort. Letting Drupal render accessible markup with ARIA is more time intensive, but ultimately provides the best experience for screen readers.

Semantic Markup

Semantic markup comprises the intent and purposes of HTML5 standards. These standards introduced several new HTML elements and deprecated some others. Ensuring your theme markup uses semantic HTML is the easiest way to provide a minimal amount of accessibility for people with screen readers or other assistive technology.

My favorite resource for keeping up with HTML5 standards is the HTML5 Doctor website. They provide contextual documentation for standards, including sample markup. It's easy to compare your Drupal theme markup with compliant HTML5 markup, and suss out where you need improvements.

While it may seem like a big task, we found it pretty straightforward to update Bear Skin's markup. For example, the main content area of the page uses the main HTML element. Also, the previous Bear Skin revision used the hgroup element to group titles and subtitles on pages. Yet that element has been removed from the HTML5 spec, and was plucked out of Bear Skin as well.

508 Compliance

Many of the requirements for 508 compliance are thought of as best practices for HTML, so it's likely your Drupal theme is nearly compliant already! For example, Section 508 stipulates that images need meaningful alt tags and each form element needs a meaningful label. These two examples are things you hopefully have in your theme already.

While updating Bear Skin, we also went over this 508 compliance checklist provided by WebAIM. Some additional features added to make Drupal 508 compliant were skip links to direct a user straight to the main page content, and ensuring the page is still usable without CSS.

WAI-ARIA Integration

The Web Accessibility Initiative section of W3C created ARIA standards as a way to provide screen readers the ability to meaningfully interact with a web page. ARIA standards are very in depth and wide-reaching, and can be somewhat confusing at first glance.

If you're going to review your own Drupal theme for ARIA compatibility, take a look at this spec produced by the W3C, Using WAI-ARIA in HTML. It includes all the basics of ARIA, as well as a short table of commonly used elements.

Landmark roles and aria-* properties are sprinkled throughout Bear Skin, and can provide your own website with a great base-level of support for screen readers.

Testing Tools

Before beginning your adventure in making your website more accessible, or after you've made updates for 508 & ARIA compliance, there are some tools available to help validate your work.

While it's not yet perfect, the regular XHTML validator is good about spotting errors in ARIA. Since a lot of Section 508 is also considered best practice for HTML, the validator is even better about spotting a lot of 508 compliance pitfalls.

WebAIM produces a tool for accessibility checking called WAVE. It can review your site for many things, like 508 compliance and ARIA. It also checks more general things like ensuring high enough contrast between text color and its background color.

If your website is in development or behind a firewall, you might not be able to provide a public link for the WAVE website. If that's the case, you can use a toolbar for Firefox or a plugin for Chrome.

Accessible Development and Design at Zivtech

Zivtech is experienced with adhering to government standards for accessibility, and it's important to us that people of all abilities can use your website. If you need help making your current website more accessible, or if you want to start a fresh site with a focus on accessibility, contact us for help.

Terms: DrupalDrupal PlanetaccessibilitySection 508 Compliancethemingbear skin
Catégories: Elsewhere

Web Wash: Create a Frequently Asked Questions Page Using FAQ Field in Drupal 7

mar, 07/04/2015 - 12:45

Frequently asked questions, or FAQ for short, are fairly common on websites these days. A good FAQ page can help in reducing the number of support requests for basic questions. Whenever I need help on a website, the first thing I look for is the FAQ page before I contact them.

In Drupal, a FAQ page can be created in a few ways. First, you could write the HTML and anchor tags by hand or you could use a module like FAQ Field.

The FAQ Field module comes with a custom field called "FAQ Field" which you can add to any type of entity. It also has a few handy formatters to display the FAQ.

I should also mention that you can use the FAQ module to create these pages. The biggest difference is that the FAQ module has its own content type, whereas, the FAQ Field is based around a field. This is useful for creating FAQs on a Product content type.

In this tutorial, you'll learn how to setup and use the FAQ Field module. We'll add the field to the "Basic page" content type that comes with the standard installation of Drupal.

Catégories: Elsewhere

Wim Leers: renderviz: tool visualizing Drupal 8's render tree

mar, 07/04/2015 - 10:37

I’m working on making Drupal 8 faster as part of my job at Acquia. The focus has been on render caching12, which implies that cacheability metadata is of vital importance in Drupal 8.

To be able to render cache all things that can possibly be render cached, Drupal 8 code must:

  • set the right cache max-age — to ensure only the cacheable parts of the page are cached
  • set the right cache contexts — to ensure content is varied as expected (per language, per role, per timezone, per user …)
  • set the right cache tags — to ensure rendered content is invalidated when the data it depends on is modified

Before Drupal 8, approximately zero attention was given to cacheability of the rendered content: everything seen on a Drupal 7 page is rendered dynamically, with only the occasional exception.

By flipping that around, we make developers more conscious about the output they’re generating, and how much time it takes to generate that output. This in turn allows Drupal 8 to automatically apply powerful performance optimizations, such as:

  1. enabling Drupal’s internal page cache (for anonymous users) by default: d.o/node/606840, which requires cache tags to be correct
  2. smartly caching partial pages for all users (including authenticated users): d.o/node/2429617, which requires cache contexts to be correct
  3. sending the dynamic, uncacheable parts of the page via a BigPipe-like mechanism: d.o/node/2429287

(The first of those three will likely happen this week. We’re working hard to make the last two a reality.)

Visualization

Caching means better performance, but it also means that without the correct cacheability metadata, the wrong content may be served to end users: without the right cache contexts, the wrong variation may be sent to a user; without the right cache tags, stale content may be sent to a user. Therefore we should make it as easy as possible to analyze the cacheability of a rendered block, entity (node/user/taxonomy term/…), view, region, menu, and so on.

It should work not only for cacheability metadata, but for all bubbleable metadata3: it’d be very valuable to be able to see which part of the page caused an expensive cache context or tag 4, but it’d be at least equally valuable to see which part of the page attached a certain asset5.

Since bubbling happens across a tree, it’s important to visualize the hierarchy. The best hierarchy visualization I know in the web developer world is the Firefox Developer Tools 3D view.

I think a tool for visualizing, analyzing and understanding the bubbleable metadata (cache contexts, cache tags, cache max-age, assets) should work in a similar way. The developer should be able to:

  • look at the document in 3D in different layers and/or queries (assets, cacheability as a whole, but also only cache contexts, only cache tags, or only max-age)
  • zoom in a specific element, and look at all of its bubbleable metadata
  • reposition the 3D view, to look from different angles — humans are very proficient at processing visual data
Prototype

So, over the past weekend, I worked on a prototype. I read the CSS Transforms spec6 and read a CSS 3D transforms introduction. As somebody with little CSS knowledge and not having touched CSS nor 3D programming in years, it was fun to play with this ) The result:

And finally, a short screencast demonstrating it in action:

Give it a try yourself by applying the attached patch to Drupal 8 at commit daf9e2c509149441d4d9a4d1964895179a84a12c and installing the renderviz module.

Want to help?

There are many rough edges — actually there are only rough edges. Everything needs work: CSS, JavaScript, UI (there isn’t any yet!), even the name!

But it’s a lot of fun to work on, and it’s very different from what most of us tend to work on every day. If you’d like to be able to build sites in Drupal 8 with a developer tool like this, please contact me, or leave a comment :)

  1. Avoiding to render exactly the same chunks of HTML endlessly on every request. See d.o/developing/api/8/render/arrays/cacheability

  2. For more about that, see the Render caching in Drupal 7 and 8 talk I did with Fabian Franz & Marco Molinari at DrupalCon Amsterdam. 

  3. Drupal is all about reusable content and reusable components. That’s why starting in Drupal 8, we don’t attach assets at the page-level (i.e. global), but we attach them to the places where we actually need them (e.g. when rendering a taxonomy term, we attach the assets to style the taxonomy term to the taxonomy term’s render array). They then “bubble” the render tree, just like JavaScript events bubble the DOM tree. The assets bubble all the way to the response level, i.e. to a HTML response’s <head> element. Similarly, cache tags and contexts bubble to a response’s X-Drupal-Cache-Contexts and X-Drupal-Cache-Tags headers. 

  4. A cache tag is expensive if it’s invalidated relatively frequently (which causes all render cache items that have that tag to be invalidated). A cache context is expensive if it causes many variations (for example: per-user caching requires a variation of the render array to be created for every single authenticated user). 

  5. In Drupal 8, all assets are defined in asset libraries, which can contain any number of CSS or JS assets, and which can depend on other asset libraries. See d.o/theme-guide/8/assets

  6. Firefox’ 3D view is built using WebGL, not CSS Transforms. We might eventually need that too, but not just yet. Oh, and for the origins of Firefox’ 3D view, see https://github.com/victorporof/Tilt

  • CSS
  • DX
  • Drupal
  • WPO
  • performance
Catégories: Elsewhere

Chapter Three: Spreading the Drupal Knowledge

lun, 06/04/2015 - 21:04

The Chapter Three team is getting out and about this weekend to attend two Drupal camps on opposite sides of the country.  These camps are great opportunities to learn new skills and connect with the Drupal community. Looking forward to seeing you there!



Bala Bosch, Andy Klepner, Drew Bolles and Casey Wight will be at Florida Drupal Camp in Orlando.



Casey and Drew are presenting on some advanced theming concepts:

Catégories: Elsewhere

Chen Hui Jing: Drupal 101: Customising field markup with Display Suite

lun, 06/04/2015 - 02:00

A minor complaint I often have about Drupal is the mess of markup it generates. Don’t get me wrong, there are times when all those default classes help when it comes to styling, but there are also times when there is so much nesting it puts Inception to shame. (This is a repeat joke, excuse me if you’ve heard me mention it before.)

This post actually came about because I was trying to include using Display Suite to set up fields as an optional step in the alternative method for accordions post. However, that step ended up being so ridiculously long it warranted its own post.

  1. Install Display suite. drush dl ds -y
  2. Enable Display Suite,...
Catégories: Elsewhere

Chen Hui Jing: Drupal 101: An alternative method for accordions

lun, 06/04/2015 - 02:00

Accordions are commonly used graphical control element. The Yahoo Design Pattern Library has a good explanation on the purpose of accordions, as well as recommendations on their usage. Accordions are usually used when you have limited space and a long list of related items. Seriously, the Yahoo Design Pattern Library is a valuable reference for all designers. I recommend you bookmark it.

There are a number of Drupal modules that help implement accordions (just google drupal accordion), but they didn’t really fit my particular use-case, so I did my accordions differently. This method was a little complicated and required some jQuery, but fit my use-case well.

Create the Accordion content type

Required modules

Acquia: Streamline your local Drupal workflow with Acquia Dev Desktop 2

lun, 06/04/2015 - 01:50

Since we introduced the original version of Acquia Dev Desktop, thousands of people have used it to quickly create local Drupal sites on their Mac or Windows PCs. Over the years we have received a lot of great feedback, and so we redesigned Dev Desktop 2 from the ground up, incorporating the most requested improvements. Thousands of users have tried the beta version, and now it's ready for prime time. If you haven't upgraded to the latest Dev Desktop 2, download it now and give it a try. It's free!

What's new in Dev Desktop 2?
  • A streamlined UI makes it easy to work with all your local Drupal sites and their code, database or files from the GUI or the command line.
  • A welcome wizard makes it easy to get started with any Drupal sites including:
  • Built-in Acquia Cloud integration lets you host any of your local sites for free, or sync locally with any of your Acquia Cloud sites. More on this below.
  • The latest xAMP stack components are included including Apache 2.4, MySQL 5.5, as well as PHP 5.6, 5.5, 5.4 and 5.3 so you can easily test your site with multiple PHP versions.
  • Drush 7 is configured to manage all of your Drupal sites via the command line. Click Dev Desktop's terminal icon to start a command line pre-configured with Drush aliases for all your sites.
  • Browse, query and edit your local site's database using phpMyAdmin.
  • Take advantage of Dev Desktop's deep integration with Acquia Cloud to:
    • Host your local sites on Acquia Cloud for free. Dev Desktop takes care of packaging up your Drupal site and importing it. Once there leverage Acquia Cloud's scalability, dev and stage team environments, Git workflow, site tests and more.
    • Synchronize any code, database, or file changes between your sites on Acquia Cloud and your local sites. Easily pull or push your code, database or files between Acquia Cloud and the local site running in Dev Desktop.
    • Add modules to your local file system and then click Push code to add those modules to your Acquia Cloud site and git repository without using Git. Use Git directly for more complex operations.
    • SSH in to your Acquia Cloud environment by clicking the terminal icon. Use drush commands to manage it.
    • When pulling an Acquia Cloud site database locally, use the sanitize checkbox to scrub the local database's user emails and passwords to keep it secure and prevent accidental email blasts while working on your site.
    • Already using Acquia Cloud? Clone any of your Acquia Cloud sites locally to work on them in Dev Desktop and your local toolchain.

And much more
  • Keep up to date with the newest Dev Desktop features and fixes by selecting the Check for updates menu. This is also done automatically when Dev Desktop starts.
  • Take advantage of the command-line installer to script the installation on multiple machines, or embed it as part of another installer that includes your custom Drupal distrobution.
  • Create multiple sites sharing the same codebase using Drupal multi-site.
  • Easily report feature suggestions or issues via the menu Help > Report an issue.
See it in action!

With these improvements Dev Desktop 2 is the fastest way to create Drupal sites on your Mac or Windows PC, and optionally sync them at any time with Acquia Cloud. Download it now, and try it out! There are more great things in the works so be sure to check for updates regularly.

Tags:  dev desktop acquia drupal planet
Catégories: Elsewhere

agoradesign: 3rd party library integration in Drupal 8

sam, 04/04/2015 - 14:24
During my work on the D8 port of our Outdated Browser module, I’ve got in touch with several API changes of Drupal 8. One of them I want to describe now is the integration of third party Javascript libraries.
Catégories: Elsewhere

Jimmy Berry: Drupal testbot command line tool

ven, 03/04/2015 - 23:31

Are you a developer familiar with the patch submission workflow?

  • load the issue page in your browser
  • add some helpful text describing the patch
  • create a patch file
  • upload it to the issue
  • change the issue status to 'Needs review'
  • wait 20 minutes (at best) to find out if the tests pass or fail with your patch

If the tests fail, then you get to do it all over again, including making possible revisions to the issue summary.

Ever wanted to run the tests while iterating on a change, but are reluctant due to:

  • insufficient local machine resources or configuration to run tests efficiently
  • inconsistent results compared to the official testbot
  • disruption of your 'creative coding moments' due to the patch submission workflow
  • long test runtime on qa.d.o

Well you may be in luck.

What if you could type "drush testbot" to have the changes in your working branch submitted and tested as a patch against Drupal? And be able to view the results in five minutes or less? If this sounds interesting, then install the "drush testbot" command file (see instructions) and take it for a spin.

Suggested usage

If your changes only affects a single module (or a few), then an assessment of your changes can often be had by simply running the tests for that module (or those modules). Once you know that your changes do not break the immediate context, then the entire test suite can be run before posting the patch on the issue queue.

You can do so by including a list of test classes to run (see examples); in so doing you might reduce your response time to a matter of seconds.

Drupal 8 examples

Run the command from the working directory with your code changes. The default test environment for Drupal 8 is mysql 5.5 and php 5.4. In lieu of setting properties on the command line, add them to a '.testbot' file in the repository root directory (i.e. the same directory that contains the .git directory).

Description Command All defaults (without .testbot file) drush testbot Using properties from .testbot file drush testbot Single test class drush testbot --properties='{"classes":["Drupal\taxonomy\Tests\TermTest"]}' Alternate environment and multiple test classes drush testbot --database='mongodb-2.6' --php-version='php-5.5' --properties='{"classes":["Drupal\node\Tests\NodeQueryAlterTest", "Drupal\node\Tests\NodeRevisionsTest"]}' Drupal 7 examples

The default test environment for Drupal 7 is mysql 5.5 and php 5.3. The command syntax matches that shown above with the addition of the 'branch:7.x' parameter to the properties. An example of testing two classes is:

drush testbot --properties='{"branch":"7.x","classes":["NodeQueryAlter","NodeRevisionsTestCase"]}' Instructions

Point your browser to https://github.com/reviewdriven/testbot and see the README file for installation instructions.

Caveat

If our test queue is empty when you submit a patch (and do not specify a list of classes to test), the actual response time for a Drupal 8 patch will be under ten minutes based on existing test suite and available hardware at the time of this writing. If the queue is full, we may not run your patch and will let you know.

Final thoughts

If you have questions, would like to offer constructive comments or suggestions, or want to let us know that you found the tool useful, please post in the github issue queue.

The testbot is provided as a complimentary service to the Drupal community. No financial assistance is received from the Drupal Association (to defray even the hardware costs). Unlike the current testbot which runs on the most powerful compute instances offered by Amazon Web Services, these tests are run on hardware with roughly 25% the processing power yet return results in under half the time.

Tags:
Catégories: Elsewhere

DrupalCon News: Higher Ed Summit: More tickets!

ven, 03/04/2015 - 23:13

Did you miss your chance to sign up for the Higher-Ed Summit? This first-ever event is so popular that we already sold out. Clearly, higher-ed is a lively crowd!

But worry not, college or university Drupalers: second chances do exist. We will release an additional twenty tickets on April 13 at 12:00pm (Pacific Standard Time).

What will I learn?

Our most suggested topics are:

  • Maintaining brand consistency on sites across campus

Catégories: Elsewhere

Freelock : Drupal 8 is around the corner... time to upgrade?

ven, 03/04/2015 - 21:51

We're starting to recommend Drupal 8 for some new upgrade projects, with the following notes...

Drupal 8Drupal Planet
Catégories: Elsewhere

Zivtech: Drupal Jeopardy

ven, 03/04/2015 - 21:31

Drupal 7 Core Site Building Jeopardy helps your team study for the Acquia Site Builder certifcation, or just brush up on your Drupal core knowledge.

We have a weekly "Dev Lunch" on Fridays and lately we've been studying some of the topics covered by the various Acquia certification tests, to help junior staff fill in the gaps of their Drupal skills. This week we mixed it up by playing Jeopardy questions I made up, using a nice web app (jeopardy.rocks) by Muno Creative.  

We had no problem including a few remote colleagues via Google hangout, and we used our regular Hipchat room with team emoticons to buzz in. Congratulations to Team Eggplant (Steve, Dima, Jeff and Victor) who won the game and are enjoying their prize (RC helicopters).

Let us know if your group plays and how you like it. This could be fun for a meetup event as well.

jeopardy.rocks/zivtech

Terms: DrupalDrupal PlanetJeopardyAcquiacoresite building
Catégories: Elsewhere

X-Team: Deep dive into the anatomy of Drupal 8 theming

ven, 03/04/2015 - 19:36

Drupal 8 is the most advanced Drupal ever built and it will surely will be a game changer among other CMSes out there. Part of its strength comes from adopting the principles from other technologies like Symfony, YAML, Twig, and Backbone.js. The theming has undergone many changes since Drupal 7, especially the deep integration with...

The post Deep dive into the anatomy of Drupal 8 theming appeared first on X-Team.

Catégories: Elsewhere

Pages