This module provides the raulfraile/ladybug Dumper for use with Devel.
The recommended method for installation is via Composer.
composer require drupal/devel_ladybug
Just go to admin/config/development/devel and select Ladybug as your preferred PHP Variables Dumper.
This module allows custom JavaScript to be injected inside a WYSIWYG iframe and modify the content within it.
It is useful if you have JavaScript that runs on the front end of your site and you want to run the same JavaScript inside the WYSIWYG to make the appearance of the content in the WYSIWYG more closely match the final output.
It requires the Wysiwyg module in order to work, and currently only works if you are using CKEditor as your WYSIWYG editor.
This module enables creation of media entities during a core D6->D8 upgrade.
It creates one media entity per file entity, autopopulating mimetype and owner uid, and using bundles and media providers to fill in other fields (e.g. image width and height).
Tools like Views, Search API, Facets, and more rely on request parameters to process specific types of input. But, this functionality is often limited to whatever the tool itself provides.
One limitation we encountered was the ability to conditionally render logic based on request parameters.
For instance, I may want to display a block conditionally if a page does not have a query parameter "search". This use case works well with the Block Visibility Groups module, except we need a condition for processing these parameters from the request.
This module allow to get the Omega 4 .info configuration from the variable without using drush command.
Install as usual.
How to use:
1- Set the properly permission.
2- Go to the Theme info in administration menu
3- Do as you wish with the .info configuration file (I recommend copy - paste on your theme .info)
Thanks to Omega Theme, I need modify some of it's code to get the .info because I can't use drush and saw some other that have the same problem.
So here is my little contribution.
The DrupalOop module is a simple backend OOP structure for building modules in Drupal 7. The idea is to write modules and other custom Drupal components as PHP Objects as simply as possible. This allows for PHPUnit testing to be more easily applied to Drupal 7 code and provides helper methods for actions that are module specific.
To keep things simple, there is no dependecy on anything Drupal 8. You don't need composer or to know what PSR-4 is. Everything is done using Drupal 7 standards.
Multiple configuration destinations are often used to store configuration specific to environment or even to separate on a site-by-site basis.
A common workflow is to leverage "sync" (the default and out-of-the-box configuration destination) as the destination for storing shared/global configuration. Overridden and additional configuration is stored in subsequent configuration destinations. A config import with the "partial" option allows for the secondary destination to bring in only that which is overridden or added.
A deeper dive into this workflow:
Assistant to administer SSL certificates.
Displays a warning and sends e-mail(s) about the expiration of a term of the SSL certificate directly on the site. Thus you will never forget to update the SSL certificate for the site.
PhpFastCache module makes use of PhpFastCache library with for main goal to improve Drupal's performances by allowing you to set up a custom cache backend.
