Drupal

bojanz's blog: How Devel causes heisenbugs

Drupal Planet - Sat, 2014-04-19 13:52
Here’s what killed my Friday. The story has been edited to remove pain, suffering, prolonged coffee intake. Read more...
Categories: Drupal

Frederick Giasson: Configuring and Using OSF FieldStorage (Screencast)

Drupal Planet - Fri, 2014-04-18 15:07

This screencast introduces you to another one of the most important OSF for Drupal connector: the OSF FieldStorage module. What this module does is to create a new FieldStorage type for Drupal7. It enables Drupal7 to save the values of its Content Types fields into another storage system than the default one (i.e MySQL in most of the cases).

Because of the way that the Field system has been designed in Drupal7, it is possible to save the values of different fields that compose the same Content Type bundle into different field storage system. For example, if your Content Type bundle is composed of 10 fields, then 4 of them could be saved into MySQL and 6 of them into OSF.

The main purpose of the OSF FieldStorage module is to be able to save Drupal local Content Type information into OSF. What that means is that all your Drupal7 local content then become accessible, manageable and manipulatable using the 27 Open Semantic Framework (OSF) web services endpoints. Your local Drupal content can then be shared with other Drupal instances that could use OSF for Drupal to connect to that same OSF instance and seamlessly republish/re-purpose that local content from the other Drupal portal.

Here is the documentation of the architecture of this connector module.

This is the power of the OSF FieldStorage connector module. It supports the following Drupal features:

  1. Full FieldStorage API
  2. Entities caching
  3. Revisioning
  4. SearchAPI
  5. 29 field widgets
  6. Export feature in 6 formats

In this screencast, you will be introduced to Drupal7′s Field system. Then you will see how the OSF FieldStorage module creates a new FieldStorage type for Drupal7 and how it can be used. Then you will see how to configure the OSF FieldStorage module: to creating new Content Type fields that uses this osf_fieldstorage type, how to map these fields to RDF, how to use one of the 29 supported field widgets, etc.

Finally, you will see how you can synchronize existing Content Type pages (that was created before OSF for Drupal was installed on your Drupal instance) into a OSF instance.

 



Categories: Drupal

Drupalize.Me: Hiding form fields in Drupal 8

Drupal Planet - Fri, 2014-04-18 15:00

If you have worked with the Field UI in Drupal 7 you will know that you are able to prevent fields from being displayed when viewing entities (e.g. content, users etc). It was fairly simple, you would go to the Manage Display tab of an entity and move the field to the ‘Hidden’ region as shown in the screenshot below.

So you could hide a fields output from being displayed when viewing that entity. But what about when editing that entity? There was no way in the Drupal 7 Field UI to hide a field on a form. You would have to write some form of hook_form_alter() in a custom module and manually force the field to be hidden, like shown in this example.

Categories: Drupal

InternetDevels: Drupal and high-load projects. Myth or reality?

Drupal Planet - Fri, 2014-04-18 14:03

One of spring days 2012 brought us a new project. One of our regular customers recommended our company to a very ambitious and engaged Moscow businessman. After reading the specifications we were at a loss… after 5 years of active web-development! HiConversion project demanded the following:

Read more
Categories: Drupal

.VDMi/Blog: Paragraphs: content editing reinvented

Drupal Planet - Fri, 2014-04-18 09:50
The biggest problem of the modern web is that non-tech-savvy users have to manage the content. Those people can quite mess up your responsive layout with their way too big tables, inline images and text marked up with Word. That's why we invented Paragraphs, less to mess up, but still the flexibility of WYSIWYG.

Let's face it, the web has evolved. But what about content editors? Dit they evolve with the web?

Most of them still like to paste everything they can find into a big WYSIWYG texarea. That's not a viable option when you want to build responsive website. It gets even hard when you want to use cool technologies like responsive images. Wouldn't it be awesome if you had all those pictures in image fields, or maybe even better, in Scald? Behold: Paragraphs!

We developed Paragraphs to be a full blown replacement of the default body field. It's comparable with Inline Entity Form, except that you can use different types of bundles in the same field. It also comes with content editing features like having your paragraphs collapsed by default. More features are on the way!

Some examples of Paragraph Bundles that we have created in the past:

  • Slideshow - A simple slideshow in your content:
    - Create a slideshow Paragraph bundle.
    - Add a multi-value image field.
    - Use a slideshow formatter.
  • Youtube embed - A Youtube embed between your text blocks:
    - Create a Youtube Paragraph bundle.
    - Add a simple embed field. 
    - Tweak the formatter settings to fit your needs.
  • Customer Quote - Add a personal quote/review from your customer in your content:
    - Add a author, text and optional email field.
    - Theme it to your style, with bundles-specific templates.

The bundles above are use-case-specific, we often start with the following bundles:

  • Text: a simple WYSIWYG textfield with the basis buttons enabled, like bold and italic.
  • Text Left, Image Right: same as above, but with an image on the right of the text.
  • Text Right, Image Left: same as above, but with the image on the left.
  • Fullwidth image: an image that takes the full width of the content.

