All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
We have released version 2.0 of our Federated Search application and Drupal integration.
Since our initial release, we’ve been doing agile, iterative development on the software. Working with our partners at the University of Michigan and the State of Georgia, we’ve made refinements to both the application and the Drupal integration.Better search results
Default searches now target the entire index and not the more narrow tm_rendered_item field. This change allows Solr admins to have better control over the refinement of search results, including the use of field boosting and elevate.xml query enhancements.Autocomplete search results
We added support for search autocomplete at both the application and Drupal block levels -- and the two can use the same or different data sources to populate results. We took a configurable approach to autocomplete, which supports “search as you type” completion of partial text. These results can also include keyboard navigation for accessibility.
Since the Drupal block is independent of the React application, we made it configurable so that the block can have a distinct API endpoint from the application. We did this because the state of Georgia has specific requirements that their default search behavior should be to search the local site first, looking for items marked with a special “highlighted content” field.Wildcard searching
We fully support wildcard searches as a configuration option, so that a search for “run” will automatically pass “run” and “run*” as search terms.Default facet control
The default facets sets for the application -- Site, Content Type, and Date Range -- can now be disabled on a per-site basis. This feature is useful for sites that contribute content to a network but only wish to search their own site’s content.Enhanced query parameters
We’ve added additional support for term-based facets to be passed from the search query string. This means that all facet options except dates can be passed directly via external URL before loading the search form.Better Drupal theming
We split the module’s display into proper theme templates for the block and it’s form, and we added template suggestions for each form element so that themes can easily enhance or override the default styling of the Drupal block. We also removed some overly opinionated CSS from the base style of the application. This change should allow CSS overrides to have better control over element styling.What’s Next for Users?
All of these changes should be backward compatible for existing users, though minor changes to the configuration may be required, Users of the Drupal 8.x-2.0 release will need to run the Drupal update script to load the new default settings. Sites that override CSS should confirm that they address the new styles.
Currently, the changes only apply to Drupal 8 sites. We’ll be backporting the new features to Drupal 7 in the upcoming month.
Users of the 1.0 release may continue to use both the existing Drupal module and their current JS and CSS files until the end of 2019. We recommend upgrading to the 2.0 versions of both, which requires minor CSS and configuration changes you can read about in the upgrade documentation.Special Thanks
Palantir senior engineer Jes Constantine worked through the most significant changes to the application and integration code. Senior front-end developer Nate Striedinger worked through the template design and CSS. And engineer Matt Carmichael provided QA and code review. And a special shoutout to James Sansbury of Lullabot -- our first external contributor.Development Drupal Open Source
Libraries provider is a module meant to relieve themes and modules
from the loading of and configuration of third party assets.
The JSON:API module was added to Drupal 8.7 as a stable module!
See Dries’ overview of why this is an important milestone for Drupal, a look behind the scenes and a look toward the future. Read that first!Upgrading?
As Mateu said, this is the first time a new module is added to Drupal core as “stable” (non-experimental) from day one. This was the plan since July 2018 — I’m glad we delivered on that promise.
This means users of the JSON:API 8.x-2.x contrib module currently on Drupal 8.5 or 8.6 can update to Drupal 8.7 on its release day and simply delete their current contributed module, and have no disruption in their current use of JSON:API, nor in security coverage! 1What’s happened lately?
The last JSON:API update was exactly two months ago, because … ever since then Gabe, Mateu and I are have been working very hard to get JSON:API through the core review process. This resulted in a few notable improvements:
- a read-only mode that is turned on by default for new installs — this strikes a nice balance between DX (still having data available via APIs by default/zero config: reading is probably the 80% use case, at least today) and minimizing risk (not allowing writes by default) 2
- auto-revisioning when PATCHing for eligible entity types
- formally documented & tested revisions and translations support 3
- formally documented security considerations
Get these improvements today by updating to version 2.4 of the JSON:API module — it’s identical to what was added to Drupal 8.7!Contributors
An incredible total of 103 people contributed in JSON:API’s issue queue to help make this happen, and 50 of those even have commits to their name:
Wim Leers, ndobromirov, e0ipso, nuez, gabesullice, xjm, effulgentsia, seanB, jhodgdon, webchick, Dries, andrewmacpherson, jibran, larowlan, Gábor Hojtsy, benjifisher, phenaproxima, ckrina, dww, amateescu, voleger, plach, justageek, catch, samuel.mortenson, berdir, zhangyb, email@example.com, malik.kotob, pfrilling, Grimreaper, andriansyahnc, blainelang, btully, ebeyrent, garphy, Niklan, joelstein, joshua.boltz, govind.maloo, tstoeckler, hchonov, dawehner, kristiaanvandeneynde, dagmar, yobottehg, firstname.lastname@example.org, keesee, caseylau, peterdijk, mortona2k, jludwig, pixelwhip, abhisekmazumdar, izus, Mile23, mglaman, steven.wichers, omkar06, haihoi2, axle_foley00, hampercm, clemens.tolboom, gargsuchi, justafish, sonnykt, alexpott, jlscott, DavidSpiessens, BR0kEN, danielnv18, drpal, martin107, balsama, nileshlohar, gerzenstl, mgalalm, tedbow, das-peter, pwolanin, skyredwang, Dave Reid, mstef, bwinett, grndlvl, Spleshka, salmonek, tom_ek, huyby, mistermoper, jazzdrive3, harrrrrrr, Ivan Berezhnov, idebr, mwebaze, dpolant, dravenk, alan_blake, jonathan1055, GeduR, kostajh, pcambra, meba, dsdeiz, jian he, matthew.perry.
Thanks to all of you!Future JSON:API blogging
I blogged about once a month since October 2018 about JSON:API, to get more people to switch to version 2.x of the JSON:API module, to ensure it was maximally mature and bug free prior to going into Drupal core. New capabilities were also being added at a pretty high pace because we’d been preparing the code base for that months prior. We went from ~1700 installs in January to ~2700 today!
Now that it is in Drupal core, there will be less need for frequent updates, and I think the API-First Drupal: what’s new in 8.next? blog posts that I have been doing probably make more sense. I will do one of those when Drupal 8.7.0 is released in May, because not only will it ship with JSON:API land, there are also other improvements!
Special thanks to Mateu Aguiló Bosch (e0ipso) for their feedback!
We’ll of course continue to provide security releases for the contributed module. Once Drupal 8.7 is released, the Drupal Security Team stops supporting Drupal 8.5. At that time, the JSON:API contributed module will only need to provide security support for Drupal 8.6. Once Drupal 8.8 is released at the end of 2019, the JSON:API contributed module will no longer be supported: since JSON:API will then be part of both Drupal 8.7 and 8.8, there is no reason for the contributed module to continue to be supported. ↩︎
Existing sites will continue to have writes enabled by default, but can choose to enable the read-only mode too. ↩︎
Limitations in the underlying Drupal core APIs prevent JSON:API from 100% of desired capabilities, but with JSON:API now being in core, it’ll be much easier to make the necessary changes happen! ↩︎
Join Ang, Chuck, John, and Matt for a discussion about the technology needed for presenting a gaming stream. This episode was recorded following Gnome Stew’s first actual play stream on Twitch, and if you missed the stream, you can catch the recording of “The Gnomes Do Mortzengersturm, the Mad Manticore of the Prismatic Peak” on the Gnome Stew YouTube channel! Will these tech gnomes be able to figure out how to avoid the stew this week?
Special thanks to Meghan Dornbrock for the fantastic gnome character art!
Keep up with all the gnomes by visiting gnomestew.com, following @gnomestew on Twitter, or visiting the Gnome Stew Facebook Page. Subscribe to the Gnome Stew Twitch channel, the Gnome Stew YouTube channel, check out Gnome Stew Merch, and support Gnome Stew on Patreon!
Follow Chuck at @InnocuousChuck on Twitter.
Check out Matt…if you can find a way.
Follow Ang at @orikes13 on Twitter.
Label fields have 128 characters limit. with this module, you can set the new limit for it.Usage:
after install,go to admin/config/label_length_limit/labellengthlimit and set the max value limit. its default value is 150
With robust and flexible infrastructure, innovative design and some great out of the box features, Drupal CMS is one of the top web solutions considered by businesses around the world to stay abreast with the surge in demand for personalization, interactivity and scalable tools. However, it turns out that a lot of marketers are quite unfamiliar with Drupal's potential.
This module allows you export configuration strings as multiline.
This module allows you to provide a taxonomy term by name as default argument.Sponsors
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 Moderately Critical security release for Drupal core to fix a Cross Site Scripting (XSS) vulnerability.
Folks have been asking us, so this is just a short note to say that this issue does NOT affect Drupal 6. So, you can focus just on updating your Drupal 7 and Drupal 8 sites today. :-)
Google unveiled a controller alongside its cloud-based game streaming service Stadia this week, but players aren't locked into using Google-made hardware to play games on the service. ...
The announcement for Google Stadia was absolutely perfect and flawless. It also told us exactly nothing about the relevant aspects for content creators or consumers. ...
Gamasutra speaks with Jack Buser, director for games business development at Google, about the boxless future that Stadia is promising. ...
Using this Module you can add secure ID-card, Mobile-ID and Smart-ID app authentication to your site without the need for complex custom nginx/apache setup and multiple integrations for each country and each secure identification method.
Smart ID has implemented many different identification methods because each country has its own popular method.
Currently it is possible to authenticate people Securely in Estonia, Latvia, Lithuania and Portugal.
Under certain circumstances the File module/subsystem allows a malicious user to upload a file that can trigger a cross-site scripting (XSS) vulnerability.Solution:
- If you are using Drupal 8.6, update to Drupal 8.6.13.
- If you are using Drupal 8.5 or earlier, update to Drupal 8.5.14.
- If you are using Drupal 7, update to Drupal 7.65.
Versions of Drupal 8 prior to 8.5.x are end-of-life and do not receive security coverage.Reported By:
Here are ideas to help you prepare for this exciting week among thousands of other Drupalers, while hundreds of sessions, summits, trainings, just-for-fun events, and more are all happening—some simultaneously. We have tips for during the conference and afterward, so make the most of this new experience!