Planet Drupal

Subscribe to Planet Drupal feed - aggregated feeds in category Planet Drupal
Updated: 9 hours 36 min ago

Drupal core announcements: Media in Drupal 8 Initiative plan posted for review

21 September 2016 - 8:54am

As we are ramping up to work on significant user improvements for Drupal 8.3, one of the key areas of progress could be with media management user interfaces and features. For that to happen, we need to agree on what we are going to work on and then have people to implement it. The Media in Drupal 8 Initiative plan is being formed and is open for feedback now if having better core media support is near and dear to your heart. Please review and post feedback on the plan.

If you'd like to get involved with the implementation, you are more than welcome! The media team meets every Wednesday at 2pm GMT on IRC in #drupal-media.

Categories: Drupal

Annertech: Things I Learned from the DrupalTwig Slack: Volume 1

21 September 2016 - 7:38am
Things I Learned from the DrupalTwig Slack: Volume 1

Without doubt, the greatest resource for information about Drupal frontend issues is the DrupalTwig Slack. There are over 300 of the world's most well known frontend Drupal developers - Wim Leers, MortenDK, Mark Drummond, David Hernandez, and more - offering and receiving help all day every day. It's very rare that someone asks a question and doesn't receive a reply with a solution within a few minutes, or at the very least a conversation about why the issue might be hard to solve.

Categories: Drupal

Kodamera Screencast: Embedding videos easily with Video Filter

21 September 2016 - 7:29am

Embedding videos can be a tricky thing to do when it comes to both the web and different CMS's. When it comes to embedding videos in the content section - the body of the page - The Video Filter module offers an easy and great solution. 

Basically, you install the module, configure it for the different text formats you want to use it with and then simply add the videos in the body text with a kind of shortcode or shorthand thingamajig.

In this video I'll go through what you need to know and how to get the videos to show in your content.

The Video Filter module only works as a text filter, so if you're looking for a solution where you can create embedded videos from a field of its own in Drupal, perhaps Video Embed Field could offer such a solution. (I'm just talking about Video Filter in this screencast.)

Read more
Categories: Drupal

Drupalize.Me: Drupalize.Me Now Powered by Pantheon

21 September 2016 - 6:37am

If you're following along at home, you may have seen that we recently made the move to Pantheon hosting. Last week during our maintenance window, Joe and I worked through our migration checklist, and officially moved the site over to our new host. The process had a few hiccups, but we thought it would be interesting to take a look at what went into our migration process. Hopefully sharing what went into our planning process, as well as what is in our pipeline for improvements now that we're on Pantheon, will help you if you ever find yourself facing a similar project.

Categories: Drupal

Unimity Solutions Drupal Blog: How Attending DrupalCon Dublin Could Benefit You?

21 September 2016 - 5:05am

DrupalCon Dublin is just a week away!! With all the excitement surrounding the event we often forget to look at key things to expect out of this event. What should one learn out of DrupalCon Dublin? Is it only for Drupal developers or should CEOs, Managers and owners attend? What’s the use of attending an event on OPEN SOURCE TECHNOLOGY? Is it useful for growth of businesses as well?

Categories: Drupal

Drupal Console: Make contrib modules with DrupalConsole commands compatible with RC-1

21 September 2016 - 2:35am

DrupalConsole RC-1 is close, is really really close, as close as DrupalCon Dublin, less than a week at least thats our goal.

Where are we?

We accomplish a lot of changes during the last two months, and this is an overview of the milestones completed for RC-1 release.

* Languages separated from the main project.

* Core commands and features to be shared across projects.

* Main repo.

* New global executable.

What is next?

The next step is to fix modules with current DrupalConsole integrations once RC-1 is released, this means next week during DrupalCon.

This is the list of the known contributed commands providing commands, we have identified and we are planning to help update and fix to be RC-1 compatible.

  • Metatag
  • Webprofiler
  • Drupal Commerce
  • Configuration Split
  • Scheduled Updates

If you know of another module(s) with contributes command please let us know by commenting on this post or on this issue

Are we done and ready for the stable ?

Not yet, we are close and we will continue working to complete the stable release and you help us complete it. This is how you can help.