All paragraph bundles have their own display settings and view modes, just like nodes! Because of that, every paragraph item also has it's own theme suggestion.

Because of the seperation of content, it's great for a responsive site. For example: Just add a wrapper around your slider paragraphs that hides the slider on mobile, or makes it smaller on tablets.

Excited already? Try it out!
Want to know more? Check the project page.

Note: Paragraphs is also useful if you want to build a Drupal site with Parallax scrolling. More on that later!

Categories: Drupal

NYC Camp News & Announcements: NYC Camp Keynote by Atefeh Riazi (UN CITO, ASG)

Drupal Planet - Fri, 2014-04-18 00:37

Last Saturday afternoon, we were very fortunate to have Atefeh Riazi, UN CITO and Assistant Secretary General (ASG), deliver a keynote presentation to the 500+ Drupalists in attendance.

Salem Avan delivered the introduction to the keynote, and spoke about "we the people" and our inherited collective responsibility to help advance the UN's goals of furthering peace and security, international development, and human rights.

Ms. Riazi then delivered a riveting keynote that was a call to action for the Drupal community to help use technology to better the world. She emphasized the importance of leveraging innovation, collaboration and partnerships in order to solve the global challenges we face, and to respond to this call to action in a coordinated manner through partnerships that bring all of our best resources to bear.

Her exciting keynote address was followed-up with a stirring panel on  Women & Technology Leadership, that featured Mr. Riazi, Holly Ross (Executive Director or the Drupal Association), and Angie Byron (webchick). The panelist explored the pivotal importance of furthering female leadership is technology circles, and particularly the Drupal community. 

You can watch the full keynote here on UN WebTV.

You can also view the Flickr photo album from the Keynote here and the Panel Discussion here

Thanks again to the UN Office of Information Communications Technology (OICT) for their generous support of NYC Camp and the Drupal NYC Community. You can find our more about the UN OICT at their websiteFacebook page and by following them on Twitter.

Categories: Drupal

Drupal.org Featured Case Studies: The Woodhouse Day Spa

Drupal Planet - Fri, 2014-04-18 00:28
Completed Drupal site or project URL: http://www.woodhousespas.com

Unleashed Technologies developed an enterprise platform that easily scales to accommodate The Woodhouse Day Spa’s explosive growth, as they take the company from 30 to more than 200 franchises. The Woodhouse Day Spa can now instantly create franchise sites that are consistent in branding and content, yet managed and updated by the franchisee. All sites for The Woodhouse Day Spa are fully integrated into spa management systems to provide a seamless experience to visitors. The Drupal platform developed for The Woodhouse Day Spa brings usability and control to its franchisees in order to increase engagement and improve ROI.

The Woodhouse Day Spa website won the 2013 Blue Drop Award for Drupal Site of the Year.

Key modules/theme/distribution used: Drupal services JSField PermissionsTaxonomy Access ControlUbercartFeaturesUltimate CronViews Bulk Operations (D8)Nodequeue
Categories: Drupal

Drupal Association News: Drupal Association Board Meeting Summary: 16 April, 2014

Drupal Planet - Thu, 2014-04-17 22:31

Preparing the materials for the monthly board meeting is a lot of work, but it's a great chance to reflect each month on the momentum of the Association and the community. Looking back, March 2014 was particularly exciting as the community and staff are pushing forward in several directions at once with considerable momentum. So let's get down to it and share some of the highlights:

Program Updates

Each month we review the metrics outlined in our 2014 Leadership Plan and share updates from the teams. We're pleased to say that most of our metrics are in the green (within 95% of goal). Particularly exciting is the news about DrupalCon Austin. Numbers looked very solid at the end of March (the end of our reporting period for this meeting), but we are also able to share that early-bird pricing ended just a few days after this dashboard closed and we beat our estimates, meaning that we are more than on-track to have a 4,000 person event this June - another biggest DrupalCon ever!

We are also really pleased with the momentum around the Drupal.org metrics. This is still our area of greatest concern - we have more red metrics here than anywhere else. However, March brought some tremendous gains that, if sustained, will move our metrics quickly towards green. In particular, we focused discussion on:

  • Page Response Time: Our goal is 3.07 seconds. Our current average for the year is 3.93 seconds. Part of the reason that we're so far from goal is that we had some serious issues in January that pushed the numbers way up. Our hardware improvments (thanks to the DIWG and Rudy) have helped speed this up, and the upcoming CDN deployment will bring this number down even further, especially for individuals accessing the site outside of the US. 
  • Testbot performance: Goal is 70 minutes, but actual average for the year is about 138 minutes. This actual is also very inflated by lots of issues we had in January that pushed the total testbot time much higher. Thanks to work done at Drupal Dev Days in Szeged by Jeremy Thorson and Ricardo Amaro, along with some changes to D8 core, the actual tesbot run time average in March was just 47 minutes!
  • Home Page Bounce Rate: This metric is one of the central motivations for the User Research that the DCWG has begun as part of a larger Drupal.org reinvention. We have also begun to put tools like Optimizely in place that will allow us to run tests and experiments based on our research, which should help us address bounce rate, time on site, and other engagement metrics for our various audiences. We likely won's see shifts here for some months, but we are definitely thinking about these metrics and working to put the foundation for a solution in place. 
