All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
jQuery-viewport-checker is a Drupal integration of jQuery-viewport-checker library. Little script that detects if an element is in the viewport and adds a class to it.Dependencies
Many are the epic arms forged in your fantasy game. But sometimes the most powerful armaments require tools as powerful as they are. Enter these forges of power, able to bring forth the most fantastic of creations.
- Cold Iron Forge: Created by a race of arctic dwarves, for whom fire was a luxury, this huge rune carved anvil allows purification of ores and forging of weapons and armor using blistering cold instead of heat. Hammering ore on the anvil causes it to crumble to fragments and re-merge purer each time. Refined ores can be tempered and shaped with the cold fire of the runes. Weapons and armor created in the cold iron forge are often heavy and dull, but are infused with the power of cold and brutally effective.
- Forge Weaver: And intricate device built by a genius spider elf tinker, the forge weaver looks like a cross between a huge loom and a twisted metal spider. Metal placed into it’s hopper is processed into thread like cable, which can be woven into material as strong as plate, but much more flexible and light. The forge can also be used to produce bowstrings and a few select weapons, but most weapons are beyond its abilities.
- Golem Forge: A few golem forges exist. All of them resemble golems and eat raw ore, scrap and refined metals and refine them into weapons and armor internally. Some were made to mass produce a common quality armament to supply large forces, but the most impressive of them were constructed to take rare materials and components and produce a single powerful weapon or armor with more skill than its creator could produce.
- Lightning forge: The lightning forge sits on a desolate hilltop, and operating it is the task of a lifetime. Material is held aloft on a pole and left there for lightning to strike. When it does, the smith must quickly lower it and work it as long as possible until it cools. This process, which may take dozens, if not hundreds of years results in arms that are blackened and electrically scarred, but which carry the fury of the sky. Of course, you may be able to speed the process with the help of a powerful caster.
- Ocean Forge: In the crushing darkness of the ocean, over a volcanic vent sits the ocean forge. Just getting there is a major challenge. Forging weapons and armor in the pressure and heat with salt water contaminating materials and wicking away heat faster than air taxes the skills of even a master smith. The strangely patinaed arms created here are almost indestructible and highly resistant to the elements.
Permission UI allows to create dynamic permissions associated with core/contrib entities via the UI. The main purpose is to avoid overwhelming of permission (like Node Access) per bundle and no dried permission system (e.g. just "administer nodes"). This module provides an UI to add necessary permissions and export them as any other configuration.Implementation What is done
1. UI for CRUD permission
This module allows creation of nested tree structures, kept in a specified configuration entity. It is somewhat similar to core taxonomy tree, but allowing elements having different parameters (fields), definable in a child class depending on anything you like (level, id, etc), not exactly the same for every element.
It uses AJAX for every operation.
This is an API module, see the attached example for a possible use case.
A Drupal module which provides consolidated management for various types of
Sometimes you would like to import a huge volume of data from a CSV file into Drupal. Maybe from another CMS. Maybe from a spreadsheet. But there is no such functionality in Drupal 8 core.
To import your data from a CSV file, you need to install and enable the contributed module "Content Import". In this tutorial, you are going to import five content items of the content type Customer.
A checkout is a pretty fundamental part of a commerce system. So the fact that Commerce 2.x has a checkout is not really news. But it’s what you can do with the checkout that makes 2.x special.
You can now configure the checkout workflow. You can opt to ask for billing information, shipping information, certificates, registration details, etc. There’s lots of different data that can change depending on the type of product you sell. If you sell digital products, for instance, you don’t need shipping information. If you sell course registrations, you might require pre-existing certificates. Maybe you do both, so you need to configure multiple types of checkouts.
And that’s easy to do. For the most part, it’s a matter of dragging and dropping options. You can add or remove pieces pretty easily. If you need something really custom, like if you need to validate a safety certificate against a third party, you might need a developer to build that functionality. But otherwise it’s a fairly simple process.
You can also integrate into any part of the checkout. Maybe you do something when you add to cart, or when you complete the order. Maybe you even go off-site to pay through PayPal or register through Eventbrite and then come back. You can hook into any step you need in order to get those things done.
Activision patented tech for "driving microtransactions in multiplayer video games" that can match players up with more experienced foes to get the junior players to buy in-game items like loot boxes. ...
Read our Roadmap to understand how this work falls into priorities set by the Drupal Association with direction and collaboration from the Board and community.
We're back from DrupalCon Vienna, with updates on what's new from the month of our European event.Announcement TLS 1.0 and 1.1 deprecated
Drupal.org uses the Fastly CDN service for content delivery, and Fastly has depreciated support for TLS 1.1, 1.0, and 3DES on the cert we use for Drupal.org, per the mandate by the PCI Security Standards Council. This change took place on 9 Aug 2017. This means that browsers and API clients using the older TLS 1.1 or 1.0 protocols will no longer be supported. Older versions of curl or wget may be affected as well.Drupal.org updates DrupalCon Calendar syncing
In our last update, we teased a new feature for DrupalCon attendees - the ability to sync your personal schedule to a calendar program. We're pleased to report that this feature made it in time for the event, and was used by attendees throughout the week. If you've already synced your calendar for DrupalCon Vienna, you're already set up to use the same feed for DrupalCon Nashville next April!Keynote simulcast to Youtube
This year at DrupalCon, in addition to live streaming on Events.Drupal.org itself, we simulcast the keynotes to YouTube. We also embedded the keynote on the Drupal.org homepage - to spread the latest news about Drupal beyond DrupalCon attendees.
In fact, if you couldn't attend DrupalCon or just missed the keynotes, you can watch Dries' update on the Drupal project here:Industry Pages promoted in the front page Call-to-Action
We've also made some updates to how the industry pages are promoted. In addition to the dedicated block with icons linking to each industry, we now also promote the industry solutions landing page in the main CTA under the homepage header.
We hope to further encourage users evaluating Drupal to explore some of the tremendous solutions that are already out there, and take inspiration from their success.First-in/First-out issue sorting
To make sure that issues are reviewed by maintainers in the order they are received, it is now possible to sort the issue queues by when the issue status last changed. This means RTBC issues can be reviewed on a first-in/first-out basis!
This 'status changed' date field is available on the advanced search view for any issue queue. Here's what it looks like for Drupal core:Project creation analysis
About six months ago we opened up project creation on Drupal.org to allow any confirmed user to create a full project. We've put together a blog post outlining the impact these changes have had on the contrib landscape. In short, we've seen a tremendous increase in the rate of project creation, and the rate of applications for security advisory coverage, and a modest increase in projects receiving stable releases without yet opting in coverage. We're continuing to monitor project creation and work with the Security Working Group and others on next steps.Displaying orphan dev releases
In last month's update we talked about a variety of changes we made to project pages, to provide better signals about project quality to evaluators. In response to feedback, we've restored the visibility of dev releases, even when they aren't associated with a tagged release.
This is particularly helpful for project maintainers trying to bring visibility to the next major development version of their modules, such as their Drupal 8 module port efforts.
As always, we’d like to say thanks to all the volunteers who work with us, and to the Drupal Association Supporters, who made it possible for us to work on these projects. In particular we want to thank:
- comm-press - Renewing Classic Supporting Partner
- Code Koalas - Renewing Classic Supporting Partner
- KWALL - Renewing Classic Supporting Partner
- ANNAI - Renewing Classic Supporting Partner
- UniMity Solutions - *NEW* Classic Supporting Partner
- Berger Schmidt - Renewing Classic Supporting Partner
If you would like to support our work as an individual or an organization, consider becoming a member of the Drupal Association.
In about a month, it'll be 2 years since Drupal 8.0.0 was released. Drupal 8 has come a long way since then, especially with Drupal 8.4.0 released two weeks ago, which is the most feature-packed release yet.
Drupal 8 is the future of Drupal. It's awesome.
However, looking at all the blogs and articles and podcasts in the Drupalsphere, we're sending a message that you should only build new sites on Drupal 8.
The common wisdom is that starting a new project on Drupal 7 is dumb idea.
While I'm sure there's lots of people who are OK with that or even think that's the right message...
I strongly believe that we are hurting the Drupal project by sending that message.
Read more to find out why!
Though it notes that it recognizes the risks of flirtations between gambling and gaming, the government itself will rely on The Gambling Commission's ongoing observation. ...
- Disallow assignments in conditions - This is controversial and could use more feedback.
- Define order of object method modifiers as in PSR-2
- Explicitly disallow yoda conditions - This issue is postponed on the assignments newly announced above.
- Disallow or or and in Logical Operators (use || or && - this issue is approved but not yet ratified as it is waiting on a coder rule
This module allows you to accept multiple payments during checkout for an order. It's intended for payment types like gift cards or store credit, where the customer may not be able to fully pay for the order with the available balance. This module allows payments from supporting gateways to be added in a new checkout pane, where they can reduce the balance due on an order. Then, the remainder can be paid with the standard payment information pane.