You know when Drupal 8 will be released or would like to join the guessing game? Simply sign up with your Twitter account or e-mail address and enter a date. After your guess you can see which date the other registered users are betting on and which ones are among the hot favorites. It's done when it's done The competition ends when the Drupal 8 release is publicly announced. The older your tip, the higher your chance of winning! 2649bugs 169participants 145predictions 93tweets There are shiny prizes We'll raffle two DrupalCon tickets.
This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release). There will be no bug fix release on this date; the next window for a Drupal core bug fix release is Wednesday, January 7.
@alexpott premiered Config installer an install profile that takes over the Drupal installer and allows sites to be created from existing configuration. This opens the door for some interesting possibilities moving forward. We upgraded Drupal core to use Symfony 2.6 stable. Symfony 2.6 includes over 100 new features and enhancements. For full details see the release announcement. Following on from SA-CORE-2006 we removed mixed SSL support from core, focusing on security by default. We updated CKEditor library to 4.4.6, which included an important security fix.
The main event should occur when saving a new piece of content. You will then create at least 3 actions. This first will be to create a new Facebook publication entity. The second populates the entity with some value from your content type (like a link or text summary). The last publishes it. You can see below for my settings, although for a more in depth look I suggest you look at this video which walks through everything in more detail.
Drupal 8 ready: drupal_ti supports both Drupal 7 and 8 modules. Use DRUPAL_TI_ENVIRONMENT="drupal-8" for your Drupal 8 modules. Tested: drupal_ti tests its own code base for both Drupal 7 and Drupal 8 modules. Modular architecture: drupal_ti has so called 'runners' and you can combine either e.g. "phpunit simpletest" or run them as separate workers by specifying a matrix. Environment aware: drupal_ti has a file for each environment, which makes the code generic for both Drupal 7 and 8.
This problem was caused by the initial decision of limiting each search index to a single entity (or other) type – since normal searches are always executed on a single index, a search across multiple types cannot be created this way. While other, maybe better-working workarounds in Drupal 7 would be possible, this is solved completely in Drupal 8 where this restriction doesn’t exist anymore.
the PSA also resulted in a large volume of press coverage – in fact much more coverage than the original disclosure of the vulnerability on October 15th. Not surprisingly, the general tone of the press coverage was quite negative. Unfortunately, some of the coverage was also inaccurate which we’d like to address here as well as provide additional context regarding our security processes. While we don’t know the total number of Drupal sites affected, the number is not near 12 million as stated in several publications.
Every project, from small brochure sites to large webapps all have a core set of intake requirements that need to be determined before development work can begin. Designed as the deliverable for these core requirements, Intake Center aims to make it easy to ensure these deliverables for Content Strategy are complete and available before development starts.
Packagist is a Composer package repository. It lets you find packages and lets Composer know where to get the code from. You can use Composer to manage your project or libraries' dependencies - read more about it on the Composer website.
This project not merely creates confusion for users who won't know whether to use drush or console but it'll double the workload for contrib authors who you are now forcing to integrate with both. Core deliberate has removed extensibility for the sake of contrib maintainers not going nuts.