My aim is: to teach you to pass from a piece of disguised nonsense to something that is patent nonsense.
The last two months finally saw rapid progress in the development of the Search API module's Drupal 8 version. Acquia generously agreed to fund all available time for both Joris Vercammen (borisson_) and me in December and January to work on this port and related modules (especially Facets).What we did
With this backing, we were able to make a lot of head-way and got a lot of large blocking issues out of the way, among them a overhaul for the fields UI, some necessary major internal refactorings and most of the Views integration. All of this is now baked into the new Alpha 12 release, created today. Over the next couple of days, we will then also create releases for the other related modules with a working D8 version: Facets, Search API Solr Search, Search API attachments (Alpha 2) and maybe also Search API pages.
That way, we should be able to avoid a confusion of versions and conflicts for any users interested in trying out the current state of work of this module suite, or already starting to build a new site using them.
Going forth, we will also try to keep this system of creating a set of compatible releases for future Alpha versions.
As noted in the release notes, though, be careful when building sites already with this module version, as there will be no upgrade paths until Beta and some changes until then are still likely to break the storage structure (and would thus lead to loss of configuration, unless handled correctly). Also, this release (like all other non-stable releases for any module) will not be covered by Drupal's Security Team, so any discovered security vulnerabilities would be reported, worked on and fixed publicly.
That being said, though, one of the greatest improvements in the module's D8 version, at least under the hood, is it's vastly improved test coverage. That, along with Drupal.org's automated testing, enables us to be very confident in each new feature we add and each bug we fix, thus also improving the maintainability and speed of feature development in the future. And it hopefully makes it much less likely that any major bugs go unnoticed for long.
But there are also lots of improvements visible right on the surface: we carefully reviewed all major encountered problems and pitfalls with the module's D7 version and worked to make the new D8 version another large leap forward to support as many search use cases as possible, while still becoming much more user-friendly than the D7 version – probably one of the largest points of criticism overall.
So, how does it look for the further path towards a stable D8 release for the Search API (and, subsequently, for its numerous add-on modules)?
Currently, there are no immediate plans for further funding, so while I will of course still work on the port whenever I can, the pace will necessarily slack down a bit again. I also neglected maintenance of my various D7 modules in the last months, so there's also a lot of catching-up to do there. (Incidentally, a great way to help this effort if you are not comfortable with D8 yet: just go into any of my modules' issue queues and try to answer support requests, reproduce or fix bugs, test patches, etc., there.)
However, while there are still a lot of beta blockers left, most of them are relatively minor compared to the ones we now resolved, so I think a first Beta release in March should be within reach. Then it will be a matter of determining the MVP for an initial stable release and working towards that – but I expect a much shorter period for Beta than it has been for Alpha, maybe only a month or two.
Florida DrupalCamp is coming up on March 5th, and DrupalEasy is happy to be involved as a sponsor and organizer. This year's event will be better than ever, with three amazing featured speakers flying in from three different countries! Karen Stevenson, Morten DK, and Jesus Manuel Olivas will be presenting double-length sessions on the lastest Druapl 8-related topics.-->
Media partners are an important part of any DrupalCon. They help us spread the word about the event to people who might not have heard of it otherwise, and get to attend (and report on) the events. Our media partners are critical to DrupalCon's success, so we'd like to say a big thank you to all of our partners for DrupalCon Asia.
I looked at my Drupal 8 Module Acceleration Program (D8 MAP) Trello board this morning and was struck with the enormity of what we have accomplished over the past 4 months.
If you want an overview of the Drupal 8 Module Acceleration Program check out my post on Acquia.com.Tags: acquia drupal planet
Modules Unraveled: 153 Protecting Drupal 8 Sites From Spam Using Honeypot with Jeff Geerling - Modules Unraveled Podcast
- What is the Honeypot module?
- What prompted you to contribute the Honeypot module? Why was it originally created?
Flocknote (two employers ago) user registration
A bunch of my blogs / comments
- What methods or techniques does honeypot use to detect bots?
A literal ‘honeypot’
- What types of foms can it protect?
- What’s different about Honeypot vs. other spam prevention modules like CAPTCHA and Mollom?
Avoid punishing the user (explain)
- How did the port of Honeypot to Drupal 8 go?
- Have you started developing new sites in Drupal 8? And if so, how’s that going?
- How have spammers adapted to tools like Honeypot, and how do you try to keep ahead of them?” “More spam getting through Honeypot lately” (https://www.drupal.org/node/2646380)
- You’re also involved a bit in other open source communities for projects like Ansible. How does the Drupal community compare? What are some things you would like to see improved?
- Is there anything you’ve done to make sure you can continue to maintain this open source project among many others both on drupal.org and github, and not get burned out?
Think you’ve got Drupal or web smarts? We’re seeking mind-blowingly good sessions for DrupalCon New Orleans, and want to hear from you about what you know best.
We have a lot of opportunities to get your experience as part of the DrupalCon program and invite you to check out the multiple ways that you can share your knowledge and passion for Drupal after you look over our tips on how to get your proposal selected.
Vroom vroom! Love Adventure? Love Drupal? Want to win a Royal Enfield Classic motorcycle? You're in luck!
The DrupalCon Asia Developer Contest is being sponsored by the great folks over at Azri Solutions and they've come up with one of the coolest developer contests we've heard of thus far. The challenge, should you choose to accept it, is this: create a beautiful, interactive visualization of the data found at https://www.drupal.org/drupalorg/api, and submit it via github no later than 11:59 PM IST on Thursday, February 18.
In mid-January we held a webinar with Acquia, explaining how to train your team on Drupal 8.
This was an interesting webinar to run because it ended up being pretty different from our planning. There were two major changes:
- When scheduling the webinar, we intended to explain many of Drupal 8 training resources available. However, by mid-January, many contributed Drupal 8 modules didn't have stable releases and so most D8 training wasn't ready. So, in the webinar, we explaind when Drupal 8 training would be available.
- We were able to make a very cool surprise announcement. Watch to the end of the webinar for the big reveal.
From the webinar, here's an overview of when several important modules will be stable:
Web Services in today's applications and websites have become critical to interacting with third parties, and a lot of Drupal developers have the need to expose content and features on their site via an API. Luckily for us, Drupal 8 now has this capability built right into Core. Some contrib modules are attempting to make such capabilities even better, too.
To shed some light onto these new features, we've worked with Acquia to develop a webinar and subsequent series of blog posts to help get you up to speed with these exciting, new features. The first of these blog posts, Web Services 101, has been published on the Acquia Developer Center today, written by our very own Senior Architect and Community Lead Larry "Crell" Garfield.
Larry kicks off the series by laying out a comprehensive explanation of exactly what Web services are, providing a necessary and strong foundation for you to approach the exciting Web services developments new to Drupal 8. Look for his follow-up posts on Palantir.net in the coming weeks. And in the meantime, we have plenty more Drupal 8 content with Larry's .
This first post on Acquia is part of a 4-part series written by Larry, and Kyle Browning, of Acquia, based on a webinar that Larry and Kyle recently gave: Drupal 8 Deep Dive: What It Means for Developers Now that REST Is in Core.
Lately I have been hearing a lot about Laravel. This is a PHP framework to build web applications and that is quickly gaining popularity. I wanted to test it to keep up to date with this current technology. So I thought: I will build a concept in Laravel to see how it works and to compare it with Drupal 8.
- A static page in which the content is loaded from a local database.
- Build a list of Blog items which is fed from a Drupal 8 RESTful API (which I had previously built for Node.js).
Overall content of this blog:
- Introduction to Laravel
- Laravel’s foundation
- Installing Laravel
- Routing in Laravel
- Laravel’s Migration: management of the database structure
- Eloquent ORM: query the database
- HTML templating in Laravel: Blade and Views
- Loading data from a RESTful Drupal 8 API
Web developers are discovering that Web services have become critical to interacting with third parties -- whether on Web sites or in applications.
Many Drupal developers now have the need to expose content and features on their site via an API. Fortunately, Drupal 8 now has this capability in core. And some contributed modules are attempting to make it even better.Tags: acquia drupal planet
BlackMesh: Attend a sprint at one of the 40 Drupal Global Sprint Weekend locations, January 30 and 31!
Drupal Global Sprint Weekend is January 30 and 31, 2016, and so far we have 40 locations all over the world.
You might think you can't help Drupal, that you should not go to a sprint… But anyone who has worked with Drupal before (content editors, site builders), can help at a sprint. So you should go to one! Bring your computer. :)
(No location near you? *You* can organize one. :) There is still time to add your small local sprint. Read the post and get your location listed!)What will you do at a sprint? Work with others
You might have had a goal of contributing for a while, but when you tried before it may have been intimidating or frustrating.
This is your chance to change that! Working together is more fun, and we can learn so much from each other.
At the sprint, ask the organizer or another attendee what project they are working on. It might be Drupal Core, a Drupal 7 contrib project, a distribution, a translation, documentation, the Drupal 8 Handbook, porting a module to Drupal 8, or drupal.org infrastructure. Find out where their issue queue is.
Write down people's names and usernames that you meet.Post comments on issues
All over the world, people work on Drupal every day (not just on Global Sprint Weekend). To coordinate this work, we post comments (and questions!) on issues, a lot.
For example, let's say after finding the issue queue, you want to help with some bugs.
Filter the list of issues to bugs. Pick one that looks interesting to you, and make a comment on the issue saying you are going to verify it and work on steps to reproduce. After a while, make another comment to post questions you have on the issue, or post some partial information you found out. Later, make *another* comment and update the issue summary and/or steps to reproduce.Eat and have fun
Take care of yourself at the sprint. Take short breaks; stand up and stretch; walk around a bit. Spend a few quiet moments alone a couple times during the day.
If your location is not providing lunch, bring food with you. (Leaving for two hours in the middle of a sprint will not be a productive use of time.)
After getting their permission, take pictures of smiling people talking and working together, and post them.Stick with a few issues
Do not measure your success, or the success of a sprint, with how many issues get touched. Stay with one or two issues, and work with a group to get them as close to done as possible.
If you were verifying a bug, ask around and find someone to fix the bug and work with them. :) Before starting to work on a fix, make sure they post a comment on the issue also, saying what you and they will be doing next.
Test a fix. Before starting to test a fix, post a comment on the issue saying what you will test (you should be posting comments on issues before starting to work on them, saying what you will do, is pretty important). Post questions about how to test, or post the result of your trying the fix. If you do not have a local environment to try out fixes, use SimplyTest.me.
Look at a patch or pull request and post questions about the fix, or post opinions you have about the solution. Or, ask around and find someone to look at the fix, and make sure they post a comment about it.
Keep gathering people on one or two issues until they get updated, fixed, reviewed, and tested (maybe doing that a few times).Celebrate
Before leaving the sprint, post comments on issues summarizing any questions and posting partial work. Check with others at the sprint and make sure they post too. Some people don't want to say things in public on issues if they feel their work is not finished or not perfect. Let them see you did it and help them feel comfortable posting questions and half broken things.
Look back on what you got done that day, what you learned, and what barriers you had before the sprint, that you have now gotten over. Even small things add up over time.You decided to attend a sprint. What next? Tell people you are going
The person organizing the location near you might be feeling a bit nervous and wondering if people will show up. Help them by RSVP'ing. Make a comment on their post saying you will attend, respond "yes" to their meetup, get a ticket through their event page, or use whatever method they have for signups.
Tweet (use the #SprintWeekend hash tag) and say you will be at X location.
Convince a friend to go with you.Read more about sprints
Still curious about what sprinting will be like? Zsófi from Cheppers in Budapest wrote about what to expect at a Global Sprint sprint. And Leslie from OwnSourcing wrote about tools sprinters can get ready before hand (or go to a sprint to get help setting up).Have questions?
- Drupal Global Sprint Weekend 2016 wiki
- You can organize a small local sprint as part of Drupal Global Sprint Weekend 2016
- Preparation tips for organizers of local Drupal Global Sprint Weekend 2016 sprints
- Get issues you care about ready for Global Sprint Weekend
- Drupal.org handbook page: Resources for sprint planners
- Dropcast Episode 14: Mediacurrent and Cathy talk about Drupal Global Sprint Weekend 2016
As you may know, Drupal 6 will reach End-Of-Life (EOL) on February 24th, 2016. This means the Drupal community (including the Security Team) will no longer support Drupal 6!
However, a small group of commercial vendors will collaborate with the Drupal Security Team to take on Long-Term Support of Drupal 6! And myDropWizard is one of those Drupal 6 long-term support vendors. :-)
In this article, we'll answer the following questions:
- What specifically will happen on February 24th?
- What is the official Drupal 6 LTS?
- How will the process work?
- What will customers need to pay for?
Read more for the answers!
Embed code for Infographics:Read more
Acquia Developer Center Blog: Acquia U: "Making the world a better place, one Drupalist at a time." - with Amy Parker
Part 2 of 2 - Amy Parker, the Director of Acquia University, and I sat down in Acquia's downtown Boston headquarters to talk about Acquia's technology boot camp, affectionately known as "Acquia U". In this podcast we talk about the diversity of candidate backgrounds, the candidate selection process, and go into what makes a successful Acquia "Ubie." We also talk about measuring the success of a program like this in human terms.
In part one, we went over the course and how it covers much more than Drupal. The curriculum is designed to produce people able to work in tech companies: Drupal and related technologies, agile methodologies, project management tools, trouble shooting tickets, presentation skills, and more. Listen to Part 1 to learn more.Interview video - 14:30 min.
More Amy and Acquia U on the web!
- Acquia Podcast: Acquia U: "Jump in and own it. Kickstart your career." - meet Amy Parker
- Acquia Podcast with Keith Donaldson, Acquia U graduate, 2015: Drupal, the fastest way from idea to MVP
- Amy spoke with Brian Lewis in 2015 on Modules Unravelled Podcast 132, AcquiaU (here's the video of their conversation).
- Amy was a guest on DrupalEasy podcast 141 in 2014.
Most of us have been using the Features module for configuration management in Drupal 7 for years now. This is not what the module was originally intended for, but it has allowed us to move variables and configurations that were kept in the database into code, so they can be transferred from development to staging and production sites.
Features is a module that creates other modules. It was designed to bundle together functionality, say for a blog or a gallery, so you could deploy that functionality to multiple sites. If you can think of grouping together a Content type with it's fields, dependencies, and views and you are thinking along the lines of the original design.
However, somewhere along the way, some smart people figured out that we could send a lot of configuration to code using Features. Different ideas of what should be kept in each "feature" arose, and a pseudo-configuration system evolved in Drupal 7. Features provides a User Interface in the Drupal admin where developers and administrators could click together variables that go into a feature, and click together we did.