In August 2014, the government of India announced the bold and far-reaching Digital India policy. This ambitious initiative aims to bring about profound digital transformation in all aspects of governance and prepare India and its citizens for a knowledge-driven future.
The three goals of Digital India are:
MidCamp is returning to Chicago, Illinois on March 17th through the 20th, 2016. We will be returning to the University of Illinois at Chicago, this time, on the west side of the campus. MidCamp is looking for people to speak to our Drupal audience! Experienced speakers are always welcome, but our camp is also a great place to start for first-time speakers.
We are expecting more than 300 people at the event this year, all in a wide variety of skill levels and disciplines. We are looking for sessions that are targeted towards beginner through advanced, in 30 minute and hour long formats, that can cover a wide variety of topics in and around Drupal.
Find out more information, please visit:
I am developing a Drupal 8 site right to manage scholarships and scholarship applications at the university. I wanted to add a bunch of custom fields to User and group them with the field_group module, but field_group generated an error that caused White Screen of Death (WSOD) up on adding a field group. I reported the error to the module maintainer, but he seemed to denounce the possibility that it generated an error in his response to me.
This past summer, Sean shed some light on one of our most exciting Drupal contributions to date: RedHen Raiser, our open source peer-to-peer fundraising solution, the first of its kind to be built entirely with Drupal. Thanks to the Capital Area Food Bank of Washington, D.C., we finally had the opportunity to build a platform that would provide fundraisers a highly-customizable, Drupal alternative to SAAS applications like Causevox and Crowdrise.
After a year of leveraging Raiser as their vehicle for crowdfunding, we’re thrilled to see that the Capital Area Food Bank of Washington, D.C. brought in over $324,000, representing tens of thousands of pounds of food, through 17 different campaigns to help fight hunger in their community.
The Food Bank recently shared an infographic with its constituents that breaks down the donations they received through their RedHen Raiser campaigns over this past year.
It’s really exciting for us to think of what other organizations will accomplish with RedHen Raiser. Raiser’s features allow fundraisers to tailor their campaigns to fit a variety of causes. The Food Bank utilized the Teams feature to give local law firms their own fundraising pages during the “Food from the Bar” campaign. There are so many other possible applications: walk-a-thons, food drives, even parties - as the Food Bank has shown us - have the potential to be great fundraising opportunities for your organization, and they can all be easily managed with RedHen Raiser.
We can’t thank the Food Bank enough for working with us to release RedHen Raiser as an open source platform so other members of the Drupal nonprofit community can benefit from it, too – and, of course, make it even better.
Is your organization using RedHen Raiser to crowdfundraise? Get in touch with us. We’d love to hear about your experience and share your story.
In our EK management tools suite we have custom designed lists of items like for instance list of management documents.
Those lists are build with custom codes and templates which is somehow more convenient to manage with complex data, links, menus and filters as in the example below.
However for simple list, the views module is very useful and can be integrated in a custom module as well to automatically create the list.
Here is an example with companies list in the system address book module showing the company name as link and a filed about the type of record plus a simple filter box.
You might have heard of Burning Man. Basically it's a lot of hippies settling down in the desert for a few days, setting up small camps with diffrent themes that make up a big, temporary city.
It's not for me.Radical Self-expression is one of Midburn ten principles. © Eyal Levkovich.
tl;dr: Drupal VM 2.2.0 'Wormhole' was released today, and it adds even more features for local dev!
Over the past few months, I've been working towards a more reliable release cadence for Drupal VM, and I've targeted one or two large features, a number of small improvements, and as many bugfixes as I have time to review. The community surrounding Drupal VM's development has been amazing; in the past few months I've noticed:
- Lunchbox, a new Node.js-based app wrapper for Drupal VM for managing local development environments.
- A mention of using Drupal VM + docker-selenium for running Behat tests with Chrome or FireFox, complete with automatic screenshots of test steps!
- A great discussion about using Drupal VM with teams in the issue queue, along with a PR with some ideas in code.
- A total of 27 individual contributors to Drupal VM (who have helped me work through 307 issues and 77 pull requests), along with hundreds of contributors for the various Ansible roles that support it.
Drupal VM is the fruit of a lot of open-source effort, and one of the things that I'm most proud of is the architecture—whereas many similar projects (whether they use Docker, Vagrant, or locally-installed software) maintain an 'island' of roles/plugins/configuration scripts within one large project, I decided to build Drupal VM on top of a few dozen completely separate Ansible roles, each of which serves an independent need, can be used for a variety of projects outside of Drupal or PHP-land, and is well tested, even in some cases on multiple platforms via Travis CI and Docker.
For example, the Apache and Nginx roles that Drupal VM uses are also used for many individual's and companies' infrastructure, even if they don't even use PHP! I'm happy to see that even some other VM-based Drupal development solutions use some of the roles as a foundation, because by sharing a common foundation, all of our tooling can benefit. It's kind of like Drupal using Twig, which benefits not only our community, but all the other PHP developers who are used to Twig!
If you want to kick the tires on Drupal VM (want to test Drupal 8 with Redis, PHP 7, Nginx, and Maria DB, or easily benchmark Drupal 8 on PHP 7 and HHVM?), follow the Quick Start Guide and let me know how it goes!drupaldrupal vmansibleinfrastructurephpvagrantdrupal planet
In Drupal 7, Views allows you to easily create exposed filters and alter a lot of the logic involved. However, sometimes you get requests to add text to the form or position things in ways that the Views UI does not allow for.
I've got two solutions that are arguably not as Drupal-like as I would like, but I've run into some dead ends on occasion with trying to fullfill requests with only Drupal-like alterations. And of course if there are better ways to do it, I am open to them.
The first method gives you primary control over the exposed form by using hook_form_FORM_ID_alter(). You would think it would be easy to alter the order of form elements in that hook, but it is a little complicated because of the way the form elements can have #weight but that the #info array has the final say over order.
To get around this and make it easy to juggle things around and add items to a form, I created a Drupal Views FormManipulator class.
If you need to do even more advanced juggling of form, header, footer and other views elements I have also resorted to using QueryPath & hook_views_post_render(). It gives you a lot more control, perhaps a bit more fragile if you are not careful to use stable selectors, but it does let you move things that would require lots of different hooks, custom templates AND still leaving you with not quite 100% of what the client is asking for.
When people talk about Mumbai, they often refer to “Bollywood.” But what is Bollywood? It’s a nickname for the most productive movie industry in the world: the Hindi-language film industry! Bollywood employs more people and produces more films than any other cinematic industry in the world, and Bollywood movies are well-loved both within India and beyond.
Happy birthday, Drupal community! Today is the Drupal project's 15th birthday. In honor of the upcoming year, we've put together a retrospective of some of the incredible changes and accomplishments we made together last year.
2015 was a landmark year for Drupal: between three DrupalCons, the release of Drupal 8, and numerous improvements to Drupal.org, there's a lot for everyone to be proud of. None of our amazing accomplishments would been possible without our community of passionate Drupalers. As you read the infographic, we invite you take a moment to congratulate yourself for all the ways that you've helped make the project strong. Because Drupal's 15th birthday isn't just an accomplishment for the software—it's an occasion to celebrate everyone who has helped get the entire project and the community to where they are today.
This is the first time that I am working with automated tests. I have written tests before and and of course I believe that tests improve projects dramatically, but I have never had (/made) the time in a project to actually do it. So I was quite excited to get started with travis.First things first, what do you test!?
I was terribly excited to start working with tests, but yesterday we didn't actually have any code to test against yet, so instead we decided, we actually want to run the drupal core tests. We want our module to be enabled, and to test know if any of our code causes a Drupal core regression, so I started with that.Trial and Error (a lot)...
Travis build history logs showing eventually passing tests.
The documentation is pretty good and there are LOADS of example .travis.yml files floating around, so I started to just get an active environment build working and focused on getting php unit tests working first. I only wanted a couple of tests to run and the main thing I cared about was that drupal installed properly and that the environment was up and running. Eventually I got a passing build with the following .travis.yml
While I was really quite happy with this, I wanted more. Simpletests to say the least, and maybe even behat tests. I found a lot of inspiration when looking at BartFeenstra's (Xano on d.o) Currency module: https://github.com/bartfeenstra/drupal-currency/blob/8.x-3.x/.travis.yml
Most importantly, I found Drupal TI - https://github.com/LionsAd/drupal_ti
This project makes it almost trivial to integrate Drupal Projects with Travis. It handles a lot of the setup in terms of MYSQL, Drupal download and how to start running tests. It managed to reduce my .travis.yml to the following:
This is quite a bit of code, but it is really clean and well commented so we can clearly see what is going on.When to test?
So now there are tests... Great! But when do we run them? Running all of Drupal's tests can take quite some time, but we do want to have a check on development to catch things. So in short we need testing on pull requests between individual development repos (eg https://github.com/yanniboi/decoupledauth) and the main project repo (https://github.com/FreelyGive/decoupledauth) but when we are doing our development we only really care about project specific tests.Seeing tests on GitHub
When I create a pull request now, I automatically have the tests run and the results on the pull request:
GitHub pull request with Travis test results
GitHub pull request test results in Travis CI
Eventually what we really want to do, is have a way of checking inside our .travis.yml, if the test has been started by a pull request, or by a code push/merge and run different parameters depending on that. But more about that next time. There will be a blog post on that soon...
In the meantime, use Travis and write tests :)References:
Lingotek’s Translation Network is a cloud-based solution that connects all your global content in one place, giving you the power to manage your brand worldwide. Our technology pairs with the best-in-class applications, such as Drupal, to continuously push dynamic multilingual content to all of your global markets.
Lingotek’s collaboration with - and development work for - the Drupal community began over four years ago with Drupal 6. Our first Drupal module was released in fall of 2011 for Drupal 6. We now have contributed modules available for both Drupal 7 and Drupal 8.Tags: acquia drupal planet
Creation of rtl css is quite an important process in front-end, necessary to make the design comply with the RTL standards. This process invlolves the substitution of margin-left by margin-right, float: left by float: right… and so on.Read more
On December 29, 2000, I made a code commit that would change my life; it is in this commit that I called my project "Drupal" and added the GPL license to it.
The commit where I dubbed my website project "Drupal" and added the GPL license.
A couple weeks later, on January 15, 2001, exactly 15 years ago from today, I released Drupal 1.0.0 into the world. The early decisions to open-source Drupal and use the GPL license set the cornerstone principles for how our community shares with one another and builds upon each other's achievements to this day.
Drupal is now 15 years old. In internet terms, that is an eternity. In 2001, only 7 percent of the world's population had internet access. The mobile internet had not entered the picture, less than 50% of the people in the United States had a mobile phone, and AT&T had just introduced text messaging. People searched the web with Lycos, Infoseek, AltaVista and Hot Bot. Google -- launched in 1998 as a Stanford University research project -- was still a small, private company just beginning its rise to prominence. Google AdWords, now a $65 billion business, had less than 500 customers when Drupal launched. Chrome, Firefox, and Safari didn't exist yet; most people used Netscape, Opera or Internet Explorer. New ideas for sharing and exchanging content such as "public diaries" and RSS had yet to gain widespread acceptance and Drupal was among the first to support those. Wikipedia was launched on the same day as Drupal and sparked the rise of user-generated content. Facebook and Twitter didn't exist until 4-5 years later. Proprietary software vendors started to feel threathened by open source; most didn't understand how a world-class operating system could coalesce out of part-time hacking by several thousand developers around the world.
Looking back, Drupal has not only survived massive changes in our industry; it has also helped drive them. Over the past decade and a half, I've seen many content management systems emerge and become obsolete: Vignette, Interwoven, PHP-Nuke, and Scoop were all popular at some point in the past but Drupal has outlived them all. A big reason is from the very beginning we have been about constant evolution and reinvention, painful as it is.
Keeping up with the pace of the web is a funny thing. Sometimes you'll look back on choices made years ago and think, "Well, I'm glad that was the right decision!". For example, Drupal introduced "hooks" and "modules" early on, concepts that are commonplace in today's platforms. At some point, you could even find some of my code in WordPress, which Matt Mullenweg started in 2003 with some inspiration from Drupal. Another fortuitous early decision was to focus Drupal on the concept of "nodes" rather than "pages". It wasn't until 10 years later with the rise of mobile that we started to see the web revolve less and less around pages. A node-based approach makes it possible to reuse content in different ways for different devices. In a way, much of the industry is still catching up to that vision. Even though the web is a living, breathing thing, there is a lot of things that we got right.
In the end, I feel fortunate that our community is willing to experiment and break things to stay relevant. Most recently, with the release of Drupal 8, we've made many big changes that will fuel Drupal's continued adoption. I believe we got a lot of things right in Drupal 8 and that we are on the brink of another new and bright era for Drupal.
I've undergone a lot of personal reinvention over the past 15 years too. In the early days, I spent all my time writing code and building Drupal.org. I quickly learned that a successful open source project requires much more than writing code. As Drupal started to grow, I found myself an "accidental leader" and worried about our culture, scaling the project, attracting a strong team of contributors, focusing more and more on Drupal's end-users, growing the commercial ecosystem around Drupal, starting the Drupal Association, and providing vision. Today, I wear a lot of different hats: manager of people and projects, evangelist, fundraiser, sponsor, public speaker, and BDFL. At times, it is difficult and overwhelming, but I would not want it any other way. I want to continue to push Drupal to reach new heights and new goals.
Today we risk losing much of the privacy, serendipity and freedom of the web we know. As the web evolves from a luxury to a basic human right, it's important that we treat it that way. To increase our impact, we have to continue to make Drupal easier to use. I'd love to help build a world where people's privacy is safe and Drupal is more approachable. And as the pace of innovation continues to accelerate, we have to think even more about how to scale the project, remain agile and encourage experimentation. I think about these issues a lot, and am fortunate enough to work with some of the smartest people I know to build the best possible version of the web.
So, here is to another 15 years of evolution, reinvention, and continued growth. No one knows what the web will look like 15 years in the future, but we'll keep doing our best to guide Drupal responsibly.
We at erdfisch are very excited to announce that the Drupal Business and Community Days will take place in Heidelberg, Germany from 8-10 April 2016.
This is part of a series of blog postings explaining what we want to achieve with this event.Business and Community Days - a new format
Firstly, a few words about the format of the Business and Community Days, because the format is slightly different from a usual Drupal camp. Over the years, a standard Drupal camp weekend format has evolved, where on Friday there is a business day, and then the community part takes place on Saturday, and Sunday morning.
For the "Drupal Business and Community Days" we are trying out a different format for the first time, with two separate tracks running parallel:
The Business Days are on Friday, Saturday and Sunday morning - in Heidelberg, this will be an opportunity for the German-speaking Drupal Business Community to get together, and work on strategies for growing Drupal within Germany, Austria and Switzerland. In Germany, Drupal has an amazing developer community, but it is not as well known as a business product as it is in other countries. We need to work on that! (Please note - the Business Days part will take place in German language).
The Community Days are also on Friday, Saturday and Sunday morning. It will be in English, German, and hopefully a few more languages. The community event will have a focus on core, translation, and D8 User Guide sprints. We want to make it as inclusive as we can. If you have not contributed code or documentation to Drupal up to now, or if you are a little rusty, there will be mentors here to help you get started!
The rest of this blog post is about the Community Days.Community Days in Heidelberg
The dream is to have an community event which has a "mini-Dev-Days" feeling, or the kind of feeling that we get on the Friday (Sprint Day) of Drupalcon - where everyone gets the chance to work on a piece of Drupal, making it better. A feeling of everyone being productive together.
I've already mentioned how awesome the community is in this part of the world. I moved to Germany from London three years ago, and I have always had the impression that our developer community here is excellent. What we need to encourage more, is to make the community wider. It can be hard sometimes to find a way to get involved, especially if you are not primarily a developer.Making sprints more accessible
One of my Drupal heroes is Jennifer Hodgdon. My first large-scale Drupal event was Drupalcon London in 2011. I was still quite fresh to Drupal (I had been developing on Microsoft ASP.Net up to that time). I was full of enthusiasm and energy, but short on understanding. I discovered that going to the presentations wasn't so satisfying for me, but that the BoFs (Birds-of-a-feather sessions) were where the action was. I went to a BoF on Documentation and Jennifer said "come to the code sprint on Friday".
At the code sprint, Jennifer single-handedly managed about 40 people, putting us together with each other in small groups so we could help each other make progress. The two people in my little team are still my friends today. We worked on documentation patches and learned a lot together. It seems so strange writing this, but I felt a kind of "high" knowing that my changes would go into Drupal and then be on millions of computers some day. That was the day I felt "committed" to Drupal - I knew that it was a thing I wanted to continue to work with in the future.
At the other Drupalcons I have attended (Munich and Barcelona) the Friday was always the highlight. On that day, you meet great people. In 2014 I went to the Dev Days in Szeged, and it was the same feeling but for a whole week!
So that's what we are aiming for with the Community part of DBCD16. Let's see how well we can achieve it. We are helped by the fact that the location is so good - we have accommodation and food on-site. Heidelberg Youth Hostel was the location for DebConf15 and the Debian people loved it.Drupal 8 User Guide Sprints
If I'm honest, you will not likely find me in the "hard" sprints. Over the past few months, I have been contributing in my free time to the Drupal 8 User Guide project, which is being led by Jennifer Hodgdon and Joe Shindelar. The aim is to have an open-source, version-controlled guide for Drupal site-builders. Once the English-language guide is ready, every language community can start translating it into their own language. So we will end up with a user guide for site-builders all over the world!
Every contribution to the guide gets a full commit credit and helps your company's ranking on its drupal.org page (you can see my very, very modest efforts here).Featured community participants
My partner-in-crime for the Community Days is my awesome erdfisch colleague Tobias Stöckler (tstoeckler). Tobias is closely involved with core, so will have more to say about the core code sprints in Heidelberg!
Tobias and I were kindly allocated a budget to invite some community members to join us. These are people who have done a lot for the Drupal community in Europe. So I'm pleased to say these people will be joining us too: zsofi.major, emma.maria and ckrina.
Hope to see you there, too! Get your tickets before the end of January so that you can take advantage of the early bird pricing.
We're looking forward to welcoming you to Heidelberg in April!Schlagworte/Tags: planet heidelberg DrupalBCDays Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank
It is possible to allow Views to show only content that has child terms from a taxonomy?
Yes, it is. This is similar but slightly different to our tutorial on using Views to show only child terms.
One OSTraining member asked us this question:How can I set the filter criteria so that Views shows only the second level in of a taxonomy?
We've had that question from other members before, so here's a tutorial explaining how it's done.
First, you need a taxonomy that has parent and child terms, as in this example: