All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
If you want to add more js files, keep adding them in the same location of my.js and add it in the js_block.libraries.yml file.
And you're all ready to enjoy your custom JS script on your drupal site without any hassle.
This module solves the problem of deleting parent entities (nodes, taxonomy terms, users, etc.) that are referred to by other entities through taxonomy term reference or entity reference fields. Drupal will not prevent a user from deleting such 'parent entities', but this module will. It hooks into various entity delete forms, and does a check of the entity or entities about to be deleted as to whether or not they are referred to by any other entities, and if so, disables the delete button on the form and shows the referrers (the child entities) to the user.
CiviCRM Blog: Registering multiple people for multiple different events - using Webforms - and LOTS of conditionals
We had a scenario where client runs a cluster of events, and folk sign up for these, and usually the registrants signs up for all events, but then they might invite mum to the Dinner, and brother John to the Talk, etc etc.
We wanted to achieve this on a single form with a single payment. We explored both CiviCart and Drupal Commerce but in the end concluded we could achieve this in a much lighter way with good old webforms.
The outcome is that up to 6 people can be registered for any combination of events, eg
- c1 registers for Events A, B, C, D, E and F
- c2 registers for B, C and D
- c3 registers for A and B
- c4 registers for A and F
To see the full gory details of the conditionals approach we took, please read the full blog on Fuzion's site.Case studies and user storiesCiviEventDrupal
The developer explains how viewing your online title as a city rather than a game can help solicit feedback from its 'residents'. ...
As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!
Today, there is a Critical security release for the Mailhandler module to fix a Remote Code Execution (RCE) vulnerability.
Remote Code Execution vulnerabilities are scary - it basically means that an attacker can run arbitrary code on your site. However, there a number of mitigating factors in this case, so, it's recommended to read the security advisory for Drupal 7.
With the help of the D6LTS vendors, a new version was released for Drupal 6 as well.
You can also download the patch the patch.
If you have a Drupal 6 site using the Mailhandler module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)
If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.
Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).
This module allows to register your Service Worker script.
Please note that to register a Service Worker script your site should have a valid SSL certificate or its domain should be "localhost".
In order to register your service worker script go to Home -> Administration -> Configuration -> Service Worker Registration Settings and enter a relative path to your service-worker.js (from the site root), e.g. sites/default/files/service-worker.js
Katherine Cross explores the evolution of The Old Republic and explains why its latest expansion was worthy of being given the much-coveted title of KotOR 3. ...
Roughly 2 years after its initial launch, Tom Clancy's Rainbow Six Siege has surpassed 25 million players. ...
In last couple of years we have seen the rise of assistants, AI is enabling our lives more and more and with help of devices like Google Home and Amazon Echo, its now entering our living rooms and changing how we interact with technology. Though Assistants have been around for couple of years through android google home app, the UX is changing rapidly with home devices where now we are experiencing Conversational UI i.e. being able to talk to devices, no more typing/searching, you can now converse with your device and book a cab or play your favourite music. Though the verdict on home devices like Echo and Google home is pending, the underlying technology i.e. AI based assistants are here to stay.
In this post, we will explore Google Assistant Developer framework and how we can integrate it with Drupal.
Google Assistant works with help of Apps that define actions which in turn invokes operations to be performed on our product and services. These apps are registered with Actions on Google, which basically is a platform comprising of Apps and hence connecting different products and services via Apps. Unlike traditional mobile or desktop apps, users interact with Assistant apps through a conversation, natural-sounding back and forth exchanges (voice or text) and not traditional Click and Touch paradigms.
The first step in the flow is understanding use requests through actions, so lets learn more about it.