All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
Creates a Gatsby Markdown Post content type that can be used with the Drupal Markdown Post Gatsby theme without any additional Drupal configuration. The related Gatsby theme uses the gatsby-remark-drupal plugin for markdown and image preprocessing.
Want to try it out?
Gatekeepers, a collection of modules dedicated to site access gatekeeping.
Rumors about a cheaper Project Scarlett console continue to ebb and flow as insiders now tell Kotaku a lower-powered next-gen system is still in the cards. ...
Every Drupal site has a status report dashboard at /admin/reports/status. This module allows you to expose, as JSON, whether everything is OK or not.
The idea is that if you are managing several Drupal sites, you can set up a dashboard or some Jenkins jobs to keep track of the status of all sites in one place.Typical usage
(1) install and enable this module.
(2) get the token by running this on the command line:
This is a single-purpose module for links fields. It will validate that links to internal content are not specified as absolute links. In other words, if you're making site https://www.example.com, links with URIs like https://example.com/node/999 are disallowed with a message to use the autocomplete reference instead.
The program committee shares about impostor syndrome and wants to remind community members that you know more than you give yourself credit for.
In the first days of December, the great news makes our hearts feel warm! We are happy to meet the sparkling fresh release — and show all our readers what’s new in Drupal 8.8.
It is, in fact, the last minor release of Drupal 8. The next one, 8.9, will come out on the same day with Drupal 9 — June 3, 2020. All D8 sites that are regularly updated and free from deprecated code will be instantly ready for Drupal 9.
This module is inspired by the web service client module but unlike the original module, this new module is only compatible with Drupal 8 and tries to integrate external web services with the TypedData and Views API of Drupal 8.
A long time ago… No. Even longer ago than that. Yes. That far back. We’re going to change reality for that long ago, and that change is going to ripple forward into the current time.
I’m not talking about going back in time to kill someone we all consider the epitome of evil. I’m also not talking about the really cool idea of “the butterfly effect.” I’m talking about something that is sometimes cool and sometimes insidious.
I’m talking about retconning. That’s right. Today, we’re going to see how to handle changing reality using “retroactive continuity.”Definition We’re going to see how to handle changing reality using “retroactive continuity.” Share1Tweet1Reddit1Email
Let’s put on Phil’s “definition panda” hat for a moment and throw out the meaning of “retcon” really fast. A retcon is a piece of new information that imposes a different interpretation on previously described events, typically used to facilitate a dramatic plot shift or account for an inconsistency. Basically, it means that we’re going to give a new understanding of past events in order to change them up some to free us to move forward in the current storyline that we have going on.Literature Examples
One of the earliest retcons in literature is Sir Arthur Conan Doyle resurrecting Sherlock Holmes from his death at Reichenbach Falls by claiming that the whole series of events was a clever ruse pulled off by Holmes to stage his death.
As an author, I have an advantage of being the sole controller of the story being told. That’s awesome because I get to make up the rules. If Marcus Barber (my protagonist in my Modern Mythology series) dies, he rises from death 3 days later, is weak as a baby for another 3 days, and then gets to go on about his immortal life as a bounty hunter. Pretty cool, huh? What happens if I kill him and I need him alive and well a mere 2 days later? Too bad. Can’t do it without a serious retcon to my entire character, and I’m not allowed to do that.As an author, I have an advantage of being the sole controller of the story being told. Share1Tweet1Reddit1Email
I’m certain if I tried, my editor, continuity readers, publisher, and possibly even a few fans would show up at my door with torches and pitchforks in hand. Well… maybe not, but those 1-star reviews would certainly pour in!Game Time
However, at the RPG table, retconning does happen from time-to-time, and it is more acceptable to do so. There are several reasons for this.
The main one is that RPG storytelling is a shared narrative. One player may forget (or may have been absent for) certain events and make a decision based on a “false history.” If this false history is more cool or compelling than the real history of the tale, then a quick retcon can flip-flop things around and make this false history now the true events of what actually happened.RPG storytelling is a shared narrative. Share1Tweet1Reddit1Email
Another valid reason for slipping in a retcon is the fact that much of the storytelling is improv. If the GM or player has to make up some fact about a location or NPC on the fly, they’ll usually do a pretty good job of it. However, given even a few minutes of time to reflect on the statement, a better idea can come along. That’s when a quick pause of the game can help. Then the person can quickly retcon their statement of fact into something a little different.Who Can Retcon? A retcon should be exceedingly rare. Share1Tweet1Reddit1Email
Honestly, I think the GM has the final call on this, but players are certainly free to throw out ideas for retcons. The reason I say the GM has the final say is that she may have some prepped material based on a past event, location, or NPC. By making changes to the past, this can screw up the GM’s future plans. If the GM denies a retcon, then she probably has a really good reason for it. As a GM, it’s also okay to say something along the lines of, “I have plans for that. Let’s not change it, please.” As a player, respect that.How Often?
Actually implementing a retcon should be exceedingly rare because then things get all squirrelly with timelines, events, past notes, and recollections. Do it too many times, and you get a mind-bender of a history for your characters that will more closely resemble the movie Inception. Only do it if really necessary, not just because a “cool idea” came along. The more distant the past event is in the game, the more difficult it is to retcon that event. If a decision is merely a few minutes old, then retcons are more easily implemented because their impact waves haven’t been felt yet.How About You?
Have you ever retconned in a game? How did it work out for you? I’d like to hear from our readers some examples of how this went well… or not.
Per the D7 release schedule we aim to release Drupal 7.68 on 2019-12-04.
Details of what will be in the release can be seen here:
The final patches for 7.68 have been committed and the code is frozen (excluding documentation fixes and fixes for any regressions).
Relevant Change Record(s) for the release (this is not the full list of changes, rather only a list of notable API additions and other changes that might affect a number of other modules, so it's a good place to start looking for any problems):
- drupal_http_request() accepts data as an array in Drupal 7
- Access to web.config is blocked in .htaccess (and vice-versa)
- New "scripts" element
- theme_table() takes an optional footer variable and produces <tfoot>
If you do find any regressions, please report them in the issue queue. Thanks!
This module adds a new field type to Drupal with optional pattern validation to match Personal Identification Code (PIC) format. This module does not check if the given PIC is a real or fake, but considers only the format.
Currently supported format checks include:
The last normal feature release of Drupal 8 includes a stable Media Library as well as several improvements to workspaces and migrations. The new experimental Claro administration theme brings a fresh look to site management. This is also the first release to come with native Composer support.
The Media Library module allows easy reuse of images, documents, videos, and other assets across the site. It is integrated into content forms and seamlessly fits into CKEditor. You can upload media right from the library and even reuse a combination of uploaded and existing media. Media Library was previously included with Drupal core as a beta experimental module.New experimental administration theme
The Claro administration theme was added to Drupal core with beta experimental stability. The new theme is clean, accessible, and powerful. Administration pages are more touch-friendly, and color combinations and contrasts are more accessible.Significant improvements to Workspaces
It is now possible to define hierarchical workspaces (such as preparing a "New Year's" issue for a magazine under the "winter issue", while both receive changes to be deployed). Workspaces can now work with Content Moderation, and path alias changes can also be staged.Native Composer support included
Drupal 8.8.0 is the first release to include native Composer support without reliance on third-party projects to set up Drupal with its dependencies. New sites can be created using a one-line command.Migration improvements
The multilingual migration path is still experimental, but has received various updates. This includes handling of vocabulary language settings, term language information, and localization. Modules can now specify whether migrations provided by them are finished or not finished to help audit completeness of available migrations.New experimental Help Topics module
The existing help system is module based, whereas users intend to complete tasks, not use modules. A new task-based Help Topics beta experimental module has been added to bring in-Drupal help to the next level.The way to Drupal 9
Drupal 8.8 is the last minor release of Drupal 8 to include significant new features or deprecations prior to 9.0.0. The next (and final) minor release, 8.9, is planned to be a long-term support release that will include all the same changes as Drupal 9.0. It will not contain significant new features compared to 8.8.0, although existing experimental modules may become stable, and small API and UX improvements can still be added.
Drupal 8.9.0's planned release date is June 3, 2020, and our target release date for Drupal 9.0.0 is the same day. Most Drupal 9 preparation steps can be done on your Drupal 8 site, custom code and contributed modules now.What does this mean for me? Drupal 8 site owners
Update to 8.8.0 to continue receiving bug fixes and prepare for 9.0.0 (or 8.9.0). The next bug-fix release (8.8.1) is scheduled for January 8, 2020. (See the release schedule overview for more information.) As of this release, sites on Drupal 8.6 will no longer receive security coverage. (Drupal 8.7 will continue receiving security fixes until June 3, 2020.)
Note that all Drupal 8.8.0 sites (new installs and updates) now require at least PHP 7.0.8.
Updating your site from 8.7.10 to 8.8.0 with update.php is exactly the same as updating from 8.7.8 to 8.7.9. Drupal 8.8.0 also has updates to several dependencies. Modules, themes, and translations may need updates for these and other changes in this minor release, so test the update carefully before updating your production site. Read the 8.8.0 release notes for a full list of changes that may affect your site.Drupal 7 site owners
Drupal 7 is fully supported by the community until November 2021, and will continue to receive bug and security fixes throughout this time. From November 2021 until at least November 2024, the Drupal 7 Vendor Extended Support program will be offered by vendors.
The migration path for monolingual Drupal 7 sites is stable, as is the built-in migrationuser interface. For multilingual sites, most outstanding issues have been resolved. Please keep testing and reporting any issues you may find.Translation, module, and theme contributors
Minor releases like Drupal 8.8.0 include backwards-compatible API additions for developers as well as new features.
Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 8.7.x and earlier will be compatible with 8.8.x as well. However, the new version does include some changes to strings, user interfaces, internal APIs and API deprecations. This means that some small updates may be required for your translations, modules, and themes. Read the 8.8.0 release notes for a full list of changes that may affect your modules and themes.
This release has advanced the Drupal project significantly and represents the efforts of hundreds of volunteers and contributors from various organizations, as well as testers from the Minor release beta testing program. Thank you to everyone who contributed to Drupal 8.8.0!