Are you a business owner?

As a business owner has your company already leveraged the advantages of Drupal Console?. Will Drupal Console play a significant role in your business plan for  your immersion in Drupal 8?

You can contribute to complete the Goals for our 1.0.0 stable release by assigning 1 or more of your resources to work in office hours to complete the pending tasks.

Are you an independent developer?

As an independent developer, you can help us by allocating some hours. We always have issues to resolve and none of them are rocket science!

Are you going to DrupalCon?

    Feel free to join us during the sprints, you can help us in several ways:

    • Fix current modules with integrations.
    • Fix bugs and improve the project.
    • Write an integration for a contrib module.
    • If you know how to write test for Drupal 8, we really need your help.

    Do not miss the DrupalConsole sessions Enzo and I will be presenting

    Do not miss the Community Keynote enzo will be presenting

    Categories: Drupal

    Deeson: White men in digital - our privilege is blinding

    21 September 2016 - 12:26am

    We’re proudly sponsoring the Women in Drupal event at DrupalCon Dublin 2016. This prompted me to reflect on our own track record on employing and advancing women.

    Of course our own house is in order. Right?

    No, it is not.

    Including our current hiring round, in our team of 40 people:

    • 0% of our four most senior posts are held by women
    • 10% of our full leadership team is made up of women
    • 20% of our developers are women
    • 30% of our overall team are women

    I would describe our approach to creating a representative, safe and welcoming workplace that facilitates everyone being able to thrive as ‘well intentioned’.

    No one in the team has raised any concerns about our approach.

    I also haven’t spent much time ensuring that we understand how to address these complex issues. Or that we’re serious about rooting out the more insidious aspects of discrimination.

    So - passive, ill-informed and well intentioned.


    On further reading I realised a little more how my personal privilege contributes to my blindness on this subject.

    I’m a white male, in an industry dominated by white men and I’m the most senior person in the organisation. An organisation where the four most senior roles are held by white men.

    In what scenario would a feeling of being ‘other’ likely occur for me? Let alone the reality that I have personally experienced discrimination?

    So it’s impossible that it’s only women that we’re failing

    By failing to engage with and acknowledge our bias, we’re not actively including all people across differences in sex, age, gender, race, sexual orientation or disability. I’m pretty sure therefore our recruitment process needs deeper thought.

    Organisationally we’re likely to reveal our implicit bias through our lack of representation of some communities at a senior level - test yours here.

    And the likelihood of that being a perpetuating factor for our failure to represent the wider community within the organisation seems high.

    A lack of awareness of this bias is also likely to hurt our work - our UX, design and development practices all require empathy and different perspectives to deliver results.

    And that means we’re not proactively developing a culture that ensures that everyone knows they’re welcome, that they will be respected as themselves, that they can thrive and belong here. How will they answer the question ‘Can someone like me be successful here?’

    For example, our lack of diversity at a senior level means that we don’t interpret the signals the way that some people might about our recruitment proposition.

    Harmful consequences

    Aside from the fact this feels ethically wrong as a state of affairs, this every day passivity is harmful in terms of the following:

    • Our ability to have a truly diverse workplace where everyone feels welcome
    • Our ability to attract the widest range of potential candidates
    • Our ability to progress people to a senior level
    • Our performance as a company

    Let’s start closer to home than the pipeline issue

    The industry approach has been on occasion less than insightful: ‘if they don’t apply for our jobs, then we can’t hire them, so what can we do?’.

    It’s a pipeline problem that’s not our fault, right?

    This ignores the appalling discrimination that people have experienced in the industry. Which, for example, contributes to a shameful retention rate of women who have chosen tech as a career.

    And if you can’t see people like you succeeding in the industry how attractive (or safe) would it feel as a career choice?

    Of course it’s important and positive that the industry backs initiatives that help support poorly represented communities. But we shouldn’t ignore the inconvenient and more directly addressable truths closer to home.

    Do we really need to hear what another white man thinks about equal representation in tech?

    On the one hand, no. The tech industry is disproportionately full of our opinions on this topic already. But, as others have pointed out, under-represented communities can't fix this on their own - those in positions of power need to make a stand alongside them.

    The target audience for this post is really other people in positions of privilege and power who, like me, somehow hadn’t woken up to the fact that being passive and ill-educated on this issue perpetuates it. That it may be painful and uncomfortable to acknowledge that you may have passively perpetuated discrimination within your organisation. That you might need to challenge your thinking.

    Before you decide this is an issue you feel comfortable ignoring - reflect a while or maybe digest some more people’s experiences in the industry.

    If you disagree with a specific point is it OK to just disengage? Or could you take positive steps on the areas that do resonate?

    How are Deeson going to do better?

    I’m going to make it a standing issue on our leadership team’s agenda so that we can monitor progress and maintain an active discussion. We aren’t going to get better overnight.

    We’re going to immediately:

    • Begin annual salary audits to check for bias and rectify imbalances
    • Report on our progress when we do our quarterly planning
    • Implicit bias training for everyone
    • Stop attending conferences that don’t have a credible Code of Conduct
    • During hiring, take a more nuanced view on whether a developer has made open source contributions
    • Stop participating in all male conference panels
    • Improve our Careers page, including clarity on parental leave
    • Stop asking for previous salary during hiring - it can perpetuate pay inequality
    • Create dialogue and feedback channels within the company to offer better support
    • Stay informed and signpost groups working in the industry

    Can digital agencies and the Drupal community do better?

    I think they can. I've worked in the UK's digital agency sector since 2001 and I've been involved with the Drupal community since 2007. The impression I get is that inequality is a problem across the board.

    The Drupal community is at least doing its best to redress imbalances - there are initiatives that support poorly represented communities in STEM subjects through coding clubs, ambassadors and advocacy, for example. But is it enough, and is it working?

    Digital agencies, perhaps because they're less in the public eye, are lagging behind in terms of these initiatives. As we've seen, CEOs, CTOs and founders are largely oblivious to their own white male privilege, and this needs to change.

    So, how should this change come about, and what is your organisation doing to increase diversity?

    I'd love to hear your opinions on this, whether you work in digital or you're a member of the Drupal community. Leave a comment below this piece, or tweet me at @timdeeson

    Background and research

    I couldn’t have written this post without the material I have referenced and for the wider reading that made me realise the extent of the issue. The material they have written has been written for no personal gain by people who have had negative personal experiences of the tech industry. They bear the disproportionate burden of both suffering the consequences of these issues and making significant efforts to improve the situation for others.

    Thank you to Lisa Armstrong, our acting Marketing Director, for her support with the post and for our conversations that prompted me to realise that not everyone has the luxury of my ignorance. Her current experience as a startup founder in the fintech field has not always been positive.

    Also, in order to develop something more likely to be helpful rather than harmful I approached Meri Williams. I took part in a training workshop she gave a few years ago, the depth of her expertise on managing people at work taught me lessons that I use every day. She turned down paid consultancy but generously offered to discuss writing this post with me pro-bono. What’s useful in this post is likely to be there through her leadership and the writing of others that I’ve mentioned. She has another workshop coming up soon.

    And thank you to the team at Deeson for their thoughts and input.

    Categories: Drupal

    LevelTen Interactive: Drupal Tutorial: How to Sort Search Results by Content Type

    20 September 2016 - 10:00pm

    For a recent website I worked on, the client wanted search results to be grouped by content type, and also wanted to control which content type results were displayed first, second, and third. While you can get most of the way there in terms of sorting search results using Views, if the desired order of the content types doesn't luckily correspond to some kind of alphabetical sorting of the content type's names, you'll need to do a little configuration and custom module work to make this happen. 

    I will walk you through how to do this using a vanilla...Read more

    Categories: Drupal

    Drupal core announcements: Core topic discussions at DrupalCon Dublin

    20 September 2016 - 6:27pm

    DrupalCon Dublin includes a full track of core conversations where you can learn about current topics in Drupal core development, and a week of sprints where you can participate in shaping Drupal's future.

    In addition to the core conversations, we have a few meetings on specific topics for future core development. These meetings will be very focused, so contact the listed organizer for each if you are interested in participating.

    Time Topic Organizer Monday Sept. 26, 14:00 Views major triage xjm Monday Sept. 26, 15:30 PHPUnit and BrowserTestBase initiative xjm Tuesday Sept. 27, 13:00 Media Initiative slashrsm Tuesday Sept. 27, 14:30 Entity Field API major triage xjm Wednesday Sept. 28, 9:00 Contact Storage initiative tedbow Wednesday Sept. 28, 10:30 Core JavaScript maintenance nod_ Wednesday Sept. 28, 12:00 Data Modeling UIs tedbow Wednesday Sept. 28, 14:00 Ideation in Agile core process gaborhojtsy Wednesday Sept. 28, 16:00 Theme component library lauriii Thursday Sept. 29, 15:30 Default content in core tkoleary Thursday Sept. 29, 15:30 New default core theme lauriii Thursday Sept. 29, 16:40 Workflow Initiative dixon_ Friday Sept. 30, 13:00 API-first and REST Initiative prestonso

    Also be sure to watch Dries' keynote for ideas about Drupal's future!

    Categories: Drupal

    Palantir: The Secret Sauce, Ep. 32: Documentation and Training

    20 September 2016 - 11:55am
    The Secret Sauce, Ep. 32: Documentation and Training The Secret Sauce brandt Tue, 09/20/2016 - 13:55 Ryan Price with Allison Manley Sep 20, 2016

    We want to make your project a success.

    Let's Chat.

    There are many benefits to documenting your project and teaching someone else how to use it.

    Senior Engineer Ryan Price dives into the importance of documentation in this week’s episode of the Secret Sauce. 

    iTunes | RSS Feed | Download| Transcript

    Stay connected with the latest news on web strategy, design, and development.

    Sign up for our newsletter. Transcript

    Allison Manley [AM]: Hello and welcome to The Secret Sauce, a short podcast by, that offers a little bit of advice to help your business run better. I’m Allison Manley, an Account Manager, and today we have Senior Engineer Ryan Price talking about the importance of documentation and training.  

    Ryan Price [RP]: My name is Ryan Price, and I want to talk a little bit today about documentation and training. Probably the key person that I think about when I get into the role of writing documentation for a project is future me. Who is the person that will be reading this later, and who is the person that’s going to get the most benefit out of it? Then I sort of go from there, because the more people that get involved with the project — whether it’s someone on the client side, whether they’re technical or non-technical, whether it’s other members of the development team, or maybe my project manager — all of those people are going to read or edit or touch the documentation of a project at some point.

    And on a lot of projects I’ve worked on in the past, I have been in the role of training the new people who are going to be using that project, whether it’s other developers or the content editor who’s working on the client side. And all of those people need to know what this website is supposed to be doing. Beyond just the business goals, there’s lots of nuts and bolts things, and in the land of Drupal we have lots of nuts and bolts things. And for some people those things are totally new, and they have fun new words like ‘nodes’ and ‘taxonomy’ and ‘views.’ And for other people, they know those things, but they haven’t seen this way for placing blocks in this context, whatever that happens to be.

    So I think even a simple project that is just a brochure site would still have documentation that needs to be written for future me. When I come back to this project, I don’t want to spend five hours remembering my motivation behind making a new field for this. It should just be there. What does this field do and why do we have it? You want to get this stuff out of your head. If you get hit by a bus, you don’t want to be the person on the project who made something that was indecipherable and everyone needs to sit around and figure it out.

    And the other thing is, when you explain something, you learn it. There’s doing it and being able to do it yourself, versus having to write it down. For me, translating something out of my head into speaking is when I really understand what it is that I’m doing, or writing it down at the same time. And you can also discover things about the project, too. Like discovering when a requirement is unclear, or when a piece of work is not quite polished. Because you’re getting ready to document it, and you say, it’s supposed to do these nine things and it does eight of them really well.

    So there are lots and lots of benefits to documenting your project and teaching someone else how to use it, and I think probably the key person among those is future me. Thank you for listening!

    AM: Thanks Ryan. That’s the end of this week’s Secret Sauce. For more great tips, please check out our website at You can also follow us on twitter at @palantir. Have a great day!

    Categories: Drupal

    BlackMesh: Best of New Orleans DrupalCon Core Conversations

    20 September 2016 - 7:46am

    DrupalCon New Orleans had many good Core Conversations. The Core Conversation track sessions are a bit different than regular session. Presenters frame a topic, discussion, or concern. And then, the conversation with the audience continues in the session recordings.

    I was the local track chair and I listened to all of the convos. Here are some choice quotes. Enjoy the highlights from New Orleans, and I'll see you in Dublin!

    Quotes from the sessions Automated javascript testing: where we are and what we actually want by dawehner

    "we should go with Mocha and Karma" @dawehner in Core Convo: Automated javascript testing @drupalconNA #drupalcon

    Approaches for UX changes big and small by yoroy

    "We've done multiple usability tests on [#Drupal] core. The results have become predictable” @royscholten #DrupalCon

    MVP should provide value for end users right from the start. @royscholten #DrupalCon

    Is size just a number?: Reflecting on community growth, mentoring, and where we spend our efforts by David Hernandez

    "Focus on the human element" from @davidnarrabilis about #Drupal Community growth #DrupalCon

    Just Right: Goldilocks and CMS theme systems by lauriii and Cottser

    Personas the theme system has to deal, are base for complexity we have @laurii1 #DrupalCon

    "Because we can do things :)" @Cottser #DrupalCon

    The potential in Drupal 8.x and how to realize it by Gábor Hojtsy and webchick

    "You can make big changes in Drupal 8" @gaborhojtsy #DrupalCon

    "Things that we want to do to the process to improve" @webchick #DrupalCon

    About Core MVP process proposal, @dickolsson: "Can we get an MVP of this" // @webchick @gaborhojtsy #DrupalCon

    The future of Drupal Performance - Parallel worlds by Fabianx

    Ha @drupalconNA "Welcome to our cooking 101 class!" @fabianfranz in The future of Drupal Performance #DrupalCon

    "Avoid doing unnecessary work" @fabianfranz in The future of Drupal Performance #DrupalCon

    Recruiting and retaining dedicated volunteers by stephelhajj

    Professional & funny: Recruiting and retaining dedicated volunteers @stephelhajj #DrupalCon

    Prune your garden @stephelhajj #DrupalCon

    Together we can make Drupal The Example for Diversity in Tech! by drnikki and techgirlgeek

    Diversity, Equality, Inclusion, Marginalized Group @TechGirlGeek #DrupalCon

    Things that make you a: good developer, no. tech worker. no: human being @drnikki #DrupalCon

    Unbias Me Chrome extension from @fureigh via @drnikki #DrupalCon

    #DrupalCon audience adds @lexiconvalley E78 Diversity resource // @TechGirlGeek @drnikki

    Learning to Let Go (Contrib Burnout) and Module Giveaway by Dave Reid

    "Be human" from @lullabot via @davereid #DrupalCon

    How to do contrib: compartmentalize, therapy, afk time, todo list via @davereid #DrupalCon

    Drupal (admin) as an application: More JavaScript in core? by prestonso , danigrrl , and mdrummond

    At #MidCamp "consensus about what features we want in Core for JavaScript" @prestonso @MarcDrummond #DrupalCon

    Workflow Initiative (Drupal is a CMS) by timmillwood and dixon_

    Check the Workflow Initiative Plan for updates #DrupalCon core convo from @timmillwood @dickolsson

    Leaving Drupal by eatings

    "One cant be a master without an apprentice" @eatings Leaving Drupal #DrupalCon core convo

    State of Drupal by Dries, xjm, and Gábor Hojtsy

    To help remove contribution barriers @Dries in State of #Drupal #DrupalCon core convo

    How to find issues that are good for new contributors from @gaborhojtsy at @Dries State of #Drupal #DrupalCon convo

    D.o, github, issue workspaces background via @xjmdrupal @joshua_io at @Dries State of #Drupal #DrupalCon convo Don't say just. It does a great disservice to the complexity of the system @joshua_io at State of #Drupal #DrupalCon

    Lessons from WordPress Core by stevector and andrew.taylor

    "We have a twin island [..] right next to us, that has all the same pressures we do.” @stevector #DrupalCon

    DrupalDrupalCon New Orleans
    Categories: Drupal

    InternetDevels: Drupal 8 Module: Rules

    20 September 2016 - 7:39am

    Rules are everywhere: at school, at work, in life in general ... and there are some Rules in Drupal 8
    as well!
    Although it’s definitely not what you think it is :)

    Read more
    Categories: Drupal

    Zivtech: What are Hooks?

    20 September 2016 - 6:32am
    As a junior developer ramping up to learning Drupal, I spent a lot of time clicking through the UI. After getting familiar with it, I wanted to take a look behind the scenes at Drupal’s codebase. Writing code for a Drupal site can be an overwhelming experience because, even though it’s written in PHP, there’s a dense API behind it. One of the biggest parts of that API is the hook system. The first exposure I had to writing PHP with Drupal was through update hooks. So I wanted to review how hooks work, and how cool they are to use! What is a Hook? Drupal has a lot of excellent Community Documentation, and their page on hooks is thorough. It says:

    “Hooks are how modules can interact with the core code of Drupal. They make it possible for a module to define new urls and pages within the site (hook_menu), to add content to pages (hook_block, hook_footer, etc.), to set up custom database tables (hook_schema), and more.

    Hooks occur at various points in the thread of execution, where Drupal seeks contributions from all the enabled modules. For example, when a user visits a help page on a Drupal site, as Drupal builds the help page it will give each module a chance to contribute documentation about itself. It does this by scanning all the module code for functions that have the name mymodule_help($path, $arg), where "mymodule" is the module's name, e.g., the block module's help hook is called block_help and the node module's help hook is called node_help. The hook may provide parameters; hook_help's parameters $path and $arg allow the developer to determine what page or pages the help messages will appear on.
    A hook can be thought of as an event listener in the sense that an event triggers an action.”

    It’s amazing that Drupal is built on this hook system. There are hooks for anything you can think of! You can even alter a form or a whole page. As Drupal builds each page, it’s scanning the module code for the hooks in core and then runs the ones that you wrote. Alan Storm put it succinctly in one of his blog posts:

    “When a hook is invoked, Drupal will

    1. Get a list of all installed and enabled modules
    2. Ask each module “Have you implemented the do_something hook”?
    3. If so, then Drupal calls the function in those modules that implement the hook

    This way, as a core developer, you can achieve what you want while still letting other programmers “hook into” what you’re doing.”

    Update Hooks The first hook I used was an update hook. The purpose of an update hook is to run code when a database update is triggered. (See the Drupal documentation for function hook_update_N for more information). I’m assuming my reader has worked with Features development (if not, go here).

    My goal was to enable a certain contributed module programmatically when I deployed my code to the site (the Olark module). To do this, I had to find an existing feature in my project that was already enabled. A good rule of thumb is to add your code to an existing feature that is related to the code you’re writing. Since Olark is a chat module, I was looking for a feature related to customers or the homepage. I couldn’t find any feature that fit exactly with the module, so I added my code to feature_general. Within the directory of that feature, I found the feature_general.install file, and added my hook:
    /** * Enables 'olark' module. */ function feature_general_update_7006() { module_enable(array('olark')); }
    After I deploy my code, I trigger a database update. Think back to the three steps that Alan Storm mentioned. Since my feature is already enabled, when the update is triggered, Drupal asks if any update hooks have been invoked. When it sees that there is one in my feature, it knows to read the code in the install file and turn on the Olark module.

    It’s also worth noting the naming convention. I have to put the name of my feature and then _update. The number of the hook also matters (see documentation for specifics on how to number your hooks). The hooks only run once, so each hook has to be one greater than the one before.

    Writing hooks is a great way for a junior developer to be introduced to PHP in Drupal and learn about how Drupal is built. Once you can conceptualize the inner workings of Drupal, it’s much easier to tackle things like module development in the future.
    Categories: Drupal Giving Clients What They Need - Not What They Want

    20 September 2016 - 5:38am

    If you're anything like me, you've spent a few years in the freelance/agency world performing work for clients. If your clients are anything like the ones I've had, they come in with preconceived notions, "wives tales", and many, many things that are just not in their best interest.

    I know there is a tendency to say "the customer is always right." I would prefer to say "the customer is entitled to the best product possible."

    Part of that product is you - their developer - and your knowledge.

    In this post, I'm going to attempt to show you a piece of what I mean when I say "Giving Clients What They Need - Not What They Want".

    Categories: Drupal

    Annertech: DrupalCon Welcome Party: It'll be Deadly and Savage (with translations)

    20 September 2016 - 3:22am
    DrupalCon Welcome Party: It'll be Deadly and Savage (with translations)

    This day next week, as part of the Drupal Ireland Association, we will be delighted to welcome you to Dublin at the DrupalCon Welcome Party. It's on a boat, which is going to be deadly ("deadly" in this context means great, "lethal" would mean dodgy/dangerous!). The boat is just across the road from the convention centre, so that will be savage ("savage" of course means lots of fun).

    Categories: Drupal

    Aurelien Navarre: Porting the Page Load Progress module to Drupal 8

    20 September 2016 - 1:08am

    Back in 2012, my colleague Mariano released the Page Load Progress module for Drupal 7. This is not a widely popular module but I love it. Simply put, it will display a spinner when a page is taking too long to load, to prevent your users from clicking around or leave the page. It excels for time-consuming form submissions.

    The path to being a co-maintainer

    In mid-2014, I wanted to start learning Drupal 8 so I figured porting the Page Load Progress module to D8 would be twofold: 1/ do something meaningful to make the module live during the Drupal 8 lifecycle 2/ get to learn about the Drupal 8 API changes.

    I quickly filed an issue in the Page Load Progress issue queue to get community feedback as I was 80% through porting the module. For about 2 years I never heard back, so at some point I realized the module was no longer being maintained and a critical Views issue on Drupal 7 (and by extension Drupal 8) was most likely preventing the module from getting wider adoption.

    I reached out to Mariano and he said he was no longer doing Drupal development and was happy for me to take over the module. Ha! Didn't think about being a module maintainer. I'm not even a developer. That being said I liked the idea that Open source is all about passing on the torch and I had to do my part until I'd pass it on to someone else.

    So, I followed the Dealing with unsupported (abandoned) projects guidelines and filed an issue to take over maintaining the Page Load Progress module. The next steps were for me to get community awareness and help with this new challenge. I thus filed a Drupal 8 Contrib Porting Tracker issue and reached out to Dom. to make him a co-maintainer and mentor on the project, since he has extensive experience with Drupal 8.

    Taking it from there

    During the summer, we then worked on completing the port of the module and brainstormed on where to bring it next. The main highlights are:

    Usage statistics show people are starting using it again, which likely means we did have a blocker with this annoying Views issue.

    Next we want to work on implementing JavaScriptTestBase and also allow users to exclude arbitrary paths from triggering the throbber.

    Conceptually, the Page Load Progress is a very simple module. But when you think about it, you can considerably improve its inner workings, support edge-cases better and have full JS test coverage to make it rock solid. We're on it. See you in the issue queue!

    Categories: Drupal

    Cocomore: We Got It: The Drupal 8 Developer Certificate

    19 September 2016 - 3:00pm

    For software developers it is very important to continue their education continuously. That’s why our Drupal programmers in Seville didn’t hesitate and participate as some of the first ones in the Drupal 8 Certification Program of Acquia. With success! For everyone thinking about also getting certified for the latest version of the CMS we have some useful tips.

    Categories: Drupal

    Palantir: Noble Network of Charter Schools

    19 September 2016 - 2:38pm
    Noble Network of Charter Schools brandt Mon, 09/19/2016 - 16:38 Supporting Students For a More Promising Future

    Support for a better managed codebase across a platform of Drupal sites.

    • Provided valuable insight into state of the site with an in-depth code audit

    • Transitioned seamlessly from previous hosting platform to Acquia

    • Streamlined theme to reduce code duplication

    Do you need a site audit?

    Let's Chat.

    Noble Network of Charter Schools (Noble) is a Chicago-based nonprofit organization that manages a network of 16 public high schools and one middle school located throughout Chicago. The schools of the Noble Network serve over 10,000 mainly low-income, underserved students, and work toward making a college degree a reality for each of them. 

    Noble needed a firm with a deep bench of Drupal talent to optimize its current sites and maintain and extend the underlying platform as Noble improved and advanced its online presence. Noble’s previous support provider no longer had the Drupal staff to support their needs, and they also needed assistance in transitioning their sites to a new hosting platform.

    As we do with all of our support clients, we began with an in-depth code audit that allowed Noble to see the state of their sites behind the scenes. This audit provided details on what we could implement to increase the stability and speed of the Noble sites. One of the most significant updates we made was to streamline the theme to reduce code duplication. The existing code base did not leverage Drupal’s theme inheritance properly.

    Across the sites in the network, about 95% of the CSS is identical. Only colors and log images are changed. However, when the site was initially built by another firm, the code and CSS for each site was duplicated, which meant that if a change was made in one place, it needed to be changed in 17 different places. Using a base theme properly, our developers updated the codebase so that if something is fixed on the core level, then it is fixed on all of the sites. 

    In addition, we implemented bonus features like a homepage slideshow, form and calendar integrations, and modified Google Translate functionality. The form and calendar integrations allows Noble students and families to more efficiently see upcoming events at their campuses and provides a quick way to contact the school by email with general questions and comments. The Google Translate functionality is very important, as many students’ families speak Spanish at home. Noble sends all official documents home with Spanish translations, and it was important that the website be just as accessible.

    Working with Acquia, we helped Noble transition to a new hosting provider that provides Drupal support for the network. Because we jumped right in with a great project manager and the right resources to get started, Noble’s sites experienced no downtime which mitigated any negative user experience. Moving to Acquia gave us better tools for managing code and deployments across the sites, and as our partnership continues and more features are added, the result is a better managed and overall more reliable platform of sites.  

    "Going with Palantir to support your Drupal website is a no brainer." Donnell P. Layne, Director of Information Technology

    We want to make your project a success.

    Let's Chat. Drupal Services Support Project Management How to Gauge Your Support Needs We've Got Your Back: Palantir's Support Services The Secret Sauce, Ep. 25: What Can Support Do for You?
    Categories: Drupal

    Drupal Aid: Enhancing CKEditor in Drupal 8

    19 September 2016 - 12:00pm

    It was a happy day for me when CKeditor was incorporated into Drupal 8 core. Out of the box, Ckeditor is great. But there a lot of things you can do to make it better and more user friendly for your clients. In this post, I’ll show you some easy additions you can make to enhance your end-user's content editing experience.

    • How to easily make Links to other content
    • How to easily add Files and Images (and manage them too)
    • Adding Custom Styles
    • Adding Templates
    • Other helpful CKEditor Add-ons that are available.

    Read more

    Categories: Drupal

    Acquia Developer Center Blog: Personalization Happens - Acquia at dmexco 2016

    19 September 2016 - 9:12am

    Conversations about delivering business needs with digital tools, or "How to get Drupal into the conversation without talking technology."

    Acquia and several partners had a successful presence at the 2016 dmexco trade show for digital marketing and advertising. By "successful," I mean we spoke with hundreds and hundreds of people about how we can help them do better business and I think many of them will end up being happy users, consumers, and contributors to Drupal and our community.

    In this podcast (audio and video), I give a quick intro to the dmexco trade fair and speak with the following people about digital transformation, selling Drupal without selling Drupal, the state of Drupal in Germany in 2016, and more:

    Bonus! Acquia made it into the official dmexco wrap-up video. Great to see us representing Drupal alongside so many big names.

    Bonus 2! Check out my Buzzword Bingo video from the dmexco floor to get a feel for the magnitude of the show and its ecosystem and the sometimes confusing world of contextual cloud targeting, media data reach optimisation, customer brand implementation, storytelling growth and even more that I didn't make up!

    Skill Level: BeginnerIntermediateAdvanced
    Categories: Drupal