Procurement Policy

At the Association, we work hard to ensure that our actions are in line with the Drupal community values. This is, of course, particularly important when money is part of the equation. To that end, the Association has a Financial Policies document that is reviewed annually by the board Finance Committee and sets rules for transparently and openly making decisions for how Association money gets spent. Until now, one element that was lacking was a Procurement Policy to govern when we pay for a service (vs. work with a volunteer) and how and when we can take in-kind donations. Back in February, we looked for feedback from the community, and incorporated a lot of the suggestions into a final policy, which was approved by the board in the meeting. 

I would like to add that this policy, though approved by the board, is just a starting place. There is so much nuance that we will encounter as we put the policy into practice. During our annual review of policies, we will have the opportunity to revisit and refine this language. In particular, we want to ensure that we are supporting and growing the volunteers who contribute to the project and not hiring contractors at the expense of the health of our community.

At-Large Elections/Terms

In the March Board meeting, we updated At-Large term length and shifted the election cycle. The goal is to give our At-Large Directors a better board experience by giving them time to integrate into the board and really work on their agendas. With this change, the community will elect one At-Large Director each year to a two-year term. For this to work, we need to stagger the terms of our existing At-Large Directors, Morten DK and Matthew Saunders. Since Morten is serving his second one-year term currently, the board voted in this meeting to extend the terms of Matthew Saunders 1 year. So, in our next election (in February 2015), we will elect a new At-Large Director to fill Morten's seat for two years and Matthew will have one year left in his term.

First Quarter Financials and Annual Audit

In Executive Session, the board reivewed the financials for the first quarter of 2014 and received a presentation of the 2013 Audit report from the Association's auditor. All materials were previously reviewed by the Finance Committee (which meets monthly to review the most recent financial reports), and the Finance Committee recommended approving both the fiancials and the audit. The audit documents are now being produced as final versions (we presented draft documents to the board) and will be shared with the community at the June public board meeting at DrupalCon Austin. If you're ready to dive into some numbers before then, you can review the first quarter financials now:

Lots more happened at this board meeting, and if you're interested, don't forget that you can read the minutes, or watch the recording. And as always, let me know if you have questions.

Flickr photo: xjm

Categories: Drupal

AGLOBALWAY: Agile Principles in Drupal Client Projects

Drupal Planet - Thu, 2014-04-17 19:18

Agile development processes can greatly help your Drupal client projects.  Agile in a nutshell is a highly collaborative process the uses feedback to make constant adjustments to the project.   Often people equate SCRUM with Agile, but that would be a mistake.  You can have SCRUM teams that never truly deeply embrace Agile ideas.   You can have Agile teams who don’t follow SCRUM. 

At the heart of any Agile team is the Agile Manifesto:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Individuals and interactions over processes and tools

With Drupal projects, your have many choices of great tools and processes to use.  Don’t let these things become your focus.  Focus on building great teams including your clients.   Tools and processes are important but not as important as the interactions and shared understand that develops in the team.

Working software over comprehensive documentation

Many Drupal projects include configurations and site building tasks using existing modules.  This begs the question, how much documentation do you need to write?   You should product “just enough” for the team to be clear and not more.  These can be everything from full Software Requirements Specifications (SRS) to a small collection of user stories.  It really depends on the needs of the team. 

Customer collaboration over contract negotiation

Don’t forget that when we speak of team in Agile development, we include the customer and everyone involved on the project.  This attitude creates strong groups including of developers, testers, project manager, and clients working together to create the best website possible.   Creating a collaborative environment should be the priority.

Responding to change over following a plan

All of this collaboration creates increased visibility for everyone involved in the project.  This gives the opportunity for new innovations and ideas to emerge as everyone has developed a shared understanding of the full view of the project.  If you blindly follow the plan, you will not be able to capitalize on new and emerging knowledge over the course of the project.

Drupal developers can greatly benefits from embracing Agile development ideas.  Think about how to structure your projects around shared knowledge, learning, collaborations and clients.

  Tags: drupalAgiledrupal planet
Categories: Drupal

Mediacurrent: Mediacurrent's Kendall Totten to speak at ConvergeSE

Drupal Planet - Thu, 2014-04-17 17:22

ConvergeSE is an immersive web design, development and business conference full of informative worshops and inspiring keynotes. Mediacurrent's own Kendall Totten will be leading the session "Choosing Drupal as a CMS Framework for your next project, which covers a wide range of subjects, such as

  • What is Drupal and what makes it great?
  • What is involved with building & theming a Drupal site.
  • How to get a Drupal site off the ground quickly

