It’s no secret that online harassment is a huge and growing problem for people trying to use the Internet. A 2014 Pew Research Center study found that 73% of adult Internet users in the United States have observed someone being harassed online and 40% have personally experienced harassment themselves.
Drupal 8 landing page
With more than 200 new features and improvements, the upcoming release of the world’s leading open source web content management platform will win you over. Drupal 8 will set a new standard for ease of use, while offering countless new ways to tailor and deploy your content to the web.
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.
Pursuant to the discussion at [policy] Require PHP 5.5, the minimum PHP version of Drupal 8 has been raised to 5.5.9, and this change will be included in the next Drupal 8 beta (8.0.0-beta13).
Blocked by #1867192: Testbots need to run on php 5.3.10, 5.4, 5.5, 5.6 and 7 It is anticipated that Drupal 8 will come out in 2015. PHP 5.5, released June 20 2013, is now 2 years old. PHP 5.4 (Drupal 8’s current minimum requirement) becomes end of life 14 September 2015.
Drupal users around the world know Aaron Winborn (aaron), a long-time community member who made countless contributions to the project and to the people who use it. From building the Media module to helping organize NYC Camp, Aaron had a massive impact on our community and our project.
Security advisories for third-party projects that are not part of Drupal core – this includes all modules, themes, and installation profiles that have been contributed by a community member. These posts by the Drupal security team are also sent to the security announcements e-mail list.
This Public Service Announcement is a follow up to SA-CORE-2014-005 – Drupal core – SQL injection. This is not an announcement of a new vulnerability in Drupal. Automated attacks began compromising Drupal 7 websites that were not patched or updated to Drupal 7.32 within hours of the announcement of SA-CORE-2014-005 – Drupal core – SQL injection.
Advisory ID: DRUPAL-SA-CORE-2014-005 Project: Drupal core Version: 7.x Date: 2014-Oct-15 Security risk: 20/25 ( Highly Critical) AC:Basic/A:None/CI:All/II:All/E:Theoretical/TD:All Vulnerability: SQL Injection
Description Drupal 6 and Drupal 7 include an XML-RPC endpoint which is publicly available (xmlrpc.php). The PHP XML parser used by this XML-RPC endpoint is vulnerable to an XML entity expansion attack and other related XML payload attacks which can cause CPU and memory exhaustion and the site’s database to reach the maximum number of open connections.
Derived from #1033818: Move xmlrpc includes into xmlrpc.module, this issue is to track the removal of the XML-RPC API in Drupal 8.0 Milestones to remove something from core should include:
I’m fairly new to Drupal-and development in general-but I’ve found a desire to participate in the community and seek some guidance in the process. I’ve decided to fork a project on Github called Varying-Vagrant-Vagrants, located here, with something I’m calling, not ironically, Varying-Drupal-Vagrants, located at my repo here.