Skip to Content

Planet Drupal

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 1 hour 32 min ago

Mediacurrent: Using Third Party Wrappers

8 April 2015 - 12:52pm

Chances are decent that at some point you've needed to provide some third party service with styling information so that they can have their service look as though it were part of your website. The types of services this could apply to could range widely from external e-commerce platforms to HR and other internal tools. Furthermore, they could either include this HTML directly or with a link to files that you host.

Categories: Drupal

Acquia: PHP: The entire world is your development team – Beth Tucker Long

8 April 2015 - 9:31am
Language Undefined PHP: The entire world is your development team – Beth Tucker Long

Categories: Drupal

Wellnet Blog: Weekly Module Review - #6 Quicktabs, create tabs in an easy way!

8 April 2015 - 8:25am

I’m developing a website and I had the need to have a page created with Views and divided in two tabs.
I know that it can be easily done by code, but I was interested in find a module that suits me.
And I found it! It’s called Quick Tabs.

Categories: Drupal

Drupal Watchdog: Connecting Drupal to Salesforce in Three Easy Steps

8 April 2015 - 7:20am
Article

The Salesforce Suite of Drupal modules is an easy way to connect Drupal to Salesforce, a Customer Relationship Management system used by retailers and non-profits alike, which allows non-technical staff to create extensive reports – reports that would be difficult to create using Drupal alone.

Although entities can be synchronized to Salesforce objects – and custom mappings created – there is lots more that can be done with Salesforce. Let’s take a look.

Getting started

For openers, you’ll need:

To get the Developer Edition, create a developer account.

Once you’re in Salesforce, you’ll quickly notice that the site seems overwhelming. A complete overview is way beyond the scope of this article; the most important objects for our purposes are Campaigns, Leads, Contacts, and Cases.

There are many other extensions for Salesforce, extensions that provide new object types. Also, existing object types can be extended in much the same way as in Drupal.

As a best practice, always work in a sandbox environment when not working within a dev instance. It will help ensure that you can create a proper development -> testing -> production workflow.

To create a sandbox (Enterprise, Performance, Unlimited, and Database.com), go to Setup » Sandboxes » Create new Sandbox.

Categories: Drupal

Drupal Watchdog: Connecting Drupal to Salesforce in Three Easy Steps

8 April 2015 - 7:20am
Article

The Salesforce Suite of Drupal modules is an easy way to connect Drupal to Salesforce, a Customer Relationship Management system used by retailers and non-profits alike, which allows non-technical staff to create extensive reports – reports that would be difficult to create using Drupal alone.

Although entities can be synchronized to Salesforce objects – and custom mappings created – there is lots more that can be done with Salesforce. Let’s take a look.

Getting started

For openers, you’ll need:

To get the Developer Edition, create a developer account.

Once you’re in Salesforce, you’ll quickly notice that the site seems overwhelming. A complete overview is way beyond the scope of this article; the most important objects for our purposes are Campaigns, Leads, Contacts, and Cases.

There are many other extensions for Salesforce, extensions that provide new object types. Also, existing object types can be extended in much the same way as in Drupal.

As a best practice, always work in a sandbox environment when not working within a dev instance. It will help ensure that you can create a proper development -> testing -> production workflow.

To create a sandbox (Enterprise, Performance, Unlimited, and Database.com), go to Setup » Sandboxes » Create new Sandbox.

Categories: Drupal

Drupal @ Penn State: Drupal speed tuning: analyzing and further optimizing Pressflow

8 April 2015 - 6:06am
If you've read my past posts on here, you'll probably find a trend: I'm obsessed with performance tuning. Any time you can get more responsiveness without more hardware, I'm very, very happy. I've been running a modified drupal core for ELMSLN for some time now and decided instead of keeping these changes / tuning to myself, I'd try and document them / test them and see if any changes make sense for pressflow. In https://github.com/btopro/Presser-Flow-FORK you can see 3 folders: _PATCHES - all the patches (from drupal.org) utilized in the metrics _RECIPES - a drush recipe that auto optimizes to the level used in testing, there are also recipes for each of the sites in the test so you can see exactly what was used for testing. _METRICS - XLS file with detailed metrics of how testing was performed, where, and what combinations
Categories: Drupal

