Planet Drupal

Subscribe to Planet Drupal feed
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 13 min 2 sec ago

groups.drupal.org frontpage posts: Looking for another Drupal 7 co-maintainer

Wed, 03/02/2016 - 10:05

I selected David Rothstein as my co-maintainer for Drupal 7 back in May of 2012. Since then, David has done a tremendous job shepherding the Drupal 7 release, paying very careful attention to the ramifications of any given patch and allowing ample time for "real world" testing before incorporating changes into the code base, ensuring that the code powering 2% of the Internet stays stable and performant.

However, after nearly 4 years of excellent stewardship on his own, David would like to also focus on other endeavors, including Drupal 8. Now the time has come to select an additional co-maintainer for Drupal 7. While David himself has recommended some excellent candidates, I'd also like to open the call out more broadly, to see if there are others who have an inclination and interest.

https://www.drupal.org/node/721106 contains comprehensive documentation on everything that a release manager does. In particular, the ideal candidate has the following traits:

  • Ample experience building "real world" sites/platforms on Drupal 7, particularly high-performant sites, sites with millions of records, or other edge cases.
  • Ample experience performing detailed and thorough technical reviews of patches, being particularly mindful of their effects on existing sites.
  • Ability to communicate calmly and respectfully when critiquing code.
  • Solid knowledge of Git and the Drupal.org release process.
  • Ideally, sponsored time to work through your employer to maintain Drupal 7, particularly around the first and third Wednesdays of the month, which are the Drupal core release windows.

Please either respond here or use my contact form if you'd like to be considered as a potential Drupal 7 co-maintainer. Thank you!

Categories: Elsewhere

Modules Unraveled: 154 Commerce 2.x for Drupal 8 with Bojan Zivanovic - Modules Unraveled Podcast

Wed, 03/02/2016 - 07:00
Published: Wed, 02/03/16Download this episodeCommerce 2.x for Drupal 8
  • What has been the biggest success of Commerce on D7?
    • By starting from scratch on D7 technologies we created a solution that is intuitive to Drupal developers and easier to extend. And with 60k installs, we’ve set a record for ecommerce on Drupal in general.
  • And what do you think have been its biggest weaknesses?
    • Not prioritizing UX from the start. Took us a year after the 1.0 release to create Inline Entity Form and recreate the admin screens as a part of the Kickstart. At that point many people already had the impression that Commerce was hard to use.
    • Not providing enough direction to developers. Flexibility is important, as is having unopinionated code. But developers also need to have a clear and obvious path forward. Having an opinionated layer on top, with sane defaults, can save a lot of development time and prevent frustration.
    • Not prioritizing certain features, leaving them to contrib instead. Modules that make up the checkout ux (checkout progress, checkout redirect, addressbook), discounts. Of course, all generals are smart after the battle.
  • How has that influenced the development of Commerce 2.x?
    • With Commerce 2.x we once again started from scratch, evaluating all feedback received in the 1.x cycle. We decided to address all three of these major points.
    • Better UX means paying more attention to the product and order admin experience, as well as providing better checkout out of the box.
    • Better APIs means doing more work for the developer, especially around pricing and taxes.
    • And finally, we’re growing the core functionality. We’re expecting a dozen contrib modules to be no longer needed, as we address edge cases and add functionality.
  • What are some of the biggest new features of Commerce 2.x?
    • Multi-store will allow people to bill customers from different branches (US and FR offices, for example), or create marketplaces like Etsy.
    • Improved support for international markets means better address forms, better currency management, and significantly better tax support, the kind that will reduce the need for people to use cloud-based tax solutions, at least in Europe.
    • Support for multiple order types, each with its own checkout and workflows will allow developers to create tailored experiences for different kinds of products, such as events, ebooks, t-shirts.
    • An integrated discounts UI means more power to the store admin.
    • And this is just the beginning. Under the hood there are many small features and improvements, over both 1.x and Kickstart.
  • What has Commerce done to integrate better with the PHP and Drupal communities?
    • We’ve created several independent ecommerce libraries, attacking currency formatting, address management and taxes. These libraries are now being adopted by the wider PHP community, bringing us additional contributors.
    • On the Drupal side we’ve joined forces with the Profile2 team, creating the D8 Profile module that we’ll use for customer profiles. We’re also depending on Inline Entity Form, which is now shared with the Media team. We’re also moving some of our generic entity code into a new Entity API module, maintained together with Daniel Wehner and other community members.
    • Finally, we have been champions of Composer, the replacement for Drush Make, and required for any module that depends on external libraries.
The Future of Commerce 2.x
  • Commerce 2.x is now in alpha2. What’s included? What’s next?
    • Alpha2 includes stores and products, as well as initial order and cart implementations.
    • It also has functional currency management and formatting, address and profile management.
    • Alpha3, to be released in the next two weeks, is focusing on completing the order and cart implementations, and adding the initial checkout implementation.
    • Post-alpha3 our focus will be on discounts, taxes, and finally, payments.
    • The best way to learn more about this is to read the drupalcommerce.org blog, where I post “Commerce 2.x stories” detailing work done so far. We have several new posts planned for february.
  • When can we expect Commerce 2.x to be production ready?
    • Our current goal is to release a production ready beta by end of march. We should also have Search API and Rules by then. Leading up to DrupalCon New Orleans we’ll be helping the community implement shipping and licensing and port payment modules. At the same time, we’ll be focusing on reaching RC status.
  • What’s the status of commerce contrib? Like PayPal, Authorize.net, etc.
  • How can the community help?
    • Each new alpha welcomes more manual testing and feedback.
    • We also have office hours every wednesday at 3PM GMT+1 on #drupal-commerce where people can discuss code and help out on individual issues.
  • Do you feel that requiring Commerce to be installed via Composer will impact adoption?
    • The average developer is already familiar with Composer and will benefit greatly from it, just like D7 developers benefited from Drush Make. Getting Drupal, Commerce, and all dependencies is a single Composer command, as is keeping it all up to date.
    • People unwilling to run Composer on their servers can run it locally and commit the result.
    • I’m also hoping we’ll be able to offer distribution-like tarballs on either drupal.org or drupalcommerce.org as we get closer to a release candidate.
Questions from Twitter
  • howdytom ‏@howdytom
    Commerce Kickstart provides a great toolset with basic configuration. Is there a plan to do a Commerce Kickstart for Drupal 8? If not, will Commerce provide more out of the box solutions for a full featured shop?
    • Commerce Kickstart had several parts.
    • The first one was about providing better admin and checkout UX, as well as discounts. That’s now handled by Commerce out of the box.
    • The second was about providing a demo store with a developed set of frontend pages. That’s going to stay in contrib and will greatly benefit from the flexibility introduced by Drupal 8 and CMI.
    • It’s too early to plan a distribution yet. Drupal 8 has almost no contrib, and drupal.org doesn’t support using Composer to build distributions yet.
    • However, we are using Composer to provide single-command site templates, the kind that gives you Drupal core, Commerce and other modules. This will allow us to provide good starting points for different use cases, similar in nature to Commerce Kickstart 1.x.
    • Once 2017 comes around, we’ll investigate next steps.
  • Jimmy Henderickx ‏@StryKaizer
    In commerce d8, will it be possible to alter a product name dynamicly (either by hook or other solution)?
  • Czövek András ‏@czovekandras
    Any plans making iframe payment methods 1st class citizens? Thinking of running checkout form callbacks.
  • Marc van Gend ‏@marcvangend
    How did D8 architecture change the way you code your modules?
Episode Links: Bojan on drupal.orgBojan on Twitter#Drupal-Commerce channel on IRCCommerce 2.x blog postsInstalling Commerce 2.x using ComposerDrupal Commerce DocumentationTim Millwood’s MultiversionTags: CommerceDrupal 8planet-drupal
Categories: Elsewhere

OSTraining: You Should Use the Drupal Security Review Module

Wed, 03/02/2016 - 02:53

There are two really useful checklist modules in Drupal:

In this video, taken from our Drupal 7 Security class, Robert introduces the Security Review module. He shows you how to fix some of the most common errors found by the module, such as "Base URL is not set in settings.php" and "Some files and directories in your install are writable". Even if you think your site is safe, give the Security Review module and you may well find something you missed.

Categories: Elsewhere

Drupal Watchdog: Welcome to DrupalCon Barcelona - The Director's Cut

Tue, 02/02/2016 - 17:48

For all you schedule-challenged CEOs – and ADHD coders – this Abbreviated Official Director’s Cut is just what the doctor ordered.

Yes, Welcome to DrupalCon can now be watched in half the previous time! But if eight minutes is still too daunting, we suggest you absorb it in a series of one-minute bursts, maybe during the rest-intervals in your 30-20-10 training, or on down time while obsessively clicking your pen waiting for the Adderall to kick in.

Enjoy!

Tags:  DrupalCon Barcelona Drupal Ron Brawer mini-documentary Drupal Association Tag1 Consulting Video: 
Categories: Elsewhere

Stanford Web Services Blog: Drupal 8 REST Requests

Tue, 02/02/2016 - 17:25

In November, 2015, the Stanford Web Services team got to dive into Drupal 8 during a weeklong sprint. I was excited to look at the RESTful web services that Drupal 8 gives out-of-the-box; what follows is my documentation of the various types of requests supported, required headers, responses, and response codes.

This is not intended to be an exhaustive documentation of RESTful web services in Drupal 8. However, I have pulled information from various posts around the Web, and my own experimentation, into this post.

Categories: Elsewhere

Deeson: Warden: Monitoring the Secruity of a Web Estate

Tue, 02/02/2016 - 13:30

Warden is a solution for in-house development teams and agencies who need to keep track of the status of many Drupal websites, hosted on a variety of different platforms.

Warden gives you a central dashboard which lists all your Drupal websites and highlights any which have issues, for example needing secuity updates.

Hosting companies, like Acquia and Pantheon, have their own reporting tools but these only work if you host on their platforms. If you have an estate of websites which run on multiple platforms you need a tool which can report on them all.

The Warden application is composed of two parts, a Warden module which you need to install on each of your websites and the central Warden dashboard you will need to host on a web server. The Warden dashboard is an application written in Symfony and is freely available on github.

At present only a Drupal integration exists but work is underway to produce a pluggable system which will allow new modules to be created for Wordpress and pure Symfony sites. Others may then wish to contribute additions for their own needs, for example by providing different kinds of reports for the sites.

Warden Dashboard

After correctly configuring the Warden Symfony application you will be presented with the Warden Dashboard. This lists all the sites in your estate with high level details of each. Sites requiring a security update are highlighted as red, sites with module updates which are not security are yellow and sites with no problems are white.

Drupal modules listing screen

The Drupal plugin for the Warden application provides a modules listing screen. This lists all Drupal modules installed across all you estate and allows you to see which Drupal websites have and do not have a particular module installed. This helps when you need to know how many sites need to be updated as a result of a module change or knowing how many of your Drupal sites might be missing a best practice module.

Security

The Warden application uses OpenSSL to encyrpt data which is sent between it and the Drupal website. The PHP OpenSSL Cryptography extension is required for both Warden and the Drupal sites it will take data from. You can also IP restrict which servers can request data from your Drupal websites in the module configuration.

In normal operation the Warden dashboard will poll the sites periodically to request the sites data be refreshed. You can alternatively configure it so that the sites push the data to the Warden dashboard. In either configuration, the site will only send data to the configured dashboard and not to the site making the request for data.

It is also recommended that you use a signed SSL certificate on your Drupal websites and your Warden dashboard.

Where to get Warden

You can download the Warden central applications from GitHub here: https://github.com/teamdeeson/warden 

The Drupal module is available on drupal.org here: https://www.drupal.org/project/warden

What next?

We welcome contributions to the Drupal module or the Symfony application codebase, let us know what you think! 

