Planète Drupal

Start:  2012-04-03 19:00 Europe/Paris User group meeting Organizers:  ninizik

L'occasion de faire connaissance, de discuter de Drupal autour d'un verre. ( et qui sait, de prévoir d'autres réunions peut être plus techniques)

Pas de sujets précis pour le moment.

Le lieu ? : Le 28 Thiers Cafe - 28 Rue Thiers, Lille ( métro Rihour)

France

Start:  2012-05-26 (All day) - 2012-05-27 (All day) Europe/Paris Drupalcamp or Regional Summit

Vous avez vu le Twit d'Artusamak aujourd'hui ?

Et, oui, le DrupalCamp Lyon approche. Ce sera donc les samedi 26 et dimanche 27 mai.

Notez-le vite dans votre agenda.

Plus d'infos très bientôt.

France

Training (free or commercial)

Pas d'annonce de formation payante sur le groupe France merci.

France

Training (free or commercial)

Pas d'annonce de formation payante sur le groupe France merci.

France

Training (free or commercial)

Pas d'annonce de formation payante sur le groupe France merci.

France

Discover Commerce Product Display Manager (shortname: commerce_pdm) in this new Commerce Module Tuesday screencast and see how to make product management easier for your commerce website.

Commerce Product Display Manager enables two UI features, the first one displays a widget in the product creation form and allows us to create a product display right from there or associate our product with an already created product display. The second feature of this module provides a dedicated administration screen with drag and drop capabilities to help managing products and displays.

Also in this screencast you'll find how to create product displays from product by using the rules provided here, and an alternative solution for the more code-like watchers that proposes a more advanced solution.

read more

Last weekend, we held a sprint at the Acquia offices for the Web Services and Context Core (WSCCI) Initiative for Drupal 8. This was an important sprint for the future of Drupal. This blog post provides a high-level overview of what was discussed and agreed upon; the different sprint participants will be laying out more technical details in follow-up blog posts.

Overall, a wide range of experience levels, skill sets, and perspectives were brought to the table, with the goal of the sprint being to clearly define the initiative’s scope, get agreement on what we wanted to accomplish and why, and lay out a clear plan for how to accomplish this.

In attendance were:

• Larry "Crell" Garfield, lead architect of the WSCCI initiative
• Daniel "sun" Kudwien, top Drupal core contributor
• Fabien "fabpot" Potencier, lead developer of the Symfony project
• Kris "EclipseGc" Vanderwater and James "neclimdul" Gilliland, who have helped develop and implement the plugin system as part of WSCCI
• Greg "heyrocker" Dunlap, initiative lead of the Configuration Management Initiative for Drupal 8
• Moshe Weitzman, long-time Drupal core contributor
• Angela "webchick" Byron, community cat herder and Drupal 7 core co-maintainer
• Randy "rfay" Fay, Justin "beejeebus" Randall and Alex "effulgentsia" Bronstein, core developers and sane voices of reason with an outside perspective
• Dries Buytaert (me), project lead

Scope

The WSCCI initiative, as envisioned by Larry Garfield, was originally set to address Drupal's web services and flexible page layout capabilities. We discovered that both would require significant changes to Drupal core, and it was difficult to build consensus online, so we decided to get together for 3 days and to flesh out what we actually wanted to accomplish, and how.

At the sprint, we first attempted to articulate all of the problems that WSCCI was trying to solve, which included: multiple page layouts, better UI/UX to manage blocks, partial page rendering (ESI, AHAH), contextual blocks, different response types per delivery callback/URL, plugin system / swappable subsystems, lazy loading bootstrap (convert subsystems to PSR-0 classes), infrastructure for building web services, dependency injection, and so on.

We then did a round of voting where we could each choose 3 of those things in order to try to determine which of those were the most important.

Two things became instantly clear during this exercise:

1. The items encompassed under WSCCI really spanned at least 3 separate major areas: Web Services, more robust ESI-based layouts (think Panels only more powerful), and cleaning up our underlying toolset to be a more loosely-coupled framework.
2. The underlying architecture to support RESTful calls to Drupal that makes all of the other things possible was deemed the most important thing to focus on.

Scope resolution

After a good chunk of discussions, all were in agreement to scale back the scope of the initiative to just the "Web Services" piece, and spin off the Layout/blocks/related-UI parts to a separate effort.

Furthermore, some efforts, such as PSR-0 and Unified Plugin system, were only semi-related to the WSCCI initiative in the first place, and just happened to become relevant for it. Work on those efforts will continue as part of the general Framework community efforts.

Architecture

Fabien was able to offer a tremendous number of insights as to how various Symfony2 components could help provide underlying structure for Drupal core to support Web Services out of the box. Essentially, most of what the WSCCI team had been trying to work toward, in the abstract, was already implemented within Symfony2. While some implementation details were different than what we had in mind, the end result is almost exactly what we have been trying to accomplish. We therefore agreed that the best way forward was to leverage several Symfony2 components within Drupal as a way to speed progress toward that end.

Benefits

Some of the concrete benefits that would come out of these changes are

• An underlying framework that is a first-class REST citizen. That means developing web services becomes easier and more efficient, because the plumbing is already in place. An HTML page is a particular case of a REST service.
• Because the core system will be fully REST-ified, we'll be able to improve existing APIs and expose Drupal content in a natively RESTful way. For example, our current AJAX system doesn't comply with REST standards, but with these changes, can be cleaned up to do so.
• That in turn makes Drupal-to-Drupal communication, content staging, content sharing, and a host of other related tasks easier.
• The use of widely used libraries and techniques makes Drupal more approachable to new developers.

Why does this matter?

As it has evolved into an increasingly powerful system, Drupal has gotten increasingly complex and is not as easy to start developing with as it once was. Many developers are nervous about continuing that trend. Managing complexity is a challenge faced by many software projects, and one approach is to use standardized patterns and components.

Due to its long support for PHP 4, as well as some unique needs, Drupal does not take full advantage of standardized patterns and components. The complexity of the custom code that’s used and the non-standard architecture combines to create a barrier to entry for developers new to Drupal (both experienced and novice developers alike).

Meanwhile, the web is constantly changing around us. Web services and mobile are more important than ever, and with that comes the need to have more flexible page and layout capabilities. Now feels like the right time to modernize Drupal’s capabilities to bring it to the forefront of modern PHP systems and web systems in general.

While changing Drupal's core plumbing to address these needs, it's also a good opportunity to do so using more widely understood and modern techniques and libraries. Leveraging the work of a fellow open source community lets us get a jump on these changes to build a more powerful, more flexible, and more easily learnable system in less time than it would take to go it our own.

While these changes may seem large, and some of them are, we believe that they will achieve the right balance between empowering Drupal's design and architecture, and moving toward more modern, standard, well-tested code and techniques to empower a new generation of developers. I hope you are as excited as we are!

Commerce Guys’ Module Now Fastest Growing in Drupal eCommerce

Jackson, MI (PRWEB) February 15, 2012

Commerce Guys, the leading eCommerce specialists with Drupal, announces its highly flexible eCommerce platform, Drupal Commerce, is now in use in over 10,000 websites worldwide. Drupal, a robust, open-source web application framework and social publishing platform, continues to gain traction as a powerful eCommerce solution.

read more

Last summer, I blogged about how I think about Drupal release date planning, tying it to the Gartner hype cycle and the corollary Drupal mood cycle.

The release timeline I laid out in my previous blog post was a Drupal 8 release 18 months after Drupal 7 had achieved the “Plateau of Productivity", the point in time where developing in Drupal 6 seems mostly pointless due to the maturity of Drupal 7.

At that time, I said that I felt that Drupal 7’s “plateau of productivity" was about 6-9 months away. Today, almost 9 months later, I think that by any reasonable measure we are currently there. There are over 300,000 live Drupal 7 installations, which represents nearly 50% of all reported Drupal sites. The top Drupal modules all have Drupal 7 releases, the vast majority of which are either stable releases or release candidates.

Having reached the “plateau of productivity" also means that I feel comfortable announcing the Drupal 8 release timeline. Without further ado, here is how the rest of the Drupal release cycle breaks down:

Timeline:

• December 1, 2012: Feature freeze. No new features are allowed (unless specifically exempted), focus turns instead to API and UI clean-ups and polishing of existing features.
• February 1, 2013: Code freeze: focus on bug fixes, stabilization. No API changes, instead focusing on bug fixing, preparing for release, and getting the count of critical bugs down to 0.
• August, 2013 (DrupalCon Europe 2013): Drupal 8 released, to wild, international fanfare. :-)