Drupal @ Penn State: Drush recipes cookin' up sweet beta eats!

8 April 2015 - 6:06am
Drush Recipes has come a long way since the project was first announced on planet a month ago.
Categories: Drupal

Drupal @ Penn State: ELMSLN optimization: Cost and Scale

8 April 2015 - 6:06am
I did a post the other day about ELMSLN Performance Optimization all about lessons learned and looking at some popular techniques and applying them. These are techniques that can be applied to ANY Drupal (and in many cases non Drupal) application to increase performance. This article looks at the real world price of performance tuning.
Categories: Drupal

Drupal @ Penn State: ELMSLN performance tuning

8 April 2015 - 6:06am
Update 2: Apache tuning / Costs There’s another posting thats dedicated to the cost and scale metrics of ELMSLN vs D6 legacy systems we were using. This is an example performance pack of conf settings that should work to do sane tuning on ANY apache system let alone drupal.
Categories: Drupal

Drupal @ Penn State: Drupal, Singularity, Digital Activism, and saving our institutions

8 April 2015 - 6:06am
It is as important to tell a great story using technology as it is to author technology that allows more stories to be told.
Categories: Drupal

Modules Unraveled: 132 How and Why Acquia is Training Drupal Talent Before They Hire Them with Amy Parker - Modules Unraveled Podcast

7 April 2015 - 10:00pm
Published: Wed, 04/08/15Download this episodeAcquiaU

While this episode might end up sounding like a giant advertisement for AcquiaU, it’s really not intended to be. I wanted to have you on to talk about the concept of, how a company that hires Drupal developers, can and should go about training them before they are hired.

In order to set the backdrop for the rest of our conversation, I’d like to quote a bit from the AcquiaU website:

The challenge the community is facing is one of supply and demand. Simply put, there just aren’t enough people to fill the needs. At any given time in the past 6 months, job aggregator Indeed.com has over 2,500 open position across the US for Drupal talent.

How do we close the gap? Find the people with the right passion and grow their talent from the inside-out. We're not looking for people with years and years of Drupal experience. We're looking for people who are curious, motivated, determined, and who can inspire a little crazy in us all. At Acquia, culture and a person's POTENTIAL to contribute and grow with us matters. A lot. These are the underpinnings of a successful candidate.

What I love about that is that you’re not looking for senior level developers with 5+ years experience. Because you’re not going to find them. They all already have jobs.

Mike and I ranted about that in the last podcast, so I won’t rehash it here, but what we boiled it down to is that Drupal shops need to create a talent pipeline for recruitment, which, as I understand it, is essentially what AcquiaU is for Acquia.

Ok, with all that said, I’ll shut up now, and let you do the talking.

  • Can you give us your description of what AcquiaU is?
  • The program is 14-weeks of hands-on training in Drupal, Acquia Products, related web technologies, and professional development skills like team building, leadership, and communication skills. We spend the first 6 weeks in a classroom environment, which is a combination of lecture, group projects, individual assignments, and self-paced learning. The most recent graduates’ project was to redesign the program’s website, u.acquia.com Each participant is assigned an Acquia Mentor who is there to not just be a buddy, but to help from a technical perspective. The next 8 weeks are spent with job rotations where they work with our customer facing Professional Services developers and customer support. Each person is assigned a client team and works side-by-side on real projects. You might think it is like any other tech bootcamp out there but we differentiate ourselves in a couple of key areas. First, we make sure we have an open job opportunity for each person who joins the program and second, we pay people to learn. Many other bootcamps have a high cost- on average up to $10,000 and while they help with job placement, I can’t say how many have jobs lined up for graduates BEFORE they join the program.

  • How do you select your candidates? Or can anyone join the class?

  • We have a rigorous screening process and look for people with 2-3 years of technology experience, but who might not be able to get a job with a development shop. A lot of times, this level of talent is overlooked because companies don’t have the internal mechanisms to train, mentor, and coach junior level talent. They are already stretched thin and want new hires to hit the ground running at a fairly high level of proficiency.

  • What types of skills do you teach?

  • We dive deep into Drupal and other web tech skills like Drush, GitHub, and Agile and a dive into our own products and services. Helping people become well rounded also means that we do workshops in team building, communication skills, and presentation skills. The next session will have an engineering focus so we will be digging into LAMP stack and web architecture.

  • Do the students have any obligation to Acquia at the end of the program? (Like they have to work for you for a given time period after the program?)

  • People are hired on as temp employees and we really hope they have had a great experience and want to stay on. The program’s goal is to hire them at Acquia or with one of our partners.

  • What percentage of students would you say you hire on average?

  • So far we have a 90% hire rate. The goal for 2016 is to expand the program and hire more people into other Drupal shops

  • Do you have information about those that you don’t hire? Do you know if they’re employed somewhere else? Or did they decide Drupal wasn’t for them?