If you are intersted in integrating Warden into other web tools then you'll need a copy of the PHP API which is available here: https://github.com/teamdeeson/wardenapi  

Categories: Elsewhere

Nacho Digital: Drupal Planet (RSS spanish & portugues)

Mon, 01/02/2016 - 22:31
If we have enough movemente and content we will have drupal.org/planeta in spanish and portugues

Since Drupalcamp chile I'm pushing with a bunch of nice people an space within drupal.org to share content in spanish and portugues.

We are almost ready, we just need to generate enough movement to make it public. Right now it exists, but it is not publicly available: drupal.org/planeta.

The main purpose of this post was to share how to do it. So I will invite you to read the spanish version to read the steps and details. I see no reason to share them in english at this time. If there is interest I can do a full translation. Just leave a coment with your request.

Cheers!

Categories: Elsewhere

Commercial Progression: The Future of Decoupled Drupal & other Bold 2016 Predictions (E13)

Mon, 01/02/2016 - 22:09

Commercial Progression presents Hooked on Drupal, “Episode 13: Future Predictions of Drupal, Technology, and Powerball Winners".  That's right, you heard it here folks, someone has already won the Powerball. Ok, so maybe that is old news... but what about the future of Decoupled Drupal website architecture, static site generators, and the next revolution in IOT technology? To receive these clairvoyant predictions along with many important highlights from 2015, you will need to tune into the future with our latest podcast. 

Hooked on Drupal Content Team

BRAD CZERNIAK - Developer

CHRIS KELLER - Developer

HILLARY LEWANDOWSKI - Developer

SHANE SEVO - Host

 Podcast Subscription

Tags:  podcast, Hooked on Drupal, Decoupled Drupal, Planet Drupal, IOT, Static Sites
Categories: Elsewhere

roomify.us: Booking and Availability Management Tools Beta Release and Roadmap

Mon, 01/02/2016 - 18:11
Our Booking and Availability Management Tools have reached beta release stage. This means that we have covered all the main features for the 1.0 version of the library and we will now focus on bug fixes and UI improvements as well as developing documentation and a more comprehensive test suite. The BAT PHP library is now version 1.0.0-beta1 while the Drupal module is at 7.x-1.0-beta1.
Categories: Elsewhere

Cheeky Monkey Media: How to Import with Feeds using JSONPath.

Mon, 01/02/2016 - 17:52

In order to import some json data, you first need theses modules installed and enabled.

Categories: Elsewhere

Cheppers blog: Drupal Genesis

Mon, 01/02/2016 - 17:28

