We now present the first release candidate for Drupal 8.0.0! Drupal 8 includes a tremendous number of new features and improvements for both users and developers.
We revamped Drupal's user interface; added WYSIWYG and in-place editing; significantly improved mobile support; added and improved key contributed modules including Views, Date, and Entity Reference; introduced a new object-oriented backend leveraging Symfony components; revamped configuration management; improved multilingual support; and added hundreds of other improvements. Drupal 8.0.0-rc1 is the collective work of over 3,200 core contributors. Read more about what's new in Drupal 8.0.x.
The first release candidate provides a great opportunity to begin developing with Drupal 8, especially for:
- New sites.
- Sites that rely mainly on the expanded functionality provided by Drupal 8 core alone.
- Projects that will take months of development time.
- Sites for which Drupal 8's benefits outweigh the effort needed to port (or work around) contributed modules that do not yet have Drupal 8 versions.
Drupal 8 itself is very functional straight out of the box -- many of the top Drupal 7 modules are now included in core, and several features have been made more flexible to avoid the need to install many other modules. Evaluate your needs, and you may easily find that everything you need for a project is already included in Drupal 8 core. Check out our slides about Drupal 8 to learn about the changes.Updating existing sites #
The new version also includes a revamped Migrate module to update existing Drupal 6 and 7 sites to Drupal 8 directly. The migration feature is currently marked "experimental," meaning it is not yet fully supported and we are still working to improve it. For this reason, the Drupal 8 release candidate does not yet provide a user interface for migrations. Use the Migrate Plus and Migrate Upgrade modules to test migrations now, or read more about Migrate in core.Contributed modules and themes #
There are a number of modules already ported to Drupal 8 as well as themes already being developed. We set up the contrib tracker project to make it easier to track the status of the ports of contributed modules.
DrupalCon Barcelona Drupal 8 sprint photo by Pedro Lozano (under the CC BY 2.0 license) Porting modules and themes to Drupal 8 #
If you have not done so already, now is the time to ensure that your modules and themes will work with the new version. While there are many changes in Drupal 8, we wanted to make it as easy as possible to get started porting modules. We suggest you use Drupal Module Upgrader to run a first pass of code upgrades. Some things will be automatically upgraded while others will get a @todo comment or will be left untouched.
To help you learn and apply the new APIs, the api.drupal.org site has overviews and short examples of all major Drupal 8 APIs. The Drupal.org handbooks have in-depth guides with more background information on each API as well. We also have a complete list of all API changes to Drupal 8, spanning the 4.5 years of Drupal 8's development.
Instead of using our own home-brewed templating system from Drupal 7 and earlier, Drupal 8 uses the Twig templating engine. Many of the concepts from previous versions of Drupal still apply with Twig. We are working on a guide for you to help update your themes. Also check out the Drupal 8 theming documentation for more information.
Be sure to file any core bugs that you may find while updating your module or theme.Translating Drupal 8 #
The interface strings are officially frozen now. Only error corrections, removals or additions of whole strings, and fixes required for critical issues may be made to the interface text from this point forward. This is the best time to translate Drupal 8, so your translations will be available when the final version is released. The installer now comes with automated translation downloads, so whatever you translate now will be useful for all Drupal 8 installs. Localize.drupal.org has a summary page about core translation status in all the supported languages with a step-by-step guide in the sidebar to help you contribute.Documentation, book, and video authors #
The user interfaces, interactions, and "look and feel" of Drupal 8.0.0 are now frozen and will only be changed if required for critical bug fixes. If you previously put your documentation, instruction video, or book project on hold, now is the time to pick it up again. Now is also the time to update documentation on Drupal.org and to get documentation fixes into Drupal 8, so the explanations are correct. Thanks for your contributions!
Be aware that Drupal 8 will employ semantic versioning, with new "minor" releases (backwards-compatible with API additions and new features) approximately every six months. So strings, user interfaces, and other visual aspects of Drupal will be improved throughout the entire Drupal 8 process, which may require subsequent updates to these materials.Contributing to Drupal 8 core #
During the release candidate phase, only critical fixes and documentation improvements will be committed to Drupal 8 core (plus certain non-disruptive "rc target" changes at core committer discretion). Other issues that have been reviewed and tested by the community may remain uncommitted until after 8.0.0 to ensure that critical bugs can be fixed quickly without risking regressions. Read more about the allowed changes during the RC phase.When will Drupal 8.0.0 be released? #
We will schedule an official release date for 8.0.0 when we are confident that the rate and nature of incoming critical bugs has slowed enough to ensure a stable release. Until then, release candidates of Drupal 8 will be released twice a month concurrently with the Drupal 6 and 7 release windows.Known issues #
We are confident that our code is stable enough for wider testing by site owners, developers, and end users. There are however still known issues with Drupal 8.0.x, including major bugs. Help resolve these issues by testing Drupal 8 and searching for existing bug reports and adding more information to help resolve those bugs. If your suspected bug hasn't been reported yet, submit a bug report.
There is a known issue with response cache headers sometimes exceeding hosting configuration limits that may cause some pages to not be viewable on some hosting providers. If you run into this, see that issue and its related issues for details.Handling security issues #
Starting now, any security issues discovered for Drupal 8 should be kept confidential and reported using the Report a security vulnerability link on the Drupal project page in order to protect existing sites. Through December 31, 2015, the Drupal 8 security bounty is also still active, so you can get paid for finding security issues and reporting them in our private tracker! See the security team page for more information on Drupal security.Talk about the release candidate! #
We suggest the #drupal8rc hashtag for Twitter, Facebook, etc. posts. To mention and find conversations about work already made with Drupal 8, use #madewithd8. We can't wait to see what you make with Drupal 8!Front page news: Drupal NewsDrupal version: Drupal 8.x
Docebo expands operations in Asia Pacific region via partnership with Bloom Training and Recruitment
The New Zealand-based training and recruitment specialist, Bloom Training and Recruitment, is partnering with Docebo, producers of the Software-as-a-Service (SaaS) Enterprise learning management system (LMS).
New research confirms that online marketers and website owners need to follow a separate strategy to help their pages rank higher in mobile phone searches on Google.
Zylpha's New Bundling Functionality Slashes The Time Taken To Prepare Electronic Document Bundles For Lawyers
Acquia has announced that they have closed a $55 million equity financing round through the help of Centerview Capital Technology. Centerview Capital specializes in partnering with the management teams of midsize companies they see as "high potential" for growth. Centerview Capital Technology led the financing round, with support from existing investors including New Enterprise Associates and Split Rock Partners. This funding will help Acquia scale its global operations, sales and marketing as well as the development of its solutions for building, delivering, and optimizing digital experiences.
The Internet of Things (IoT) is the idea to expand the existing Internet infrastructure (such as IP or UDP/TCP) to devices in order to facilitate communication between the devices themselves and between the devices and humans.The underlying functionality of IoT allows objects to be controlled and sensed remotely across an existing network infrastructure. Hence, it creates tremendous opportunities for a direct integration between our physical world and the computer-based systems.
What makes the traditional faxing process even more cumbersome and insecure for many provider offices is that often, the information that is sent via fax becomes electronic, when staff enters the information into a database or electronic health record by hand or via scanning, thereby changing it to information that must be secured under the HIPAA electronic PHI rules. All of this, in addition to the cumbersome and time intensive process of using a traditional fax machine, has many providers wondering how they can send PHI and still maintain HIPAA compliance.
One solution to the faxing-HIPAA compliance dilemma is a secure cloud faxing solution. These solutions give providers more flexibility when sending faxes, while also increasing the overall security of the PHI they contain.
Hippo and Kanban Solutions invite Forrester's Ted Schadler to speak on Content-rich Customer Experiences
While the Agility CMS has been in Beta for much of 2015, the Production release will be rolling out to Agility's clients and their sites this Fall. While gradual improvements were made in the CMS, probably the biggest change for Agility Inc. was in late 2013 with the appointment of their new CEO, Jonathan Voigt. When Jon was appointed CEO he promised a refocused vision for Agility that would provide better products and improved services for Agility's paying customers. This autumn, Agility fulfills that promise as it rolls out a significant rebuild and redesign of the content management system's interface. Besides the interface improvements, the new version of Agility CMS also introduces a new Dashboard feature as well as significant improvements in software performance and task workflow.
Agility and their clients have a lot riding on this new release. Let's take a sneak peek at what the new CMS has to offer.
The trademark team manages and defends Joomla-related trademarks and licensing on behalf of the the Joomla Community. We want to make sure the world respects the policies and regulations we have around the use of the Joomla! name and brand mark.
This comes with a lot of work. We need active team members that will pick up on tasks such as building our own trademark subdomain on the Joomla!-website, finetuning processes as we want to make it easy for applicants to apply online and follow their submission. Furthermore we need license administrators to take in the requests and give follow up. In time, licenses have to be checked randomly and regularly on proper use.
Are you interested in taking part in our team? Or do you have suggestions on who would be interested in joining? Please let us know by writing a short (introduction) e-mail to our team-leader, Marco Richter (firstname.lastname@example.org).
Most roles only require less than a couple of hours per week. No special experience is necessary. As a team we will manage. We will teach you what you need to know.
We welcome your response!
You can expect a reply within two business-days.
The Docebo Software-as-a-Service (SaaS) Enterprise learning management system (LMS) is playing a key part in helping the cloud-based accounting software producer, FreshBooks, to keep its business growing.
We are excited to announce some big changes to the Drupal.org Marketplace. In Dries’ Amsterdam Keynote, he made a compelling case for showing the contributions of organizations that are helping build Drupal. By highlighting organizations that give their employees time to give back, we make it possible for more people to give time to making the project better.
In March, we took steps to begin collecting this information by allowing individuals that were contributing in the issue queues to attribute their contributions to organization that they are employed by or customers that funded the work. When a maintainer of a project (module, theme, distribution or Drupal Core) closes an issue as fixed, they have an opportunity to pass on credit to the individuals who helped contribute to fixing the issue—and not just code contributions, but any kind of feedback, review, designs, etc.
We called this system issue credits and it has been a huge success. We now show the last 90 days of issue credits awarded to an individual or organization on their profile.
Today, after months of collecting this data, we are taking how we highlight contributing organizations to a new level.
With this launch, we are removing the distinction of "featured service providers" versus "all service providers". By using data about these organizations contributions, we can provide a single list of all organizations ordered by their contributions.
For now, we are using issue credits as the primary sort. The secondary sort highlights organizations that are giving back by supporting Drupal.org through the supporting partner program or organization membership. Soon, we plan to incorporate case studies submitted, DrupalCon sponsorships, and camp sponsorships to help make a more complete picture of how organizations are contributing to our community.
Give it a look and give us your feedback.Front page news: Drupal News
On an early August morning, users of Amazon Web Services (AWS) woke up to some rather startling and frightening news. Error messages indicated that services were down both for the Simple Storage Service (S3) and Elastic Compute Cloud (EC2) solutions that Amazon provides. This severe outage lasted well into the afternoon and early evening before Amazon finally notified its customers that the problems had been corrected and services restored. While the outage lasted less than a day, it sparked a new discussion about what caused it and, just as important, how to prevent such outages from occurring in the future. For some, the solution to the problem was clear: decentralized cloud computing. While some have rejected this idea, proponents say the benefits of a decentralized cloud network are worth pursuing, especially when it comes to future outages.
Over the years, I have promoted a lot of conferences for marketers, businesses, and content providers. For the most part these conferences blend in together so much that it is difficult to distinguish one from the other. However, not all conferences are forgotten with time. There are an elite few that stand out from the pack year after year. One of those is the Gilbane Conference.
The Gilbane Conference is geared for marketers, IT, and business managers that wish to "integrate content strategies and computing technologies to produce superior customer experiences for all stakeholders".
This year, Gilbane Conference 2015 is being held in Boston, Massachusetts from December 1st through the 3rd. This year, the conference will focus on how best to integrate your content, data, and software to improve the multichannel digital customer experience. Whether you are just getting started with managing multichannel content, need to improve the consistency of the web and mobile discovery experience, or are ready to integrate with an ecommerce, content marketing, business intelligence or other marketing or data management platform, you will want to attend this conference.
The Structure Team is happy to announce the results of the elections for the Transition Team. In total 24 Leadership Members (of 27) elected 6 community members for the transition team. We like to introduce them in a random order:TJ Baker (USA)
TJ is located in Visalia, Califonia (USA) and has a long history of working collaboratively in the Joomla Project. He is known as a great team player, making sure all voices are heard, and collaborative decisions are made. According to TJ’s own words he owes a great debt to the many volunteers, past and present, who have made Joomla what it is today. Serving on this team would be a small gesture to repay part of that debt.Ian MacMillan (UK)
Ian is located in London (UK) and has been a change management specialist for decades. He has dealt with some very difficult transitions in the past and has always managed to get even the most dissolute teams to find cohesion and a clear path to move forward on. He has no history as a Joomla community member but understands the importance of making this evolutionary change. Offering his experience of delivering difficult change, for which being outside of the community, and thus not part of the natural tensions of this significant change, is an additional benefit.Ken Crowder (USA)
Ken is located in Omaha (USA) and has been a long standing contributing member of the Joomla! Community. He is a moderator on the Joomla forum since 2006 and has held various positions including time on the Leadership team. He likes to think of himself as a level headed person with the ability to look at things objectively and not emotionally. According to him it is crucial that the transition team be made up of individuals that are focused on doing what is best for the project and not made up of individuals that make decisions based on friends or favors.Helvecio da Silva (Brazil)
Helvecio is located in Rio de Janeiro (Brazil) and is known for his contributions as an illustrator and translator. His goal is to promote Joomla within less privileged communities in Rio de Janeiro, Brazil. According to him the project showed him new horizons in his career and improved the way he acts within different communities he is part of. His motivation comes from a quote of Ghandi:“You must be the change you wish to see in the world.” Being part of the Transition Team is one more step into being this change.Stefania Gaianigo (Italy)
Stefania is located in Garda (Italy) and gave her contributions translating the CMS and the documentation by coordinating the Italian Joomla Translation Team since the birth of Joomla. Currently she is a member of the Joomla Translation Coordination Team and an administrator of Joomla.it, where she daily gives voluntary support to the users of the italian community.Jon Neubauer (USA)
Jon is located in Charlotte, North Carolina (USA) and has been involved in various teams within the Joomla Community over the years. Currently he is the lead organizer of the Joomla World Conference. He firmly believes that the opportunities offered to us by this transition period is one of the few times where we have the chance to "make or break" Joomla. He is motivated to make sure that, in this new structure we are able to keep the open, nimble, "all together" spirit that has defined most of Joomla's history and work together towards another decade of growth.
The Transition Team will be completed by representatives of each leadership team:
- Ryan Ozimek (the board)
- George Wilson (PLT)
- Guillermo Bravo (CLT)
We would like to thank all the people that participated in the elections as well as Dianne Henning and Jacques Rentzke who verified all votes casted and made sure the procedure was followed.
- Between the 20th of September and the 1st of October the Transition Team has an initial handover meeting with the Structure team
- On the 1st of October the new Transition Team will officially take over from the Structure Team and implement the new structure.
Forum discussion thread: http://forum.joomla.org/viewtopic.php?f=704&t=894869
Docebo, producer of the Software-as-a-Service (SaaS) Enterprise learning management system (LMS), is joining forces with the globally-known business research organization, Aberdeen Group, to reveal the changing face of corporate learning.
Users of the eXact learning solutions’ suite of digital learning content management business solutions met in Rome recently. There, they discussed the latest product features and gained an insight into forthcoming advances in the eXact learning solutions’ suite of products: eXact learning LCMS, eXact learning Packager and eXact learning Mobile.
DrupalCI is the next generation testing infrastructure for Drupal. After years of development, DrupalCI has been rolled out for testing Drupal 8 Core and Contrib projects - and will soon be taking over testing Drupal 7 Core and Contrib as well and for Drupal 6 for the duration of its long term support window.
But we need your help!
At this time, DrupalCI is running in parallel with the existing PIFT/PIFR testing architecture. Before we retire the old testing infrastructure we want to ensure that there are no feature regressions in the new DrupalCI system, and that core and contrib developers have had time to learn the new testing architecture and try it out thoroughly.
If you are a maintainer of a contrib module with testing enabled, we will enable DrupalCI testing for your project. At this time, DrupalCI supports testing in D8 Core and Contrib, but D7 and D6 testing will be enabled soon. If you see that DrupalCI testing has been enabled for your project, please provide your feedback in the issue linked below.
To learn more about how to use DrupalCI for automated testing of your project on Drupal.org, please consult this documentation page.How can you provide feedback?
We are collecting feedback on the new testing architecture in this issue: #2534132 - Disable Legacy Testbots and use drupalCI as our testing infrastructure. Please focus your feedback on:
- Feature regressions from current testbots
- Unexpected test failures
- User interface issues
- Test result parsing and display
Though DrupalCI is a more flexible and extensible testing architecture, we are not collecting additional feature requests at this time.
If you are a module maintainer, and you are a satisfied that the new DrupalCI tests are meeting your testing needs, you can return to the Automated Testing tab for your project and choose to disable PIFT/PIFR testing, by deleting the specific releases you no longer need tested in the old system:
Learn how to add automated testing to your project…
If you would like to add automated testing to your projects on Drupal.org you can learn more about writing tests with this tutorial.Front page news: Drupal NewsDrupal version: Drupal 6.xDrupal 7.xDrupal 8.x
WordPress 4.3.1 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately.
This release addresses three issues, including two cross-site scripting vulnerabilities and a potential privilege escalation.
- WordPress versions 4.3 and earlier are vulnerable to a cross-site scripting vulnerability when processing shortcode tags (CVE-2015-5714). Reported by Shahar Tal and Netanel Rubin of Check Point.
- A separate cross-site scripting vulnerability was found in the user list table. Reported by Ben Bidner of the WordPress security team.
- Finally, in certain cases, users without proper permissions could publish private posts and make them sticky (CVE-2015-5715). Reported by Shahar Tal and Netanel Rubin of Check Point.
Our thanks to those who have practiced responsible disclosure of security issues.
Download WordPress 4.3.1 or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.3.1.
Thanks to everyone who contributed to 4.3.1:
Adam Silverstein, Andrea Fercia, Andrew Ozz, Boone Gorges, Brandon Kraft, chriscct7, Daisuke Takahashi, Dion Hulse, Dominik Schilling, Drew Jaynes, dustinbolton, Gary Pendergast, hauvong, James Huff, Jeremy Felt, jobst, Marin Atanasov, Nick Halsey, nikeo, Nikolay Bachiyski, Pascal Birchler, Paul Ryan, Peter Wilson, Robert Chapin, Samuel Wood, Scott Taylor, Sergey Biryukov, tmatsuur, Tracy Levesque, Umesh Nevase, vortfu, welcher, Weston Ruter