Feeds

Author

Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Oct 06 2021
Oct 06

One of our clients had the need to display calendar links in an email which was being sent out after the user signed up for an event. The event registration was being handled as a Weform submission and and email was being sent out to the user after they had submitted the form. We had no easy way to add the calendar links in as the markup required was quite complex.

One possible alternative was the Calendar Link module. It provides twig functions for converting a link into an invite. This was not of use to us because we wanted to convert the link to an invite in an email, rather than a web page. The natural solution was to extend the token system to do this for us.

The Calendar Links Token module is the simple solution. It makes use of the Calendar Links library to implement a token which can be used in Drupal. We have used it in emails, however it could be used in other situations.

The token has quite a number of options to handle the various fields which can be used when creating links for the various calendar services.

[calendar_links:parameters:nid|date_start_field|date_end_field|title_field|description_field|location_field]

The module page has a few examples of how this can be used.

The output of the token shows links to the common calendar services:

This tiny little module has allowed us to build a simple event registration system which provides a better user experience, allowing users to easily add the event to their calendars once they have signed up.

We hope you find this module of use in one of your projects. 

Oct 04 2021
Oct 04

On a recent client project we had a demanding requirement. Content needed to be managed with the Group module as well as support workflow via the Scheduled Transitions module. The problem was that both of these modules did not work together. When content is in a Group, it operates in a way that is separate to the usal Drupal way of doing things. This goes for permissions, content management and for workflow as well. This meant that Group and Scheduled Transitions did not play nicely together. The Group Scheduled Transitions module has been released to overcome this shortcoming.

Firstly, it is important to understand that Drupal core comes with Content Moderation. Content moderation allows content to be flowed btween a number of different states. It can be used to move content from draft to review to finally being publiched. Content can also be archived. It is a flexible system which can accommodate many different workflows depending on the client needs.

The Scheduled Transitions module works in with Content Moderation, allowing for the transition from one state to another to be scheduled at a certain time in the future. When that time arrives the content is moved onto the next step. This is really handy for publishing content at a certain time, and it can also be used to archive or unpublish content.

Unfortunately (for us), the Scheduled Transitions module did not work in with the Group module which we were using to manage content permissions and access. The can find out more about this issue on drupal.org issue queue where the advice was to build a new module. And so the Group Scheduled Transitions module was born.

Behind the scenes the module adds Group support by adding view scheduled transitions and add scheduled transitions permissions. This can be used to allow group roles to also to be able to scheduled transitions.

We hope you enjoy using the module.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web