Five years after the launch of Drupal 7, we were terribly excited about the launch of Drupal 8 set for November 19 2015. As the release date had been announced a few weeks before, we wanted to join the initiative of the worldwide Drupal 8 celebration (#Celebr8D8 - celebratedrupal8.com) and create a unique surprise for the Drupal community.

Categories: Elsewhere

xjm: Emacs keybindings, PhpStorm, Mac OS, and the random characters I almost add to Drupal

Mon, 01/02/2016 - 15:41
Emacs keybindings, PhpStorm, Mac OS, and the random characters I almost add to Drupal xjm Mon, 02/01/2016 - 14:41
Categories: Elsewhere

myDropWizard.com: Why we don't provide a "security updates only" plan for Drupal 6 Long-Term Support

Mon, 01/02/2016 - 15:14

A couple of times now, we've gotten a reaction like this to our Drupal 6 Long-Term Support offering:

Your cheapest plan ($125/mo) is too expensive. We just want to keep getting security updates for Drupal 6, but don't want any support and maintenance. Can you provide a "security updates only" plan for us?

This is something we thought long and hard about...

A cheaper plan would appeal to a larger group of users, and allow us to work with people with smaller budgets. These are definitely things we want! We'd like to be able to help as many people as possible, and NOT only big enterprise companies with massive budgets (they can already get all the help they need).

But in the end, we decided that we'd be doing our customers a disservice by trying to reduce our offer any further.

Read more to find out why!

Categories: Elsewhere

Kodamera Screencast: How to install modules and themes

Mon, 01/02/2016 - 14:50

Drupal is a great CMS (Content Management System), but everything isn't included in the core installation package of Drupal. Luckily there are thousands of modules (another word for plugin) made just for this easy way to build a website that fits your needs. When this screencast was recorded there were over 32000 modules available, and though it's just over two months since version 8 of Drupal was released there are already over 1000 modules for this version.

We continue our thorough journey alongside Drupal and explain two ways of adding modules and themes to your Drupal installation. Never install modules or themes from some place other than drupal.org. Other publishing systems have had and are having problems with plugins being available from here and there, and on more than one occasion there have been malicious code in these plugins. 

I show you the two easiest ways as a newcomer to Drupal to add functionality via new modules and we touch subjects as Update Manager, security and security updates and the commenting module Disqus (which we use here on screencast.kodamera.se).

 


Read more
Categories: Elsewhere

Valuebound: Building Configuration Form in Drupal 8

Mon, 01/02/2016 - 14:15

The primary mechanism for collecting input from users is Form, without them Drupal wouldn't be so much useful. This is also one of the first things Developer should learn when they start development using Drupal. Forms are fundamental to creating Drupal modules, whether asking someone to leave a comment or Administrator has option to turn the module configuration ON/OFF.

The configuration system / state system has replaced the variable system in D8. There is no variable table and no more variable_get() / variable_set() /  variable_del() calls. Configuration is stored in the database and synced with YML files on the disk for deployment purposes.

The $config object handles CRUD (Create/Read/Update/Delete) for YML files, so you simply use ::get(), ::set(), and ::save()…

Categories: Elsewhere

Chris Hall on Drupal 8: Twig extends and a D8 Twig Block base theme

Mon, 01/02/2016 - 13:55
Twig extends and a D8 Twig Block base theme chrishu Mon, 02/01/2016 - 12:55 Introduction

Twig Blocks and the extend functionality can be used to stop needless repetition.

I have posted before about Twig Blocks and Drupal and experimented a little with a theme on Github used as the base theme for this site, I also raised an issue for consideration of Twig blocks to be added to Core templates as I felt that without them D8 theming had slightly missed a trick (admittedly far too close to the release).

Fortunately the late addition of the Stable theme to D8 makes it much easier to experiment with alternative approaches to theming plus allows Core mark-up to evolve much faster than the Drupal release cycle (without arbitrarily breaking existing themes).

Copy of Stable with Twig blocks

Stable is/was a copy of the Drupal core templates that will not change, it is the default base theme for every theme that does not define a specific base theme unless base theme: false is set in the info file (which would leave you vulnerable to any changes in core templates, CSS and JS over the D8 life-cycle).

I have made a copy of Stable called Blocky and marked up some of the templates with Twig Blocks, which doesn't change the functionality of the theme at all but does allow more selective override of templates directly, after inspecting what blocks are available. For a simple example an alternative node template can just override the mark-up of the title leaving the rest of the parent template mark-up alone (no need to slavishly copy all the bits you don't want to change).

{% extends "@blocky/content/node.twig.html" %} {% block node_title %} {{ title_prefix }} {% if not page %} <h3{{ title_attributes }}> <a href="{{ url }}" rel="bookmark">{{ label }}</a> </h3> {% endif %} {{ title_suffix }} {% endblock node_title %}

