I am a big car, and I'm a strip bar, Call it fake, I call it good as it gets.
Drupal 7.33, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.33 release notes for a full listing.Download Drupal 7.33
Upgrading your existing Drupal 7 sites is recommended. There are no major new features in this release. For more information about the Drupal 7.x release series, consult the Drupal 7.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 includes the built-in Update Manager module, which informs you about important updates to your modules and themes.
There are no security fixes in this release of Drupal core.Bug reports
Drupal 7.33 contains bug fixes and small API/feature improvements only. The full list of changes between the 7.32 and 7.33 releases can be found by reading the 7.33 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.Update notes
See the 7.33 release notes for details on important changes in this release.Known issues
None.Front page news: Planet DrupalDrupal version: Drupal 7.x
Have you ever had to try to hide a title on a page in Drupal? Maybe you created a page to be your front page and don't want the Node title to show up. The Exclude Node Title module makes this situation or any other situation in which you need to hide a node title, as simple as a few clicks of the mouse.Tags: DrupalDrupal 7Drupal Planet
This provides some verbose logging for the Message Notify module.
It will log message sending to the DB.
You need the following two forks in the message stack to make this logging work:
Adds file info (file type icon, extension, size) to local managed file links.
This module offers a filter called "Append File Info Filter" which adds file info to any Media links (ie. media/3), File Entity links (ie. file/3) and Drupal core File links (ie. sites/default/files/example.pdf).
It also offers a theme override which adds this information to themed file links.
I had a chance to try the upcoming (Drupal) Acquia Certified Developer - Front end Specialist Certification Exam. Thanks to Acquia Certification Team for allowing me to try it out.
I have been able to clear it with an 83% score. That was way beyond what I was expecting. I expected the exam to focus heavily on advanced CSS and JS and hence was not expecting a good score. But it turned out the exam gives good weightage to Drupal theming and templating and various other concepts in Drupal that gave me a fair chance to score.
The exam evaluates you on the following areas:
Fundamental Web Development Concepts
The official exam blue print and curriculum is not released by Acquia yet. So I do not have the links here for you. They should be out soon. The exam is scheduled to be released for public on December 1st.
But for any of you taking the exam pre-release, or if you are planning to take the exam immediately after the release, here is some information for you that could help you in your preparation before the official study guide comes out.
Fundamental Web Development Concepts
There were questions about CSS, JS, Jquery. Some of the resources that could help:
Drupal + CSS
Responsive Web Design:
A fair idea of any one of those CSS grid systems would help
Knowledge of some of the new elements in HTML5
You should make yourself thoroughly familiar with all the Theming and Advanced Theming chapters in The Definitive Guide to Drupal 7.
Sub- Theming Concepts
This notes is very specific to the Front End Specialist Certification. If you are looking for Acquia Certified Developer examination, check out my previous post on Cracking Acquia Drupal Certification.
Drop in your comments below if you have any additional resources that would help in the exam preparation that I have missed above.
In Drupal 8, we’ve significantly improved the way pages are rendered. I will explain the entire render pipeline, which will also cover:
- render caching — blocks and entities are now render cached automatically!
- cache tags — finally we have the cache invalidation system we’ve always needed!
- assets — only the necessary assets are loaded anymore, thanks to asset dependencies!
- bubbling — rather than relying on global statics that broke caching, we now correctly bubble up all attached metadata — no more frustrations!
But I will also explain what is going to be possible in Drupal 8:
- anonymous page loads: invalidating Varnish/CDNs with perfect precision
- authenticated page loads: not completely regenerated on every page load, but assembled from render cached parts
- alternative render strategies, like Big Pipe
Where relevant, I’ll compare with Drupal 7, how you can write Drupal 7 code today that will be easy to upgrade to Drupal 8, and which Drupal 7 backports exist (hint: Big Pipe does exist!).Slides: Drupal 8's render pipelineConference: DrupalCamp GhentLocation: Ghent, BelgiumDate: Nov 7 2014 - 09:30Duration: 45 minutesExtra information:
This webinar is an update to Dante Taylor’s TWIG: Getting Started in Drupal 8 presentation from October 2013. The most significant change to Drupal 8 theming is the introduction of the Classy Theme, which was part of the 8.0.0-beta2 release last month. In a nutshell, Classy is a base theme for those who want to have templates with the core classes. Setting Classy as a base is simple—add the following line to the theme.info.yml file inside the theme directory:
For all the sites I maintain, I have at least a local and production environment. Some projects warrant a dev, qa, etc. as well, but for the purposes of this post, let's just assume you often run drush commands on local or development environments during development, and eventually run a similar command on production during a deployment.
What happens if, at some point, you are churning through some Drush commands, using aliases (e.g. drush @site.local break-all-the-things to break things for testing), and you accidentally enter @site.prod instead of @site.local? Or what if you were doing something potentially disastrous, like deleting a database table locally so you can test a module install file, using drush sqlq to run a query?
Achievements and activity tracking module. Allows developers two write their own achievements.
Drupal core and contributed modules events wrapped in an observer design pattern.
Commerce closure make sells disabled during period.Why to do such a thing ?
For some people, e-commerce is not something which can be accessible at full time. Especially for little shop with hand made products, if shop owner is also maker and seller, events like outdoor market don't let them have 2 stocks (one for market, one for website), there are no more time to ship. So they may be want to make their e-commerce activities off.
This module will be released at http://drupalcamp.berlin . More information to come. Stay tuned.
Drupal has everything you need to start a full-featured online business. Drupal is open, free and flexible – and it provides all the components required to integrate content, commerce and community features. With just a few of the 15,000+ modules, it’s possible to build almost any web application you need. With the ERPAL Platform Drupal distribution, Drupal developers and site builders get a pre-configured Drupal installation as a starting point for flexible and open business applications. As one of our first use cases, I want to show how you can use ERPAL Platform to build your complete online business within a single Drupal installation. In this blogpost I’ll cover the overall functionality of this e-commerce use case and in one of the next blogposts I’ll show you in detail how to build your online shop, complete with all the administration features you need to manage your online business.Business processes first
No matter whether you sell services, projects, or products; no matter whether you sell them online or offline: all business will go through the same basic steps. Starting with the first customer contact to begin the sales process, you’ll mostly be tracking leads that will be transformed into opportunities and become prospects. In the prospect status you’ll create a quote for your customer in which you offer the products and services that the customer requested. After the quote is accepted, it becomes an order (which may be different from the quote). The order confirmation is sent as a receipt to your customer. Now it depends on the payment modalities negotiated before the order as to how and when you can create one or more invoices to get paid. You may get some upfront payment with the submission of the order, after some or all products have been delivered, or once you’ve reached a certain milestone in a project or manufacturing process. So no matter what you deliver to your customer, you get paid either in advance or upon delivery, or a combination of both.
This sales process is always fundamentally the same and it’s the core functionality that ERPAL Platform provides. With Drupal Commerce entities for quotes, orders and invoices, this business process is flexible and can be extended with fields, rules and views. With these features the administrative backend for the general business process is already in place, and you can extend it as you need. Read one of the first ERPAL Platform blog posts for more details about this business process and how it’s implemented in ERPAL PlatformIntegrate a Drupal Commerce storefront
Since Drupal Commerce is already integrated into ERPAL Platform, it’s easy to extend the feature set with an e-commerce storefront. At the "frontend" you sell your products to your customers. They can buy any products directly in the web from an online store that’s built on top of your business process platform. If you already know Drupal Commerce, it’s easy to extend ERPAL Platform to expose a storefront to website visitors. In this use case, the ERPAL Platform features will serve a complete administrative backend – visible only to shop administrators – for all your business processes.
Imagine we have three commerce order bundles – order, quote and invoice – to separate these entities. If a user adds a product to her cart, this is an order entity. For an order entity that’s not yet checked out, as a customer you can request a quote, which can be used to compare products and prices with other stores or to show to another party (as PDF). If the customer comes back, she can continue with the order and complete the checkout process. After the checkout is complete, the invoice is created as a separate entity and both the user and the shop administrator can access all these receipts in the same Drupal installation: no synchronization between systems needed. If a payment is made, it’s added to the invoice and changes the balance. That’s it! There you have all you need to process your business in a nutshell. If you build an e-commerce site for a start-up you may want to begin lean and without heavy integration projects. With ERPAL Platform you have all the features in one distribution to start an online business and to continue to grow it in an agile way.
In one of our next blogposts, we’ll present a step-by-step guide for building an online business based on ERPAL Platform.
In our upcomming webinar with the Commerce Guys, we will talk about open integration of Drupal Commerce and give a real use case of an ERPAL Platform project that integrates all online-business process in one platform.