Join Kendall on the Front End track, or explore some of the other tracks, such as Design, Gaming, Makers, UX, Development, and Business and Marketing.

Categories: Drupal

Scott Hadfield: Drupal community member interviews with Acquia. You won't believe what happens next!

Drupal Planet - Thu, 2014-04-17 16:55
With apologies to webchick for ripping her brilliant headline ;-) The background:

At the end of 2013 I started to think about where I currently am work-wise, and what I enjoy and want to do with myself now. My drupal-based startup Hello Pretty has been growing at a fantastic rate, and is also self sustaining enough now that I can step away without harming it. We've built it with an ideal of keeping things technically as simple as possible and rather focusing our money & energy on marketing.

In my job at NowPublic I managed the dev team (rather than doing any programming myself. After 20 years of it I've started to get a bit bored). I loved that job and decided that I'd like to get back into that.

In January I began the process of looking for jobs. This would most likely have meant leaving our beautiful home in Cape Town and moving to where the work was. So it was no small decision for Sam and I.

At the end of February two very cool companies for positions I hadn't applied to contacted me two days apart, both through word-of-mouth references from people I've worked with previously. After a handful of rejections in the process already, I was ecstatic. One was in one of my favourite cities in the world, Vancouver :), and the other - Acquia - I've followed since day one of it's existence and have several friends and former colleagues who work there.

After chatting to the company in Vancouver a couple of times, they were quite keen and waiting to hear back on where I stood.

As I write this I keep thinking back to one of my favourite quotes and wondering why I didn't heed this advice sooner. It refers to a person's character or nature, and that how they handle anything small or 'unimportant' most likely reflects how they handle everything big or important.

 

My Acquia Story

 

Note: I don't blame any individual for my experience, but rather a culture within the company. Any names of the people who I spoke to have been changed.

Week 1

Matt from Acquia and I chatted on Skype video for about an hour. He was the person most involved in hiring me, and making a final call. We discussed my skills and qualifications, my salary expectations, and the fact that I had another company waiting for a response from me. He was keen to chat more and would try to keep the process quick so that I didn't have to keep the Vancouver company waiting long. He asked whether I'd be ok to have interviews over the next week. I agreed and said I'd explain the situation to the other company. After those were done there'd still be the meetings with the CEO and CTO of Acquia. He couldn't promise that it would be easy to schedule with them, so there could be additional delays.

This was on Wednesday morning Boston-time.

Week 2

By the following Monday at mid day, 6 days later, I still hadn't heard from them and assumed that he'd changed his mind. Not a big deal. But then, a recruiter from Acquia finally emailed me to schedule some interviews. Yay!

I sent back my schedule and... nothing. I understood from friends that Acquia usually want a few interviews, and the week was quickly coming to an end.

I followed up with the recruiter explaining that there was some urgency and that I didn't want to keep the Vancouver company waiting - I'd already put them off for a full week at this point. In the interest of expediting the process I offered to rearrange my own schedule or meet at short notice. I also asked for a sense of Acquia's timeline.

The recruiter promptly responded by setting up 4 interviews over the next two days. Three of them after 8pm my time, and one of them scheduled from 11:30pm to 12:30am. Ok, I figured, people are busy, and if this was going to get things done sooner, then great. Besides, this would give me bragging rights for having had a job interview at midnight.

After those 4 interviews I was asked to review the product I'd be working with to provide feedback, suggestions, etc. which I did over the weekend. I spent a few hours figuring it out, and working on my review. Obviously I wanted to impress, and the feedback I got from them (on my feedback) was very positive. I was actually really impressed with what I saw. Acquia is doing a lot of very cool stuff that I'd had no idea about.

Week 3

I had now kept the company in Vancouver waiting considerably longer than I'd told them I would. I hate keeping people waiting, in any context, and if I tell someone I'm going to do anything by a certain date or time it's important to me to stick to it. That goes for work and personal commitments.

On Monday (day 13) I'd again had no word. I followed up on Tuesday. "Interviews would be scheduled shortly". Matt asked if it would be ok to do this on very short notice and how late I could meet. Keen to wrap things up, I agreed to meet at any time.

After those next two interviews, radio silence. Matt said he'd "touch base to follow up with next steps". And then more radio silence. Two days later he got back to me to say he was having the recruiter set up more interviews. And sure enough, on Friday that week the recruiter mailed me to arrange a few more interviews.

This was when I started feeling demoralized. Why had they only scheduled two interviews in the entire week when I'd made my schedule completely open to them? Why did they continue to schedule interviews after 8pm for me (that's after 2pm Boston-time) if they were only going to schedule two or three in a week? I knew there was one other candidate, I had no idea where I stood, and it was never communicated to me how many more interviews there might be. I'd made my schedule very flexible for Acquia, and I'd pushed back my other job to the point where I was being straight-up disrespectful to them.

