Talking Drupal #437 - Drupal Mail & Easy Email

Today we are talking about sending email with Drupal, The Easy Email Module, and Drupal Mail Best Practices with guest Wayne Eaker. We’ll also cover Content Access by Path as our module of the week.

For show notes visit: www.talkingDrupal.com/437

Topics

• Current state of email
• What happened to swiftmailer
• Do you still need the mailsystem module
• Why Symfony Mailer
• New dependency in core
• Difference between Symfony Mailer module and the Symfony Mailer Lite module
• How does the Easy email module make it easier
• What are the features of Easy Email
• Why not use PHP mail
• JMAP
• Do you have a roadmap
• How do we communicate the different module options
• Are you looking for help

Resources

• Easy Email Module
• Symfony Mailer Lite Module
• Symfony Mailer Module
• Mail System Module
• hook_mail replacement issue
• Swiftmailer / Symfony mailer issue
• JMAP
• FastMail
• Free Easy Email Webinar

Guests

Wayne Eaker - drupaltutor.com zengenuity

Hosts

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ivan Stegic - ten7.com ivanstegic

MOTW Correspondent

Martin Anderson-Clutz - mandclu

• Brief description:
  • Have you ever wanted to grant users access to edit content based on the path alias of the content? There’s a module for that.
• Module name/project name:
  • Content Access by Path
• Brief history
  • How old: created in the past month by Mark Conroy of Annertech, who is also a core subsystem maintainer for the Umami profile
  • Versions available: a stable 1.0.0, created in the past week, that works with Drupal 10
• Maintainership
  • Actively maintained
  • Doesn’t have a user guide yet, but the module’s README does include some FAQs, and the project page includes a link to a YouTube video that demonstrates how to install and use the module
  • Number of open issues: 2, one of which is a bug
• Usage stats:
  • 2 sites
• Module features and usage
  • When installed, the module adds a new taxonomy vocabulary to your site. You can add terms to this vocabulary to define sections by path
  • Users on the site will have a new field, where you can reference one or more of the section terms, granting the user access to edit any content with a path that matches the section
  • The module also includes a submodule called Content Access by Path Admin Content. When installed, users who go to the admin/content listing will only see content listed that they can edit, based on either the sections they’ve been assigned, or their ownership of the content.
  • Granting edit permissions to a “section” of the website is a common ask for site owners, so I’m excited that this module makes it easy to set that up. There are solutions in the contrib ecosystem based on taxonomy for access control, and back in episode #414 we talked about Access Policy as a very flexible way to grant edit permissions, but in my mind those all require more set-up, and may require an extra step during content creation to make sure the right access is available. Content Access by Path, along with something like the near-ubiquitous Pathauto, can make it pretty painless to set up and use section-specific edit permissions