For our Drupal distribution we needed to redirect all anonymous users to the login page, as for now it’s implemented as a closed platform for social collaboration. The Drupal 8 way didn’t work anymore; we fixed it for Drupal 9 and published a working module. So if you’re building a Drupal social intranet, collaboration tool or community this might help you to direct them the right way -so they don’t get an unfriendly ‘access denied’.
Innovation within Canadian healthcare continues to provide better care experiences for those using the system. As the population ages and strains our facilities to care for those nearing their end-of-life, hospitals are looking at technological solutions to ease the burden on emergency rooms and give people access to accurate and timely healthcare.
In a previous article we explained the syntax used to write Drupal migration. We also provided references of subfields and content entities’ properties including those provided by the Commerce module. This time we are going to list the configuration options of many migrate source plugins. For example, when importing from a JSON file you need to specify which data fetcher and parser to use.
Drupal 7 introduced the brilliant feature of letting users cancel their own account and with it various options for what to do with content they’ve created when they are cancelled. One of these options is to: Delete the account and its content. Which can prove somewhat problematic if used incorrectly.
In a previous article we explained the syntax used to write Drupal migrations. When migrating into content entities, these define several properties that can be included in the process section to populate their values. For example, when importing nodes you can specify the title, publication status, creation date, etc.