All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Under certain circumstances, it might be necessary to build a specific version of Lightning with dependencies exactly as they were when it was released. But sometimes building older versions of Lightning can be problematic. For example, maybe a new dependency conflicts with an old one, or a patch no longer applies with an updated dependency.
In that case, you can use the new "Lightning Strict" package to pin all of Lightning's dependencies (and their dependencies recursively) to the specific versions that were included in Lightning's composer.lock file when it was released. (If this sounds familiar, a "Drupal Core Strict" package also exists that does the same thing for core. But note that package is incompatible with Lightning Strict since Lightning uses PHP 7.0 when building its lock file.)
In this example, we want to build Lightning 2.2.4 - which contains the migration to Content Moderation, Workflows, and Lightning Scheduler:$ composer require acquia/lightning:2.2.4 balsama/lightning_strict:2.2.4 --no-update $ composer update
Assuming you were updating from Lightning 2.2.3, you could then follow the update instructions for 2.2.4 found in our release notes. In this case, they are:$ drush updatedb && drush cache-rebuild $ drupal update:lightning --since=2.2.3
Once you've updated to the most recent version, you can remove the dependency on balsama/lightning_strict.
The package will automatically be updated when new versions of Lightning are released. Hopefully this will solve some of the problems people have experienced when trying to build older version of Lightning.
One of the things we do on an annual basis for our clients at Advomatic is an annual site audit – a high level kick-the-tires kind of site inspection. For Drupal sites, we check the logs for any glaring errors, check for overrides in Features, run some SEO and accessibility testing, and, of course, take it... Read more »
Leads capture module webform form submittions capture action service.
Developer Diary #3: The Alchemist Code x Brave Frontier Special Crossover Collaboration! - by gumi Team
This module acts as an interface of PIVOTREV.com. PIVOTREV is a cloud based, online centralized review and rating system for real consumers community portal with a new way of product reviews to find out what real users are saying about your products or services you want to sale.
The Allowed Languages makes it possible to set restrictions on which content a user can edit based on language.
This modules was meant to clean up the toolbar, so you can use it to provide admin toolbars for your different roles.
Specifically, it is a great companion with toolbar_menu
Encrpt and Decrypt text in the URL's, In general, while Anonymous user's are given access to make some DB operations via UI, then important thing to make sure is its not hackable.. For this to make sure, minimum thing to do is encrypt the piece of text for the end user and decrypt back piece of text while doing the backend operation..heykarthikwithu Thursday, 18 January 2018 - 18:19:35 IST
This project/module helps to bulk import the nodes. Once you enable this module, you can start importing the nodes based on each content type.
The menu link can be found in "admin/structure". After this module is enabled, you will get the list of content types that are present in your site. Once you select the content type, all the fields listed in that content type will be displayed in the table format. Here, we are using nid as the identifier/primary key to bulk import nodes. Recommended file format is UTF-8 file format and of CSV file type.