I decided to get back to the guys in Vancouver and figure out next-steps with them.

I've interviewed for jobs in the past, and I've interviewed people for jobs. I'm quite familiar with the "normal" process from both ends. Never had I been involved in, or even heard of, had such a long, stretched out and uncomfortably bureaucratic process. I hardly expected it from a company who claims to want to move quickly, and one who I hadn't applied to, but had actually approached me in the first instance. This is a company whose CEO subscribes to a philosophy of Ready, Fire, Aim. I'm of the opinion that, if you can't make a decision after 4 interviews... DO NOT HIRE. It's a sign that something's wrong, maybe just a gut feeling, but something worth listening to. I'd had 7 interviews by now, with 3 more scheduled for the following week.

I began seriously questioning whether I could work for a company with such bureaucratic, non-transparent and slow processes. Was this how things operate internally too? It was hard for me to believe that they could have a hiring process like this and still function acceptably within the rest of the company. But, I have a lot of friends who work for Acquia and they all seem to really enjoy working there.

The recruiter asked for times early the following week, so I again opened up my entire schedule including late night interviews. For anyone who's never done a late night interview, I'll tell you right now that they're extremely challenging. After a full day of work (I've been putting in 10 to 12 hour days), after hanging out, eating dinner, it's time to snap out of it and get ready. Get out of your PJs, put on a nice shirt, and get focussed. It's always important to be on top of your game in any interview. This means being wide awake and involves adrenaline.

 

