Large-scale Drupal sites often maintain a separate "staging" server to test and preview changes before they're released to the public. If you're working on a smaller project, though, it can be useful to give a few trusted testers access to a few pages of the site. In those situations, the Protected Pages module might be just what you need.
Drupal 8 Alpha 6 is out and it has a migrate module in there! It even has a few complete migrations: variables to the configuration files owned by system module. Since the last report the configuration of process has changed significantly, this is now documented in the handbook. We have two patches in the core queue, one potpourri of small fixes and one to split migrate into migrate and migrate_drupal, the latter holding the Drupal 6->Drupal 8 and Drupal 7->Drupal 8 migration. I have a third almost ready, this will be our first config entity migration, namely filter formats. This is actually working but the test is currently not doing much -- once this is fleshed out a bit, I will submit this as well. This patch will introduce most generic process plugins we planned to write and so the handbook pages for all the source plugins needed to be written before it could be submitted. A lot of code has been written for a fourth, this will be all the variables to configuration files. There's rapid progress, Mike Ryan now participates on a daily basis which means a lot of domain knowledge has been added to the team. marvil07 is working on porting the CCK fields code from migrate_d2d -- yes, the battle plan is that you will be able to migrate CCK fielded nodes to Drupal 8 straight. bdone and Mike is working on expanding the test coverage on two big classes which were straight ported from Drupal 7. YesCT is fixing our doxygen (I worked on this as well because the terminology was very confusing, hopefully now it's less so). My next task is to go over the existing hook_update_6xxx functions and see whether there's special logic that won't be covered by simple entity-to-entity migrations and create issues for them. fastangel have written the bulk of the fourth patch, I fully expect he will pick a lot of these issues, with the rest of the team piling on them once their work is done. With a little luck and perseverance the Drupal 6 -> Drupal 8 migration will be done by the Drupal birthday (January 15).
In the longer term, we will need to do Drupal 7 to Drupal 8 and I will need extra helping hands with multilingual issues. Ryan Weal already voluntereed to help, but I am sure we can use a few more so if you know i18n+migrate both, please don't hesitate to contact me.
Part of the Drupalize.Me team, Addison Berry, Joe Shindelar, Kyle Hofmeyer, and Joe Fender, gets on today's episode to talk about our new site launch, and the long road it took for us to get here. We talk about the reasons we decided to upgrade the site, and share some of the big changes we made, and the biggest issues we've faced getting the job done.
I've been doing a lot more Behat testing recently. As my tests have gotten more complex, I've discovered that it was only a matter of "luck" that my earlier tests were properly cleaning up after themselves. What I mean, is that during my tests I fill out and submit a node form, checking that I successfully created it and that the appropriate users can see it. After each scenario you want to clean up any data that was created so you can run the test again and get the same result. The way the Drupal Behat extension works, it tracks nodes, users, roles and taxonomy terms you create using its methods, so that in its @AfterScenario function knows which nodes to delete. The problem is that when you submit the form using steps like the ones below, the extension does not track those nodes:
Big news! The annual Google Code-In contest kicked off Monday, November 18th. The contest's purpose for pre-university students (ages 13 - 17) is learning how to contribute to open-source software projects and offers them a chance to win a once in a life time grand prize of an all expense paid trip to Google HQ in California. The bigger news...Drupal was chosen as one of the ten participating organizations to create tasks for the students to complete during the 2013 contest! This is a huge honor for Drupal and gives us an amazing opportunity to grow our community. Details @ https://www.google-melange.com/gci/homepage/google/gci2013
Drupal Community, we're about 48 hours into the 2013 Code-In contest, students have already finished several tasks, and we need YOUR help. In this busy day and age, finding mentors can prove challenging and after months of "cat herding", we realized a simple solution for participation: "Just 1 Task". Even if you submit one task and mentor that task, everyone wins. We currently have 14 mentors in Google's system with tasks, but there is no limit on mentors or number of tasks we can accomplish. Ironically, after mentors add one task, they usually add a few more tasks. With Drupal 8 on the horizon, we have plenty of easy tasks that anyone at any age can accomplish, and it is the perfect opportunity to find new long time contributors. This is your chance to be a part of the global phenomenon that is open-source software! Join us in #drupal-gci or see information below on becoming a mentor.
After being selected to participate in the 2013 Code-In contest, our goal is to keep this momentum moving forward and plan to have a solid application with an elevated level of participation in Summer of Code 2014. Plus, Google has big plans in 2014 for Summer of Code's 10 year anniversary ( http://google-opensource.blogspot.com/2013/10/google-code-in-2013-and-go... ).
A big thank you to our core team of mentors that organized tasks, worked on the application, and set up everything for student participation (Janez Urevc in Slovenia, Varun Baker in Jamaica, and Matthew Lechleider in USA). Plus, we can't forget all the current mentors who jumped at the chance to contribute (Aaron Dudehofer, Abdul Qadir, Andrew Shemo, Ben Carlson, Patrick Elward, Cody Carlson, Doug Vann, Jason Daniels, Kevin Reynen, Martin Martinov, Matt V).
How to Become a Mentor
*Login with Google account @ https://www.google-melange.com/gci/homepage/google/gci2013
*Click "Register to be a Mentor"
*Connect with Drupal
*(wait for approval)
**Contact slurpee on d.o if issues
How to Add Tasks
*Login @ https://www.google-melange.com/gci/homepage/google/gci2013
*Click "My Dashboard"
*Click "Create Tasks..."
How to be a Mentor
*Add at least one task @ https://www.google-melange.com/gci/task/create/google/gci2013/drupal
*Notification of task will be sent to Drupal admins for approval
*Approval of task by admin publishes tasks publicly to students
*Request to be assigned task by student notifies mentor
*Mentor logs into Melange to click "Assign Task"
*Notification that task has started is sent to Student/Mentor/Admins
*Hangout in #drupal-irc on freenode to answer questions in real time if needed
*Comment task in Melange for feedback and help with student on task
*Review students work when completed
*Complete task to finish process
Questions? Contact Drupal's GCI 2013 Admin (Matthew Lechleider) @ https://drupal.org/user/91767/contact