This means that Drupal 8 is 18 months away. Time to shift Drupal 8 core development into higher gear!

The ~6-month window for bug fixes laid out here is obviously much shorter than the 18-month window for bug fixes we ended up having with Drupal 7, but the hope is that the issue count thresholds that we’ve introduced this release will ensure this process is much shorter than in Drupal 7, since we’ll be going from approximately 15 down to 0, rather than approximately 300 to 0.

This timeline also means that if there are Drupal 8 initiatives you’d like to see happen, or other specific features or things you want to see fixed in Drupal core, now is the time to make those things happen. If you’ve never helped with Drupal core development before and would like to, stop by IRC during Core office hours, or join us at DrupalCon Denver. There will also be plenty of other sprints at DrupalCon around various Drupal core initiatives, and you can always start your own!

See you in Denver and in the issue queue! :-)

Commerce extra price formatters provides a number of extra formatters for displaying commerce prices that extend the current ones provided by Commerce core.
Currently this module enables these three formatters but there will be probably others in the future:
- Retail Prices / Your price: A similar feature than Commerce Price Savings Formatter but with a different display result, allowing you to show the original, unmodified price of a product and next to it the user price, in tabular format.
- Prefix and Suffix for prices: Easily add extra labels to your prices, e.g. for indicating that a price is a special limited offer.
- No decimal places: If you only need whole unit prices, this is the formatter for you, this option will disable the decimals of your prices, turning 10.00€ into 10€.