Of course Blocky could always just be used as the basis of another copy, providing a more customised theme with the ability to use Twig extends (do read the official documentation for extends if you haven't used it before). You may have many variations of node templates, any change to boilerplate mark-up that is not generally overridden in child templates only has to be modified once in the parent template that all the others are extending.

Extends is not just for Twig Blocks

Extends allows for adding variables via the child that are then available in the parent template. A child template can affect the parent template or provide new variables to the parent opening up new possibilities for Drupal 8 theming strategies even without using Twig Blocks.

Classy already does this in one or two places now, for example the meat of the Classy field--field-text.htm.twig is as follows:

{% extends "field.html.twig" %} {% set attributes = attributes.addClass('clearfix', 'text-formatted') %}

In this case a more specific template is adding a class to it's general parent template without having to repeat mark-up. Is your brain starting to whir? Potential new approaches to theming? Excited?

Taking it further

Unfortunately I have not found a client project that is suitable for Drupal 8 yet so experimentation is in free-time. I am hoping to move another blog to Sculpin and then work on a better theme for that and this site that share as much as possible.

Even with Twig Blocks Drupal still has a fairly linear approach to building the front-end, so approaches sometimes used by other frameworks with Twig or Twig like template syntax will need a bit more head-scratching. For example a common approach used elsewhere would use parent layout templates that are never directly rendered, just extended. These layout templates may well have empty Twig Blocks (the main events) that are filled in further down the chain. A Drupally equivalent might be an html.html.twig template that has an empty 'page' block rather than kicking off the rendering of the page by outputting $page. This template could then be extended by multiple variations of page. Note: this approach will not currently work in Drupal but 'should' be possible digging around in pre-processing etc. (well it feels like it should).

Twig has some other tricks like embed and the simpler include and these along with extends can utilise conditionals and variables.... OMG the potential approaches to theming Drupal have increased exponentially!!! :).

 

Add new comment
Categories: Elsewhere

Valuebound: Drupal 8 installation in Windows with XAMPP

Mon, 01/02/2016 - 08:04

Installation of Drupal requires a Web server. We will be employing XAMPP package for the same purpose. XAMPP is a free and open source web server solution stack. It stands for (X-cross platform), (A-Apache HTTP Server), (M-MariaDB), (P-PHP), (P-Perl).  XAMPP is hassle free and is…

Categories: Elsewhere

hussainweb.me: Drupal Global Sprint Weekend 2016 in Bangalore

Mon, 01/02/2016 - 05:50
This year’s Drupal Global Sprint Weekend 2016 was held on January 30th and 31st throughout the world. We conduct a Drupal meetup every last Saturday in a month in Bangalore and this time, we just organized the sprint instead.
Categories: Elsewhere

Iztok Smolic: Drush 8 on Mac OSX and MAMP

Sun, 31/01/2016 - 20:23

Here is a complete guide to get your drush working OS X El Capitan. 1) Download latest stable release using the code below or browse to github.com/drush-ops/drush/releases. wget http://files.drush.org/drush.phar (Or use our upcoming release: wget http://files.drush.org/drush-unstable.phar) 2) Test your install. php drush.phar core-status 3) Rename to `drush` instead of `php drush.phar`. Destination can be anywhere […]

The post Drush 8 on Mac OSX and MAMP appeared first on Iztok.

Categories: Elsewhere

Drupal core announcements: Drupal 8 and 7 core release window on Wednesday, February 03, 2016

Sun, 31/01/2016 - 17:53
Start:  2016-02-24 00:00 - 23:30 UTC Organizers:  xjm catch David_Rothstein Event type:  Online meeting (eg. IRC meeting)

The monthly core patch (bug fix) release window is this Wednesday, February 03. Drupal 8.0.3 and 7.42 will be released with fixes for Drupal 8 and 7. There will be no Drupal 6 bugfix release this month.

To ensure a reliable release window for the patch release, there will be a Drupal 8.0.x commit freeze from 00:00 to 23:30 UTC on Wednesday, February 03. Now is a good time to update your development/staging servers to the latest 8.0.x-dev or 7.x-dev code and help us catch any regressions in advance. If you do find any regressions, please report them in the issue queue. Thanks!

To see all of the latest changes that will be included in the releases, see the 8.0.x commit log and 7.x commit log.

Other upcoming core release windows after this week include:

  • Wednesday, February 24 (security release window)
  • Wednesday, March 02 (patch release window)
  • Wednesday, April 20 (scheduled minor release)

For more information on Drupal core release windows, see the documentation on release timing and security releases, as well as the Drupal core release cycle overview.

Categories: Elsewhere

Pages