The interviews themselves are always intense. Almost always enjoyable for me too, since I love chatting with interesting people (and everyone I spoke to at Acquia was interesting). Regardless, if my interview ends at 11pm, I won't be getting to sleep before 2am at the absolute earliest. This means a slow day to follow it up. Of course I had no idea that this would be the case when I first started agreeing to these, and I also thought I'd be looking at 7 days of it, not at least 3 weeks of it (at the end of which I still didn't have any clue as to when it would all end).

Week 4

My meetings for the week were set up, the final one being at 9pm on Friday. The first interview of the week was with Matt again. I'd hoped to get a chance to get clarity on the process, but no dice. I was caught a bit off guard as he grilled me again on things we'd already discussed in our first and second interviews, and that were brought up by the developers I spoke to in week 3. I had another interview immediately after that which was probably my favourite of the bunch but at the end of it all I was left feeling very disheartened with no idea what was going on.

While I was moving forward with the Vancouver company, all of this was still upsetting. I was under the impression when they contacted me that this would take a week, and it had now been dragged out over 4 (with no end in sight). Had I known up front that they required 10-12 interviews I'd have turned them down immediately and saved everybody a lot of time.

Through all this, and despite feeling the way I did, everyone at Acquia seemed very smart and like people I'd have really enjoyed working with. I felt I had a great vibe with Matt and even if this didn't work out, every one of the team would have been a person I'd have enjoyed having a beer with next time I was in Boston.

This is why the response I received the following Monday was so shocking.

Week 5

 

Hi Scott,

Thank you for taking the time to interview with us for our Director, Acquia {DIVISION HIDDEN} opening. Our team has had a chance to discuss your qualifications, and unfortunately, I have decided to pursue other candidates who appear to match (skills and experience) our requirements more closely at this time.

Should something change on our side (or I get another job opening that matches your background better), I will not hesitate to contact you.

Thank you again for your interest in an employment opportunity with Acquia, Inc., and I wish you the best of luck in your current job search.

Thanks,
[Recruiter's Name]

I was in shocked disbelief. Not because I was turned down for the job though: I had in fact received this identical message two months earlier when I applied for an unrelated position at Acquia. They'd looked at my resume and turned me away without any interviews. And now, after:

  • 3 interviews with Matt,
  • a lot of back and forth emails discussing the company and position,
  • a couple of hours spent reviewing and reporting on the project I'd be managing,
  • 4 weeks, and
  • 10 interviews, with
  • 8 people...

... I got a template rejection? And not even from Matt himself, but from the recruiter he delegated it to.

It took a full day of thinking to figure out whether I was upset because I didn't get the job, or because I'd been treated in such a disrespectful way. I'd believed that I'd had a great vibe with Matt, and that the task of sending me my template rejection had been delegated to a recruiter was insulting.

I'll be honest, I was so furious that first day that I considered working for one of their competitors with the sole purpose of taking them down. The next day after I'd got my head back on straight I realized that that would be a strange focus to put on my life for at least the next decade. I spoke to a friend at Acquia and asked if he thought this (the process, not my malicious aspirations) was normal. He couldn't believe my story, and promptly spoke to Matt about what had happened.

I don't think Matt realized I'd be getting a template response, and after learning so from my friend he quickly sent me an apology mail for it. While his mail explicitly said "Either way, no excuses", it was still surprisingly full of excuses (such as being too swamped).

Now, for all I know Matt wanted to send me a long detailed response or call me to explain everything but really was too swamped to. However, considering that he knew I was under pressure with another company and availed myself for what turned out to be a 10-interview gauntlet, a quick 2-liner explaining that I was rejected and setting up a call would have been appreciated.

 

The Moral

I feel that my quote here applies firmly. When you start seeing red flags like a company taking advantage of a person's offer of flexibility (or anything else), unnecessary bureaucracy, and a lack of transparency, it's probably time to call it a day and cut off communication with them (unless you work well in that environment). After the way I felt during the whole process, should I really have been surprised with the way my rejection was handled?

Nobody, whether applying to a position as a CEO or a janitor, should be treated with such discourtesy by the company interviewing them.

 

For Acquia:

Despite dealing more with Matt than anyone else, I certainly don't put the full blame on him. I believe that what happened here is the result of culture and attitude within Acquia.

You have a CEO who contradictorily states that he won't hire anyone with a Ready Aim Fire mentality. Acquia's hiring process is exactly that. Dries (the CTO) says he wants Acquia to do well and good such as acting as a driver to build up and support the Drupal community, yet at the same time the company is treating job candidates (many from within that same community) extraordinarily disrespectfully.

To those at Acquia who are in a position where they can make positive change: it's time you look at your processes and question them. Another friend at Acquia told me that the HR and hiring process is something you're proud of. If you happen to read this post and you're proud of the actions taken, well, I appreciate the rejection.

I'm almost certainly not an isolated case. Much of the Acquia team is made up of loyal members of the Drupal community, and I'd guess that a large percentage of the applicants are community members too (myself included).

Categories: Drupal

Frederick Giasson: Configuring and Using OSF Entities (Screencast)

Drupal Planet - Thu, 2014-04-17 14:29

This screencalcast introduces you to one of the most important OSF for Drupal connector: the OSF Entities module. This module creates a new Entity Type called Resource. The description of these entities is managed directly into the Open Semantic Framework (OSF). All the calls to the core entity API function like: entity_load(), entity_save(), entity_create() and entity_delete() are operated with different calls to different OSF web service endpoints.

What this means for a Drupal developer is that they can use Drupal’s Entity API to manage instance records that are hosted remotely in a OSF instance. They don’t have to know how OSF works in order to take advantage of it. They just have to use the API they are used to use. This new Entity Type supports the following Drupal features:

  1. Full Entity API
  2. Entities caching
  3. Revisioning
  4. SearchAPI
  5. Templates selection with inference on their type
  6. 29 field widgets
  7. Export feature in 6 formats

The screencast introduces you to the following aspects of the OSF Entities module:

  1. Introduction to the architecture of the OSF Entities module
  2. Exposing the available entities in OSF into Drupal Bundles and Fields
  3. Browsing and searching for Resource entities
  4. Managing Resource Type bundles
  5. Introduction to the OSF Entity Reference field widget
  6. Creating and updating Resource entities

 



Categories: Drupal

Amazee Labs: Logfile Handling - Are you visualizing your Logfiles?

Drupal Planet - Thu, 2014-04-17 11:23

We are crazy about graphs and statistics. No wonder we also want to get a feel for the health of our Drupal sites in some way. On our video wall, one screen is dedicated to showing us errors per server to get a better understanding for how good we are doing. You cannot reach zero here, but you see if something fails miserably when things go over 9,000!

We can use our logging information for several things - visualizing error messages is just one use case. As an example, we store the generated data a bit longer to audit some processes, for example, content modification or deletion which is logged by the content module. However, let's jump in!

Architecture

Our setup is currently pretty simple. The so called Elasticsearch ELK Stack (ELK stands for Elasticsearch Logstash Kibana) provides many more possibilities to setup for scalability. For our current size and needs we are happy with the way we set it up. It is straight forward and empowers us to make use of the data that is otherwise stored in the Drupal databases mostly unnoticed.

Drupal - Syslog Module

We make use of the Syslog functionality within Drupal to ship the Syslogs to our Local 7 endpoint of Syslog. From there, the messages are passed to Logstash.

Enabling Syslog is a straightforward thing:

drush en syslog drush vset syslog_identity yoursite_com drush vset syslog_facility 184 drush dis dblog

The remaining settings are left default, but you can change the information that is logged to your needs.

Logstash

Logstash, written by Jordan Sissel, is the Swiss Army knife in our setup. You can think of it as Multiple Input - Multiple Output System. It features many In and Output Types (check the documentation section of the Logstash website for more information). We use the Syslog listener of Logstash and feed this data into our Elasticsearch instance. We create a new index every day to ease the process with retaining the logfiles. The current setup does not need further separation to this, Logstash allows us to split up the messages passed along from Drupal into separate searchable fields. For example, we split the site name, username, module, severity into separated fields.

Elasticsearch

All log entries are passed on from Logstash to Elasticsearch for indexing, search and storage. Elasticsearch is a quite young but powerful tool. It handles sharding and replication over many nodes with ease and has fantastic performance in searching.

Kibana

Kibana is the frontend to Elasticsearch. It allows you to query the data stored within Elasticsearch and displays this information in graphs, diagrams tailored to your needs. We have several graphs we use daily. For example, we show all exceptions thrown on our video wall to see when something goes down. A sudden change in quantity of the errors gives us a hint to look into it. We also go trough the errors after deployments to ensure no fatal exceptions happen and are able to fix things that wouldn't be noticed otherwise.

Want to hear more?

Got curious to see what you can achieve with those tools? I'll is speaking at Campus Berne on 22. April 2014 - You can register yourself on TechUp.

Stay in the loop – join our newsletter!  

 

Categories: Drupal

Phase2: Contemplating the Benefits of Open Source with Metal Toad Media

Drupal Planet - Wed, 2014-04-16 23:27

Last week, I made the journey from Washington, D.C., to our new Portland office, or the “Front End Development Capital of Phase2,” as I like to call it. It was an incredibly enjoyable and productive trip, including everything from hanging out with the awesome West Coast Phase2 crew to discussing our vision for growth in Portland over the coming months and years.

While in Portland, I had the pleasure of sharing some great local beer and stimulating conversation at Metal Toad Media headquarters. During an hour-long podcast that provoked many insightful comments and questions, our host Joaquin Lippincott, Metal Toad’s president, led me, Jacob Redding, and David Bellous through a discussion on the merits of open source vs. closed source technologies.

Joaquin got the ball rolling with the aggressive statement that all closed source technology should be torn down and rebuilt with an open source counterpart. Despite each participant’s shared passion for open source, David was cautious about agreeing to such a sweeping declaration, arguing that with enough time and money it is possible to solve any problem with any technology. He placed greater emphasis on finding the tool best suited to a company’s unique cultural ecosystem and specific technical objectives. My take: I fully agree that each situation requires a creative approach to selecting the right tool for the job, taking into account culture, budget, and goals. In my opinion, there are increasingly less times today when a closed source solution is the right fit.

The discussion turned to the issue of sunk costs and opportunity costs. In the context of what Joaquin deemed the “unmitigated disaster” of Oregon’s online healthcare exchange, which was implemented by Oracle, we debated the increasingly outdated perspective that paying more for software automatically translates to better results. I used Microsoft’s collaborative software SharePoint as an example of a widely purchased product with mediocre if not downright poor customer satisfaction. However, when a massive investment is made (like Oregon’s $132 million in CoverOregon), it is difficult for a government or business to cut its losses and start over, no matter how much additional money it stands to lose in the long run.

Innovation, and the process by which open and closed organizations arrive at it, was another fascinating topic of conversation. Jacob pointed out that while Oracle’s annual investment of $5 million in research and development is easy to grasp, the constant aggregated innovation produced by the open source community is a less tangible concept – but no less meaningful. Most of us acknowledged the merits of a defined road map for innovation, which is usually more visible from proprietary companies, but agreed that collaborative methods of development are being embraced by closed and open source organizations alike. It’s a trend that is really exciting for me personally: more companies are losing their “F.U.D.” (fear, uncertainty, and doubt) about releasing long-kept “secret” code and embracing the clear advantages of open collaboration.

Although Joaquin, Jacob, David, and I covered many other issues, including the advantages of open methodology and the importance of properly executed implementation regardless of the technology, I feel that we’ve only covered the tip of the iceberg in the open vs. closed debate. Altogether it was an extremely enjoyable afternoon (beers included!). Check out the recording at Metal Toad Media, and let me know your thoughts on our discussion. I’d love to hear others weigh in and continue the debate here!

Categories: Drupal

Metal Toad: Toadcast 22

Drupal Planet - Wed, 2014-04-16 22:38



Toadcast 22 hosted an All-Star cast including: Dave Bellous co-owner of Yellow Pencil, Jacob Redding Open Source Manager at Accenture's Emerging Technology Innovation Labs, Jeff Walpole CEO of Phase2, & Joaquin Lippincott President of Metal Toad Media to discuss Open Source, Oracle, and and the healthcare web-tech industry (Cover Oregon).

Categories: Drupal

Drupal.org frontpage posts for the Drupal planet: Drupal 7.27 and 6.31 released

Drupal Planet - Wed, 2014-04-16 21:59

Drupal 7.27 and Drupal 6.31, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.27 and Drupal 6.31 release notes for further information.

Download Drupal 7.27
Download Drupal 6.31

Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features or non-security-related bug fixes in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement. More information on the Drupal 6.x release series can be found in the Drupal 6.0 release announcement.

Security information

We have a security announcement mailing list and a history of all security advisories, as well as an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 and 6 include the built-in Update Status module (renamed to Update Manager in Drupal 7), which informs you about important updates to your modules and themes.

Bug reports

Both Drupal 7.x and 6.x are being maintained, so given enough bug fixes (not just bug reports) more maintenance releases will be made available, according to our monthly release cycle.

Changelog

Drupal 7.27 is a security release only. For more details, see the 7.27 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.31 is a security release only. For more details, see the 6.31 release notes. A complete list of all bug fixes in the stable 6.x branch can be found in the git commit log.

Security vulnerabilities

Drupal 7.27 and 6.31 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

To fix the security problem, please upgrade to either Drupal 7.27 or Drupal 6.31.

Known issues

This security release introduces small API changes which may require code updates on sites that expose Ajax or multi-step forms to anonymous users, and where the forms are displayed on pages that are cached (either by Drupal or by an external system). See the Drupal 7.27 release notes and Drupal 6.31 release notes for more information.

Front page news: Planet DrupalDrupal version: Drupal 6.xDrupal 7.x
Categories: Drupal

Appnovation Technologies: Acquia Cloud Reduces Challenges for Media and Entertainment

Drupal Planet - Wed, 2014-04-16 21:06
Acquia Cloud is a powerful platform for developing and deploying Drupal sites. This post discusses how the Acquia Cloud can reduce website challenges experienced by the Media and Entertainment industries. var switchTo5x = false;stLight.options({"publisher":"dr-75626d0b-d9b4-2fdb-6d29-1a20f61d683"});
Categories: Drupal

AGLOBALWAY: Quick Way To integrate Animate.css in to LESS

Drupal Planet - Wed, 2014-04-16 20:38

Recently I was working in a project, that required some nice predefined css3 animation on different elements. I was wondering if I could achieve it without using javascript and do it fast. Here how I did it:

A quick way to use LESS pre-process and animate.css functionality to make your frontend nice and smoothly animated without any javascript involved.

  1. Download animate.css in to you project/less folder and change file extension to .less
    Your structure should look something like this: project/ ├── less/ │ ├── style.less │ ├── animate.less │ └── overrides.less └── css/ └── style.css
  2. Import animate.less to your main style file. // libraries @import "animate.less"; // core @import "overrides.less";
  3. Edit overrides.less to apply animations on your elements. <h1 class="spetialHeader">Hover Me</h1> h1{ &.spetialHeader{ .animated(); &:hover,&:focus{ .fadeInUp(); } } }
  4. Less preprocess will make the magic and create css file
Tags: Animate.cssdrupal planet
Categories: Drupal

NYC Camp News & Announcements: Holly Ross Becomes 2014th Contributor to Drupal 8 at NYC Camp 2014

Drupal Planet - Wed, 2014-04-16 19:47

Making good on a long stranding promise with webchick, the DA's Holly Ross rolled her first patch, and inadvertently became the 2014th contributor to Drupal 8 at NYC Camp 2014!

NYC Camp 2014 ended with a bang that perfectly *put a bird* on what was a really tremendous 14th event put on by the NYC Drupal community. Sunday was the final day on which everyone is encouraged to come back and sprint on Drupal code or a project they are working on or to get started contributing with help from a Drupal mentor.  Just over 120 attendees came back for Sprints Day, coordinated by  Irene MeiselCathy Theys & Fureigh

And we had a very special attendee who with just such mentoring was able to make her first contribution. On Saturday during their panel discussion at the United Nations with UN CITO Atti Riazi, Drupal 7 co-maintainer Angie "webchick" Byron and Drupal Association executive director Holly Ross reaffirmed their vow that webchick would help her commit her first patch to Drupal 8, and set a date of the next day (the last day of the camp which was given over to NYC Camp sprinting.)

Also on Saturday at NYC Camp, Alina Mackenzie had discovered an issue in the multiligual system documentation, where the language manager interface docblock was returning implementation details (methods should never return implementation details; it belongs to the implementation to do that.)

As Holly was going through the issue queue to pick something to work on, she came across this one, which since it affects the Drupal's Multilingual system was perfect for the United Nations,  which is preparing to become the largest multilingual Drupal deployment in the world.  Alina had a proposed resolution, so with a little mentoring from Cathy Theys, Holly rolled her 1st patch, which passed SimpleTest. 

However SimpleTest couldn't catch another inline comment on the sort method itself which also contained implementation details, that tstoeckler noticed when he was reviewing Holly's patch.  A temporary setback, Holly quickly rolled a 2nd patch, and even included an interdiff. That was enough to satisfy tsoeckler and he marked the new patch RTBC. 

YesCT also added her RTBC (though not before noticing a bug in d.o. node ownership when the node is edited by and admin) and webchick commited the patch at 5:00 pm, and thus at the exact end of NYC Camp.

It was then that everyone noticed an amazing coincidence. Holly had just become the 2014th contributor to Drupal 8. At NYC Camp 2014.

Uncanny. Check out video of the moment on Drupal TV

Stay tuned for more highlights from NYC Camp 2014

Categories: Drupal

Pages