It is not true that in order to live one has to believe in one's own existence. There is no necessity to that.
Drupal 7.35 and Drupal 6.35, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.35 and Drupal 6.35 release notes for further information.Download Drupal 7.35
Download Drupal 6.35
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
Drupal 7.35 and 6.35 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.35 or Drupal 6.35.Update notes Planet DrupalDrupal version: Drupal 6.xDrupal 7.x
Interested in what is happening with Drupal Association membership? Here's a recap of 2014.
Last year, the Drupal Association membership program had a solid renewal rate, slight overall growth, and we surpassed revenue goals. We're happy to point out that even though the overall number of Organization Members has declined (our peak was 619 active organization members in 2013), it's because 82 of those companies have become our Supporters. This means they give at even greater levels than members. To all of our supporters, cheers and thank you for giving back to Drupal!
(For the general public: if you see a profile or company page on Drupal.org with a badge on it, you can thank the individual or organization for all that they do for Drupal!)
Do you have more thoughts or questions about membership? Find me via contact form anytime with your feedback.Membership
Have lots of books on your website? Are they a nightmare to manage? This module allows you to categorize your books into categories so that they're a little easier to manage.
This module replaces the view of your books on admin/content/book so that you can place your books into Categories. You can create whatever categories you'd like. Once books are categorized, they will show up underneath those categories on the node edit page.
We have two team members slated to speak at two different Drupal Camps in March!
Gus Childs will be delivering a talk at MidCamp in Chicago titled, "Need a Better Way to Organize Your Features? Go Ask Alice." It’s based on a blog post of ours and he’ll cover Features best practices and how to stay sane while using them on your bigger projects.
Mark Dorison will be speaking at DrupalCamp NOLA on 3/28. His talk, "Spend More Time Surfing: Simplifying Your Code (and Life) With Entityfieldquery & EntityMetadataWrapper" will cover methods you can use right now to work with entities in Drupal 7.
If you’re attending either of these camps, be sure to say “hello” to Gus, Mark, or any other CHROMATIC team member that might be floating around. You just might land yourself a CHROMATIC t-shirt!
Today we’ll analyze the module MEFIBS (More Exposed Forms In Blocks).
Lately I often lighted on having the need to insert some exposed filters in more blocks, staying on the same view!
Since the last Drupal Core Update, the Drupal community has reduced the number of D8 critical issues to 45, and managed to keep the number of critical issues on one pagesince we hit 50 criticals on March 6th! We've also changed the behavior of the "admin role" setting so that any user with the "admin role" passes all permission checks automatically (like the superuser); added HTML5-lib to core so that HTML5 can be parsed properly; and fixed a bug preventing all PHPUnit tests from running.
Also, after a few months of work, the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers presented their proposed changes to the project application review process. They're looking for your feedback, so please read their proposal and leave your thoughts!
Some other highlights of the month were:
- xjm performed a detailed analysis of contibution and influence in Drupal 8.
- To improve user experience, field types are now grouped by category.
- Josh Taylor detailed how to automatically test contrib modules when Drupal 8 updates.
- On the front end, the $messages page element was converted into a block, a filter to render render-arrays was added to Twig, views base fields are now rendered like Field UI fields; the button, skip link, and comment components now follow CSS standards; and menu classes were added back.
- Sujith Nara wrote an overview of all the caching methods available in Drupal 8.
- To improve performance, getting fresh entity and field definitions no longer invalidates all caches, views exposed filter forms no longer cause cache tables to grow exponentially, views now sets cache tags on it's render arrays, views can now cache base tables and entity types, routes are now rebuilt on write; and the unused block_plugin cache tags were removed.
- Daniel Sipos wrote a tutorial on creating custom field formatters in Drupal 8.
- To improve developer experience, developers can enable an X-Drupal-Cache-Contexts HTML header to list cache tags, and entities and fields can now report which language their content is in.
- Amber Matz wrote an excellent article explaining dependency injection using real-world examples.
- Lee Rowlands explained the tradeoffs of using the Events system versus Alter hooks in Drupal 8.
- The procedural functions drupal_bootstrap(), drupal_get_bootstrap_phase(), language_load(), language_list(), language_default(), drupal_theme_access(), drupal_html_id(), node_type_load(), node_type_get_types(), entity_load('node_type'), entity_load_multiple('node_type'), request_uri(), system_rebuild_theme_data(), and entity_load_by_uuid() were all removed, as was the html => TRUE option to l() and the $script_path global variable.
See Help get Drupal 8 released! for updated information on the current state of the release and more information on how you can help.
We're also looking for more contributors to help compile these posts. Contact mparker17 if you'd like to help!Drupal 8 In Real Life
Voting in the Drupal Association's 2015 At-Large Board Elections ends Friday, so this is your last chance to make your voice heard! Anyone with a Drupal.org account that was created before the time nominations opened (January 31, 2015), and who has logged in at least once in the past year is allowed to vote, even if they are not a member of the Drupal Association!
Some other events happening in the coming weeks are:
- MidCamp starts tomorrow (March 19th) and runs until March 22nd at the University of Illinois in Chicago, Illinois, USA.
- DrupalCamp New Orleans will be on March 28th in New Orleans, LA, USA.
- Stanford Drupal Camp 2015 in Stanford, CA, USA will be on April 10th and 11th.
- Drupal Dev Days, a week of sprints among core contributors and Drupal veterans with awesome sessions on D8, is less than a month away (April 13—19), hosted in Montpellier, France. All the early bird tickets are gone, so buy your tickets soon!
- In case you missed it, DrupalCamp Ottawa has been postponed to summer 2015.
Do you follow Drupal Planet with devotion, or keep a close eye on the Drupal event calendar, or git pull origin 8.0.x every morning without fail before your coffee? We're looking for more contributors to help compile these posts. You could either take a few hours once every six weeks or so to put together a whole post, or help with one section more regularly. If you'd like to volunteer for helping to draft these posts, please follow the steps here!
It can be difficult to decide whether to send representatives of your organization to DrupalCon. You may find yourself asking questions like, what's the ROI? What’s the value of being there in person? Is it really worth the money? There are tremendous benefits, measurable and immeasurable, to sending your employees to DrupalCon. Here are three reasons why going is a win-win for both your employees and your organization.
Signifyd protects your online store with enterprise grade fraud technology.
For the past few months, members of the Technical Working Group, Drupal.org Software Working Group, Security Working Group, and frequent project application reviewers have been working on proposed changes to the project application review process.
The proposed changes have been posted for public review. https://www.drupal.org/node/2453587
If you have any comments or questions, please add them to the issue. This proposal is open for feedback until the end of March. We will then incorporate the feedback and start working on implementing these changes.
In Pratchett’s “Going Postal”, workers who die in the line of duty have their names transmitted up and down the Discworld’s telegraph system as a tribute.
Drupal 8 comes with two extension points for module developers to allow other modules to interact with their code.
The trusty alter hook, the linchpin of Drupal versions past is still there - allowing other modules to interact and intervene in the behaviour of your module.
But there is a new kid on the block, the event system.
So as a module developer how do you decide whether to use the alter system or the event system.
Do you plan meet-ups, camps, sprints, or trainings for your local community? The Drupal Association is creating a new Community Organizer Newsletter, so be sure to sign up on your Drupal.org profile. Read on to find out more!
This past January, I celebrated my one-year anniversary of employment at the Drupal Association. I came to the Association from a community management background, working with multiple stakeholders in a distributed community; the role as Community Outreach Coordinator itself appealed to me because I knew the Association serves a strong, active, and connected community. I thought that the community aspect of my job would be nothing I hadn’t encountered before, as I knew I’d be working with very similar community models. What I did not know at the time was the astonishing amount of effort that our volunteers put in to better their local communities and therefore enhance a global community.
Over the past year, I’ve been fortunate enough to visit several camps, attend and participate in planning DrupalCons, sit in on Community Summits, and have countless interactions with volunteers from around the world. One thing that has resonated with me as I started to connect to volunteers globally is that many community organizers often ask similar questions about other communities and volunteers. What are others doing for camps? What are others doing for hosting a sprint? Do others struggle to get people to meetups? How do we engage new leadership? Does the Drupal Association have resources to support our local community groups and user groups?
The frequency with which I have encountered these questions got me thinking: how do we highlight the efforts of our volunteers and share best practices with everyone. After all, we’re open source, and sharing is how we do things. We’re a do-ocracy! After a lot of thought, I realized that the best way to accomplish this task will have to be collaborative.
I’ll be working with our talented staff at the Association and volunteers to create a quarterly Drupal Community Organizers Newsletter full of tips, tricks, and news for anyone who runs, organizes, or wants to help grow their local community. The best part is that this newsletter will be mostly curated content from you all, our organizers! Who better to help others than our troops in the trenches? I’ll be including blogs, upcoming camps and sprints, best practices, highlights from communities, volunteer recognition and more information.
I anticipate that we will release the first issue in the beginning of April, at the start of this year’s Second Quarter. As part of this effort, I need your help. Would you like to receive the newsletter? Sign up HERE , and contact me HERE if you have content (or know of content) that would be great to share with our community organizers. Know other community organizers? Spread the word and get them on the list! Let’s work together to share and support each other in our global Drupal Community.
No Bob this week but we soldier on in this week's episode.
Your browser does not support the audio element.
Episode 2 Audio Download Link
When originally building the Marconi module, I did not realize that Openstack project names change. Most recently, the name of the queue project in Openstack was renamed to Zaqar. To avoid further renaming issues, I have renamed the Drupal module to Openstack Queues.
Openstack Zaqar provides a queuing service similar to Amazon SQS for Openstack-based providers. It is currently known to be running in production at Rackspace. This site as well as several sites that we host currently use the Openstack Queues module.
The Openstack Queues module allows Drupal to use Openstack Zaqar as a queue backend.
You know It's coming - you can feel it, hear it, and see it - the low but powerful rumbling of change - the next big wave of innovation in ecommerce.
Buying and selling online has become second nature and a core part of our lives - yet there is fundamental change underway in how people are thinking about ecommerce and how transactions of all kinds should be woven into the fabric of an engaging online user experience.Content Sells
The importance of content in creating online experiences that drive people to buy is becoming increasingly important to online merchants and brands. Is there any doubt that this next wave of innovation will in part be centered around a more fluid content driven commerce experience?
Companies who are using a traditional catalog based ecommerce solution are realizing the importance of content to online revenue growth and that simply integrating their ecommerce solution with a separate CMS solution is ultimately not a great solution and creates unnecessary complexity. As a result, many companies with mature online revenue channels are beginning to define their next generation systems.Ingredients of a Revolution
Fundamental change and a common vision are key ingredients for any Revolution. Mix in a large and growing community of stakeholders who all stand to benefit from this change and you begin to see momentum shift.
But it all starts with needs that are not being met.
Talk to anyone who has been using or delivering ecommerce solutions over the past view years and you will hear a discontent with their current system and in general the future of ecommerce.
What is the source of this discontent and what do they want their ecommerce solution to do that it isn't doing now? Here is what we hear.
- My current ecommerce solution doesn't provide me with powerful enough CMS functionality to deliver the type of experience that I need to attract and keep users on my site.
- I have too many systems to manage and maintain - one for content, one for online transactions, one for orders, fulfillment, and inventory and it's hard to integrate them and expensive to support - and even harder to create a unified experience for my users.
- I need to be much more agile and timely in adapting to changes in the market and responding to the changing behavior of my customers. My technology needs to support this iterative approach that is critical for my business.
- Technology is way too complex so I really would like a service that insulates me from the complexities of technology so that I can focus on my business - BUT - I don't want to sacrifice flexibility and control over the functionality my business needs and I CAN'T be locked into a single vendor who doesn't have my interests in mind.
- I need ecommerce functionality that is more modular - rather than an all-in-one solution that resides in a large and separate codebase - so that I have greater flexibility in how and where commerce exists on my site.
While Drupal + Drupal Commerce won't solve all of your problems, it will address many of these fundamental challenges, and it will solve them far better than most ecommerce solutions today.
Why? Because it is built, supported, and extended on a massive scale by the largest open source community to address the needs of users just like you.Join the Revolution
Want to be part of this change? Join us for the first Commerce Revolution on Monday afternoon, May 11 right before the start of DrupalCon Los Angeles. This is a great opportunity to learn, engage, and hear how customers, integrators, and agencies are addressing the shifing needs in ecommerce with Drupal + Drupal Commerce. This is an exclusive, invitation only event. If you would like to receive more information when we officially announce the Commerce Revolution on March 30, please let us know by completing the form below.
STBE is a library of attractive looking HTML elements and integrates with various modules help content creators and designers use these elements in websites. The module was built as part of the Drupal CMS Powerstart distribution.
Part of learning Drupal’s API is learning about “what’s in the pantry.” In Drupal 8, that pantry is configured quite a bit differently than before. Instead of getting the whole warehouse of Drupal functions on every page load, functions—well, now methods—are contained in objects which are defined by classes. Most, if not all, of these classes, which exist in their own PHP files, can be extended and many of them are specifically designed to be extended. These extensible classes are the pantries. They contain properties and methods that we can just use in the classes that extend them. When we extend these classes, we need to make sure we peek inside to see what’s available before we go elsewhere for something that might already be in the cupboard.