Bonjour à tous,

Notre bonne résolution 2012 est de mettre à disposition un blog sur Drupal 7 orienté développeur : http://www.drupalons.fr . Nous y avons déjà adjoints des petits outils de type agrégateur de flux Drupal en anglais et en français et même le début d'un générateur de code pour créer ses modules plus rapidement.

N'hésitez pas me dire ce que vous en pensez ! (j'avoue, on ne s'est pas foulé sur le graphisme pour l'instant...).

France

Commerce Customizable Products is another module that provides custom line item types like Commerce Custom Line Items, which I've shown before.

Our goal here is to sell a T-shirt with a customizable slogan on it. This could be any customization, and there could be more than one field. Here's how we do it:

1. Enable Commerce Customizable Products.
2. Create a custom line item type which will have the extra field. (We wouldn't have to do this if all products in our store had this customization.)
3. Add the field to the new line item type. In this case it's a text field called "slogan".
4. Create a special product display content type (with a product reference field) so that we can configure the display settings on the product reference field.
5. Configure the display settings to use our custom line item type (and tell it not to try to combine like items in the cart).
6. Create product and product display node to try it out.

For extra credit in the video we add the new field to the cart view, and even give the customer the option to edit it in the cart view by using the excellent Editable Fields module.

Here's the screencast:

SEO and Web Design Telecommute Telemarketing Vacancy

France or UK English Speaking Telemarketing Vacancy

1 Website Designer (http://www.1websitedesigner.com) is a creative Drupal web design and SEO company.

We are looking to establish a long term relationship with an experienced Telemarketing professional. This is a freelance, work from home Telemarketing vacancy for a candidate in the UK or France. All calls will be completed in English and we require the Telemarketing person to be a fluent English speaker.

1 Website Designer was established in 2006 and offers 3 core services:

Website design and development (from simple websites to complex websites such as e-commerce stores and property portals).

Search Engine Optimization (SEO) in English and French – optimizing websites and building links to them to increase their position with Google et al and generate many more visitors to their sites as a result of this.

Graphic design – Including complete web graphic design, logos, business cards, illustrations, etc.

The vacancy will involve calling businesses in specified categories and asking if they would be interested in a website redesign or in appearing on the first page with Google through an effective SEO service.

Training will be provided on SEO and web design and you will also be provided with scripts, presentations and other material, as well as being able to refer companies to a range of websites providing information on our different services.

Commission

We offer different commission structures depending on the type of project won, as follows:

SEO – 20% commission on the first month’s SEO payment, an additional 15% commission on the second month’s SEO payment. £100 minimum commission on any SEO project.

Web and Graphic Design – 10% commission on any projects agreed within the first month. £50 minimum commission on any graphic or web project.

We have already completed a large number of successful SEO and web design projects in the UK, France and internationally and will provide details of these; it is therefore easy to show potential clients previous examples of our success.

Ethics

1 Website Designer is an ethical organisation. We do not accept work for adult sites, gambling sites or other dubious projects. All our SEO is completed in an ethical and organic fashion, delivering a long term benefit to our clients, not simply by paying Google for Adwords.

We never ask clients to commit to long term SEO projects and provide a realistic indication of what our services will achieve.

We are looking for a Telemarketing professional who will operate to similar ethical standards in relation to their dealing with potential clients.

The Ideal Candidate

Given that different potential clients will have different needs, we are looking for someone who is perceptive and can tailor what they offer to each individual. If someone isn’t interested, our policy is to say a polite “good bye” and move onto the next person. We are looking for a professional Telemarketing person who communicates respectfully and can ask sufficient questions for us to send a proposal tailored to that individual.

Essential skills:

Previous experience in sales or marketing

Fluent English speaking

Polite and professional manner.

A quick learner who is self-motivated and confident

Desirable skills

None of the following skills are essential for this role, but if you do have them, please mention it in your application:

Experience or knowledge of web design or SEO

Any level of French

We look forward to hearing from all candidates interested in the telecommute web design and SEO Telemarketing vacancy with 1 Website Designer, UK. 

To apply for the telesales vacancy, please send:

A covering letter

Your CV

Names and telephone numbers of at least 2 references

To telesales@1websitedesigner.com.

France

Voting is now open for the 2012 election of at large directors of the Drupal Association. Two directors will be elected from among the ten candidates.

About the Drupal Association elections

When we designed a new governance structure for the Drupal Association last year, we decided that most of the board is selected through a nominating committee with the goal to carefully balance many factors like needed skills and geographical and sector representation. However, it was also deemed important that we have directors chosen directly by the Drupal community to make sure that the community is always well-represented.

We're holding our first open community elections! Two community "at large" directors will be elected to the Drupal Association Board of Directors, and YOU can get to say who they are!

Where to find out about candidates

• Review their nomination profiles.
• Read the notes from the two all candidates' meetings at http://groups.drupal.org/node/207398.

Who can vote?

Voting is open to all individuals who registered an account on drupal.org prior to January 18, 2012 and who have logged into that account at least once in the one-year period prior to February 3, 2012.

There is no need to register to vote. The voting system has been set up and prepopulated with the list of eligible voters.

How to vote

• Log in to this site.
• Visit the https://association.drupal.org/2012-vote page. After clicking through, you will be asked to rank each of the eligible voters, from 1st (top choice) to 10th (last choice). You also need to check a box confirming you're an eligible voter. Make your selections and save the form. That's it!

How does voting work?

The voting is done using the "Instant Runoff" voting method, powered by Decisions module. For more about this method of voting, please see this helpful YouTube video which explains it with post-it notes: http://www.youtube.com/watch?v=wA3_t-08Vr0

Can I change my mind after I've voted?

Yes! Before the close of voting, you can return to the voting form, cancel your previous vote, and submit a new vote.

When will voting close?

Voting will close at midnight UTC on Tuesday, February 7, 2012.

How will results be determined and announced?

When voting closes, a four-member elections team will review the results and post them to this site (association.drupal.org). Results will then be forwarded to the Drupal Association board for ratification.

The election team includes Angela Byron, DA board member; Cary Gordon, DA board member; Nedjo Rogers, DA advisory board member; and Thomas Svenson, Drupal community member who participated in the community process of planning the elections.

Why was voting delayed?

We had focused a bit too much on organizing the elections and left finalizing the actual voting system till the last minute. After several community members and Drupal Association staff pitched in, we got the elections system up about 3 hours after the planned opening of voting.

Wait. Only XXX eligible voters? What gives?

Despite the fact that the voting form lists far fewer, there are actually 270K Drupal.org accounts that fit the voter eligibility criteria. Valid accounts are added to the electorate list when they visit the Association website. These shenanigans are due to the Bakery module, our single-sign on solution, and the requirement to reconcile peoples' Association.drupal.org user IDs and their Drupal.org user IDs.

Problems and solutions

If you believe you are eligible to vote and try to vote and cannot or encounter some error, please post an issue to the Drupal Association issue queue, selecting "elections" as the component.

More about the elections

• The nominations announcement.
• The elections plan.
• All elections posts.

Drupal 7.11 and 6.23, maintenance releases which fix security vulnerabilities are now available for download.

Drupal 7.12 and 6.24 also fix other issues reported through the bug tracking system.

Download Drupal 7.12
Download Drupal 6.24

Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement, more information on the 6.x releases can be found in the Drupal 6.0 release announcement. Drupal 5 is no longer maintained, upgrading to Drupal 6 is recommended.

Security information

We have a security announcement mailing list, a history of all security advisories, and 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, which informs you about important updates to your modules and themes.

Bug reports

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

Changelog

Drupal 7.11 only includes fixes for security issues. Drupal 7.12 also includes bugfixes. The full list of changes between the 7.10 and 7.12 releases can be found by reading the 7.12 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.23 only includes fixes for security issues. Drupal 6.24 also includes bugfixes. The full list of changes between the 6.22 and 6.24 releases can be found by reading the 6.24 release notes. A complete list of all bug fixes in the stable 6.x branch can be found at git commit log.

Security vulnerabilities

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

• SA-CORE-2012-001

To fix the security problem, please upgrade Drupal.

What is included with each release?

We made two versions of both Drupal 7 and 6 available, so you can choose to only include security fixes (Drupal 7.11 and 6.23 respectively) or security fixes and bugfixes (Drupal 7.12 and 6.24). You can choose your preferred version. We are trying to make it easier and quicker to roll out security updates by making security-only releases available as well as ones with bugfixes included. We hope this helps you roll out the fixes as soon as possible. Read more details in the handbook.

Update notes

The default.settings.php file was changed in Drupal 7.12, to add documentation about PDO attribute override capabilities that were added as a result of #1309278: Make PDO connection options configurable.

The robots.txt file was changed in Drupal 6.24 to block filter tips from search engines. The .htaccess and (default.)settings.php files were not changed in Drupal 6. Additionally, indexes were added to the node_comment_statistics and comment tables, for performance.

Known issues

Bug fixes in 7.12 release cause problems with the Internationalization (i18n) module. i18n users are encouraged to update to 7.11 to get the security fixes, and hold off on the 7.12 upgrade until #1351678: Follow menu_link_get_preferred active trail handling for custom menus and #1050466: The taxonomy index should be maintained in a node hook, not a field hook are resolved. (Note: Help here would be greatly appreciated!)

Elections for at large Drupal Association elections are kicking into high gear with two all candidates meetings this week before voting opens Friday.

Election candidates will participate in all candidates meetings are scheduled over the next two days (Wed., Thurs. or Fri., depending on your location). The first meeting, intended to work for people in the Asia and the Pacific, is scheduled for 01:00 UTC on Thursday. That's 5 PM PST on Wednesday for those in the US and Canada.

The second all candidates meeting at 17:00 UTC Thursday is timed for participants in Europe, Africa, and the Americas.

Then on Friday voting will open. Details on voting will be posted to association.drupal.org.

See the elections announcement for more on how to learn about the candidates.

Commerce Price table is a module that provides both a field type and a display formatter that allows to manage and displays prices in a table based in the quantity so that different prices can be shown depending on the quantity of products that the customer purchases.

It plays nice with the default price field, allowing to hide it in the edit forms and replacing it in a transparent way using the power of rules and all the pricing rules that you apply to prices are also applied to the price table, such as taxes, discounts, etc.

We're proud to present a new design for the Mollom.com website.

We first launched the Mollom.com site in 2007. For more than four years, Mollom.com was using the same design. As we grew Mollom, we wanted to address some of the issues that we've been stewing over since our original design. We have been planning to redesign the site for over a year now but work on the Mollom web service and developing new Mollom products have always had a higher priority so we haven't found the time to complete the new design until now.

The old Mollom.com design that we used from 2007 to early 2012.

The new design is the first step in our plans to reorganize the website. We still have updates to make to the content of some pages, for example. Already, we think the new design is a fresh new change that improves usability.

Take a look at the new mollom.com, we hope you like it!

The new Mollom.com website design.

This screencast demonstrates how to do custom per-product email notifications. After adding a multivalued "notification" field to the product, we can check through the order on order completion to see if there are products which have product owners who need to be notified. The logic is "When the checkout process is completed", Loop through the line items in the order. For each line item, call a component (a Rules subroutine) that checks to see if the line item is associated with a product, and if so, if it has notification fields filled out. If so, the action is to loop through the emails in the multivalued notification field and send a tokenized email to each one.

Before getting started I mention the three things that persistently give people trouble with Commerce and Rules, and some solutions:

1. Not understanding rules in the first place: Spend a few hours starting from the beginning with Itangalo's outstanding "Learn the Rules Framework" video series.
2. Not understanding how to bring related fields and entities into scope: Read the FAQ about bringing fields into scope from the Drupal Commerce FAQ.
3. Not understanding how to use conditions in a loop or how to use Rules Components (subroutines), which is something we'll demonstrate here.

Here's the screencast:

Comprehensive new release by the leading eCommerce team working with open-source powerhouse Drupal 7 includes 73 performance, usability and developer experience improvements.

read more