For years, the last weekend in January has been a special one for the worldwide community behind the CMS system Drupal: The Global Contribution Weekend. Factorial has been a major contributor to the Drupal community for many years, so we hosted our own hybrid Global Contribution Weekend event.
Webform is a Drupal module that allows you to create forms directly in Drupal without using a 3rd party service.
It can be used to create basic “Contact Us” and complex application forms with custom field logic and integration.
In this getting started guide you’ll learn how to:
This tutorial accompanies the video above.
Symfony Scheduler provides a viable replacement to hook_cron wherein messages can be scheduled for dispatch at a predefined interval. Messages are dispatched the moment they are scheduled, and there is no message duplication, making tasks more reliable and efficient.
This post is part 4 in a series about Symfony Messenger.
With this, the sm worker provided by the SM project, the Symfony Messenger integration with Drupal, can be solely relied on. Rather than legacy runners such as Drupal web cron, request termination cron (automated_cron.module), Drush cron, and Ultimate Cron.
Scheduler functionality is implemented by the Symfony Scheduler component. The Drupal integration is provided by the SM Scheduler module
Create a message and message handler as usual, then create a Schedule Provider:
<?php
declare(strict_types = 1);
namespace Drupal\my_module\Messenger;
use Symfony\Component\Scheduler\Attribute\AsSchedule;
use Symfony\Component\Scheduler\RecurringMessage;
use Symfony\Component\Scheduler\Schedule;
use Symfony\Component\Scheduler\ScheduleProviderInterface;
#[AsSchedule('my_scheduler_name')]
final class MyScheduleProvider implements ScheduleProviderInterface {
/**
* {@inheritdoc}
*/
public function getSchedule(): Schedule {
return (new Schedule())->add(
RecurringMessage::every('5 minutes', new MyMessage()),
);
}
}A schedule provider is:
Messenger\ namespace#[AsScheduler] class attributeSymfony\Component\Scheduler\ScheduleProviderInterfacegetSchedule method. This method returns a message instance and the schedule frequency.For dependency injection, schedule providers have autowiring enabled.
What would normally be the contents of a hook_cron hook would instead be added to the message handler. The message itself does not need to store any meaningful data.
Instead of intervals via RecurringMessage::every(...), crontab syntax can be used:
\Symfony\Component\Scheduler\RecurringMessage::cron('*/5 * * * *', new MyMessage());Lastly, schedulers must be run via the consume command with a dedicated transport. The transport name is the schedule ID prefixed by scheduler_. For example, given the scheduler ID my_scheduler_name from above, the transport name will be scheduler_my_scheduler_name.
The command finally becomes: sm messenger:consume scheduler_my_scheduler_name .
Messages will be dispatched the moment their interval arrives. Normally intervals begin when the worker is initiated, however you can set a point in time to begin interval computation using the \Symfony\Component\Scheduler\RecurringMessage::every $from parameter.
The worker must be running at the time when a message is scheduled to be sent. The transport won't retroactively catch-up with messages not dispatched during the time it wasn't running.
The next post outlines how to intercept legacy Drupal @QueueWorker items and insert them into the message bus.
We talk with Kevin Quillen, author of Drupal 10 Development Cookbook, published in February, 2023 by Packt Publishing.
Professional module development - 15 weeks, 90 hours, live, online course.
Drupal Career Online - 12 weeks, 77 hours, live online, beginner-focused course.
We're using the machine-driven Amazon Transcribe service to provide an audio transcript of this episode.
Subscribe to our podcast on iTunes, Google Play, iHeart, Amazon, YouTube, or Spotify.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.
Podcast edited by Amelia Anello.
Today we are talking about AI within Drupal, How AI can help, and Modules to use with guest Martin Anderson-Clutz. We’ll also cover Augmentor AI as our module of the week.
For show notes visit: www.talkingDrupal.com/436
TopicsMartin Anderson-Clutz - mandclu
HostsNic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi
MOTW CorrespondentMartin Anderson-Clutz - mandclu Augmentor AI
Fun fact. Drupal was started in 2001 — two years before WordPress was released. According to W3Techs, this CMS powers 1.1% of all websites, from blogs to e-commerce and government sites, holding a 1.6% market share.
Building a website with Drupal is a good idea. But remember: a poorly optimized Drupal site is vulnerable, has lower response times, and results in database delays. When talking about its performance optimization, the tricks include different architectural changes, modes of caching, and other ways to speed up website load time.
The international community organizations behind Drupal, Joomla, TYPO3, and WordPress join forces in a leadership-level alliance. The members of the Alliance are united in their shared values and their message to decision-makers to always choose open source software over proprietary systems.
The Alliance represents the content management systems (CMS) behind roughly 50% of all websites online today. The Open Website Alliance was founded to promote the choice of open-source software and facilitate collaboration between free and open-source web content management projects, furthering openness, trust, and quality. Other free and open-source CMS organizations are encouraged to apply for membership.
Open source is not just the future of software, it is the present,” said Tim Doyle, CEO of the Drupal Association. “At a time when some market forces are pushing solutions that require users to sacrifice ownership of their data, we know that open source offers a better way. Through this alliance, we can help promote, educate, and inspire end-users to take back control of their software, their data, and their own words. Together we can build a better web.
The Alliance comes about as the result of the collaboration between the Drupal Association, Open Source Matters (Joomla), the TYPO3 Association, and the WordPress Project around an open letter to the European Union.
The Alliance uniquely connects its members on a leadership level. This means the organizations can more easily coordinate strategy and actions, fostering new cross-community collaboration projects and strengthening those that already exist.
The organization’s leadership is also based on collaboration. The presidency rotates among the members, and all decisions are consensus-based.
According to the Alliance’s purpose statement, the “members commit to jointly encourage prospective website owners and developers to always choose open source software over proprietary systems, and to educate why this decision is the first and most important one in a website project. Through this advocacy, we are expanding opportunities for all open source CMS projects.”
The purpose statement describes the Alliance as a “community of communities, built on and furthering openness, trust, and quality.” The collaboration organization also seeks to “benefit the public perception of open source projects, the reliability of open source software, [and] the quality and safety of open source communities,” by being “a platform where members can share and discuss best practices.”
Accounting for the distributed and collaborative nature of open-source software — also beyond content management — the Alliance also includes support of upstream dependencies: “Whenever possible, the Alliance should support third party open source projects and communities upon which our projects depend.”
In addition to a promise of joint collaboration, the Open Website Alliance members adhere to the Open Web Manifesto. Originally pioneered by the Drupal Association, the manifesto is a commitment to the web as an empowering tool, built on freedom and decentralization: “Everyone in the world, regardless of background, identity, ability, wealth, or status, has a home on the open web as a user, creator, architect, and innovator. It requires participation: The open web is a shared resource and a shared responsibility, sustained by deliberate choice and collaborative effort.”
Harnessing the concept of shared responsibility, the manifest describes the open web as a protector of privacy and freedom of speech. It should also “enable the next generation of innovators and entrepreneurs” and “must be resilient to a changing world and not controlled by a select few.”
The manifesto ends with a grand perspective on the role of the open web and open-source software that could also be a credo for the Alliance’s member projects: “Together, we’re shaping the foundation for how the digital world operates, and how future generations will live, work, connect, and express themselves. As long as our software exists, that foundation will be an open web that is open source, open access, and always open to improvement.”
The Drupal Association is proud to be a founding member of the Open Website Alliance and extends a special thank you to Matthias at Typo3 for his leadership in its formation. This work firmly aligns with the Drupal Association’s vision for a web that is innovative, inclusive, and open.
Did you know that the first-ever computer bug wasn't a piece of software code, but an actual moth? Now, let's talk about something related but not quite as buggy – website development.
Debugging is like fixing problems in a website's code. It's important because it helps Drupal developers find and solve issues, making the website work better. To do this, you need the right tools. One handy tool for PHP (a programming language often used in web development) is XDebug.
In this article, we’ll share the steps and things you need to know to set up PHP debugging using XDebug. We'll focus on using Lando and DDEV setups for Drupal. And to make things even better, we'll be using the VS Code IDE (that stands for Integrated Development Environment). Let’s get started!
XDebug is a powerful debugger that makes it easier for PHP developers to create a smooth functioning website. Here are some core features of it: