All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
This module integrates with the anti-virus scanner Cloudmersive Antivirus API.
Uploaded files are forwarded to the Cloudmersive Antivirus service and checked.
are blocked in the validation routine, so they cannot be saved.
This module provides a view style plugin, which is capable to insert custom row into a views row results after every nth row or once per page.
The inserted row can contain a standard Drupal block or custom content. The row can use the custom class name along with the default row classes like views-row-1 and standard striping (odd/even), first/last row classes or it can go without them.
This module can be used for placing Google Ads or any other code snippets/content into your views blocks/pages.
This project integrates Drupal Commerce to the payment provider QuickPay, making it possible to use QuickPay as payment provider on your Drupal Commerce platform.
QuickPay supports three methods of payment; Link, Form and Embedded, but currently this module only supports the Form method, making a full redirect to QuickPay to handle the payments.
Supported Drupal 8, no plan for v7 support.
Mozart is a visual content composer for Drupal. Administratiors can create complex grid based pages on the fly through a reactive user interface.
The Mozart module is still in the alpha stage. Monthly to bi-monthly releases are planned as we move towards a stable release.
Over the past few months, I've been test-driving various Docker-based local development environments with two goals in mind. First, as my "daily driver" for consulting work - I've been a long-time MAMP Pro user and I've been feeling for a long time that I need to modernize my local development tools. Second, I'm trying to figure out what is the most ideal local development environment for students of both our 12-week Drupal Career Online class (starts March 19) and our 6-week Mastering Professional Drupal Development Workflows with Pantheon (starts February 26) courses.
One of the necessary skills for a professional Drupal developer (one who codes either modules or themes) is to be able run a solid debugging tool. As part of my evaluation of Lando, I decided to figure out how to set up local PHP debugging with Xdebug and PhpStorm on Mac OS X.
My local setup includes:
- Mac OS X Sierra 10.12.6
- Lando v3.0.0-beta.21
- Google Chrome with the Xdebug helper extension
- PhpStorm 2016.1.1
This tutorial assumes that you have a local Drupal site up-and-running in Lando and set up as a project in PhpStorm. In this example, my local site is using the Lando "Pantheon" recipe, but as you'll see in a bit, any recipe can be used. Also - my local site is based on the standard Drupal project composer template (with a nested docroot).Enable Xdebug in Lando
The first step is to enable Xdebug in Lando - this is easily done by modifying the local site's .lando.yml file. In my case, I added the following:
If your .lando.yml file is defining a custom appserver service, then you should be able to just add the "xdebug: true" bit to the appserver definition.
Once added, you'll need to perform a "lando rebuild" - this will rebuild your environment based on your .lando.yml, including adding Xdebug. The documentation page for the "rebuild" command includes a caution about how there's no guarantee that data will persist between rebuilds. In my experience, I haven't had any issues with losing my database. If you're concerned, then you may want to perform a "lando db-export" prior to rebuilding.Configuring PhpStorm
Here's where some magic comes in. Admittedly, I don't fully understand the details of some of the configuration necessary in PhpStorm to get debugging working, but I can confirm that following these steps, it has worked every time for me so far.
The first step is to add the Lando recipe folder as an "Include path" in your PhpStorm project. Open Preferences > Languages & Frameworks > PHP, click the "+" button at the bottom of the list, and manually type in the name of the folder of the Lando recipe you're using. On my machine it is: /Users/michael/.lando/services/config/pantheon. If you're using the standard "Drupal8" recipe, then it would be: /Users/michael/.lando/services/config/drupal8. Unless your username is also "michael", you'll want to update the path.
Then, go to Preferences > Languages & Frameworks > PHP > Servers
If no server for your project exists (it might be called “appserver”), then enable PhpStorm to listen for Xdebug connections, load a page from your local site in your browser and PhpStorm will prompt you to accept the incoming connection. In my case, it didn’t matter if the Xdebug helper is set to debugging or disabled at this point.
Then, once a server for your local site exists (remember, it might be called "appserver”), select it and ensure that "Use path mappings" is checked, and ensure that your project folder is mapped to "/app" for the "Absolute path on server". Also ensure that the "Absolute path for the server" for the “include path” is "/srv/includes".
Give it a try!
At this point, we should be ready for debugging! As a test, open up the site's index.php in PhpStorm and place a breakpoint.
Then, using the Xdebug Helper extension, enable debugging. Also ensure that PhpStorm is still set to listen to incoming Xdebug connections.
Finally, load your local site's home and watch how PhpStorm will pause code execution at your breakpoint in the index.php file.
While Xdebug is a powerful tool and will absolutely save you loads of time, there's a dark side. Performance will suffer. I recommend disabling Xdebug in your .lando.yml - by setting "xdebug: false" - (and rebuilding) when you're not using it. You can leave it enabled and gain back some (but not all) performance by disabling PhpStorm's listener as well.Final thoughts
In case you're wondering where some of the configuration settings come from, here's what I've figured out so far:
- "appserver" is the name of the Lando service that contains the codebase.
- "/app" is the absolute path of the codebase in the "appserver" Docker container.
- "/srv/includes" is the absolute path to a Lando-provided "prepend.php" file in the "appserver" Docker container. As far as I can tell, this file defines and sets a bunch of environment variables depending on the recipe used.
Read more »
Cross-origin resource sharing (CORS) - the module provides possibility to customize settings CORS by path patterns.
All settings will be saved in configs.
PhpStorm is quite convenient to debug scripts with XDebug (do you support Derick for giving us XDebug ?): just add a "Run/Debug configuration", choosing the "PHP Script" type, give a few parameters, and you can start debugging your PHP CLI scripts, using breakpoints, evaluations, etc.
Wonderful. So now, let's define such a configuration to debug a Composer script, say a Behat configuration generator from site settings for some current Drupal 8 project. Apply the configuration, run it in debug mode, and ....
...PhpStorm doesn't stop, the script runs and ends, and all breakpoints were ignored. How to actually use breakpoints in the IDE ?
Social feed fetcher module provides the user to fetch the data from their respective Facebook, Twitter, and Instagram profiles and then display them accordingly as per their requirement using the Drupal node system.
This module depends on https://www.drupal.org/project/socialfeed
If the answer is something like "to get some content to your site." - consider again. The SoMe feed might benefit you or harm you depending how you manage it.
Here are some points to consider:Social media SoMe Drupal 8 SoMe wall Planet Drupal
Is a fork of the features module varbase_media from Varbase Distribution.
I'm a big fan of the Varbase Distribution and wanted the people who like some of the functionality but feels that Varbase is too heavy for some website to be able to install separate features.#Purpose of this module
Is to easily add and save images.
This module provides an integrated login experience for users by integrating OKTA and Drupal. Core OKTA functionality is seamlessly presented through Drupal, where the end user is not exposed directly to OKTA, this provides a cohesive experience.
We are thrilled to bring you the most exciting event of this year Drupal Camp Goa 2018! You would be ecstatic to be a part of something really big that’s happening in India’s most sought-after destination, Goa. It’s a shoutout for all of you who love developing and would like to extend their immense support to the web’s leading content management system (CMS), Drupal!Why should Drupalers have all the fun!
This time it is not just Drupal, we are exploring beyond it. Join us to share your knowledge on topics like...
Datetime Time Day provides the ability to store data (start, end) time of single day.Requirements
This module requires the following modules:
- Field (Drupal core).
- Datetime (Drupal core)
- Download and enable as normal module
- Datetime (Drupal core)
You could configure form view mode and display view mode, like in any standard field. See Field UI help for more details.
We always aim to offer our customers the best experience possible, with the tools they want to use. Usually that means expanding the platforms and languages we support (which now stands at six languages and counting), but occasionally it means dropping tools that are not being used so that we can focus resources on those that are.
For that reason, we will be dropping support for the HHVM runtime on 1 March 2018.
HHVM began life at Facebook as a faster, more robust PHP runtime. Although it never quite reached 100% PHP compatibility it got extremely close, and did see some success and buy-in outside of Facebook itself. Its most notable achievement, however, was providing PHP itself with much-needed competition, which in turn spurred the work that resulted in the massive performance improvements of PHP 7.
Similarly, Facebook's "PHP extended" language, Hack (which ran on HHVM), has seen only limited use outside of Facebook itself but served as a test bed and proving ground for many improvements and features that have since made their way into PHP itself. Like HHVM itself, though, Hack never achieved critical mass in the marketplace outside of Facebook.
Back in September, Facebook announced that they would be continuing development of Hack as its own language, and not aiming for PHP compatibility. Essentially Hack/HHVM will be a "full fork" of the PHP language and go its own way, and no longer try to be a drop-in replacement for PHP.
Platform.sh has offered HHVM support as a PHP alternative for several years, although as in the broader market it didn't see much use and with the release of PHP 7 the performance advantage of HHVM basically disappeared, leading people to migrate back to vanilla PHP 7. Looking at our own statistics, in fact, we recently found that HHVM was virtually unused on our system.
"Give the people what they want" also means not giving them what they clearly don't want, and the PHP market clearly doesn't want HHVM at this point. We will therefore be dropping support for it on 1 March. If Hack/HHVM develops its own market in the future and there's demand for it we may look into re-adding it at that time, but we'll wait and see.
Good night, sweet HHVM, and may a herd of ElePHPants sing thee to they REST!Larry Garfield 30 Jan, 2018