Expanding the Concept
  • Now that you have a few classes under your belt, is this something you think other shops should look into doing?

    • People have asked me this and I think they should think about what the end goal is. Our program is not to just train more people for Acquia, but to give back to the Drupal community by creating a long-form drupal training program with learning paths and a structured hands-on curriculum.
  • We were talking before we started recording about this idea. Mike had mentioned that shops should create a talent pipeline. And while I agree with that in theory, what that means is that the shops first have to develop a training program, and one or more people who are skilled at both Drupal and teaching in a way that doesn’t alienate the trainee. From your perspective, how would you respond to that?

    • Having a talent pipleline means that you have a people development strategy that aligns to your business strategy, and that you have launched that people plan long before you launch the business strategy. Most companies play catch-up and are more reactive than proactive. Being proactive means you’re looking ahead 2-4 years out and making plans for your people.
  • If there is a shop owner out there listening right now, what would your advice be on how to go about creating a program like this?

    • I think you really have to be prepared to commit. Budgets need to allow for hiring junior talent, the business needs to be ready to bring in this level of need. It takes a lot of planning to launch a program like this. For companies that can’t support hiring 5-10 junior level talent, they should start out with a smaller number. A really strong learning program doesn’t just focus on the skills, but on different ways that people will need to learn and being able to translate really complex ideas into ways that different people will relate to. If you’ve ever heard about the adult learning cycle and experiential learning, we know that people tend to be most successful learning new skills when they can reach back into their own experience and apply them to the new content. Being a really strong developer doesn’t always mean that you can tap into other peoples’ experiences and make it relevant to them now. So when you look at creating that pipeline and having junior level talent come on board, you also have to figure out the most effective way to do it.
Episode Links: Amy on TwitterAcquia on TwitterAcquiaU on TwitterAcquiaU WebsiteTags: JobsCareersHiringplanet-drupal
Categories: Drupal

Promet Source: My Experience with Acquia Certification

7 April 2015 - 2:03pm
My Advice

 

Preparing for the exam:

- Review this great guide: Five Steps to Get Ready for the Acquia Certified Developer Exam (pdf)

- As the guide says, review topics (in the pdf appendix) and identify your weaknesses, read up on your weaknesses.

Categories: Drupal

Drupal Easy: Drupal Goes to College

7 April 2015 - 1:04pm

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

Categories: Drupal

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

7 April 2015 - 11:52am

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:

Categories: Drupal

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

7 April 2015 - 10:30am
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.
Categories: Drupal

Mediacurrent: Mediacurrent Dropcast: Episode 3

7 April 2015 - 9:40am

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.

Categories: Drupal

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

7 April 2015 - 6:19am
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

Categories: Drupal

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

7 April 2015 - 6:05am

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.

Categories: Drupal

Zivtech: Accessibility in Drupal Themes

7 April 2015 - 4:00am

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
Categories: Drupal

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

7 April 2015 - 3:45am

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.

Categories: Drupal


Google+
about seo