All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
The database_info module provides Drupal UI with access to their see Default Drupal database tables from Drupal admin user interface.
It doesn't provide facility to alter or any changes in database. It is just listing the default database tables and their data.
Please provide feedback so we can make it better for developer use.
With this module you can easily select the nodes to be displayed in current block with autocomplete and also the choice of view mode.
If you want to customize the display of the content of block, just overload the block with the use of variable content['#bcs_items'] in the file of the current block template.
Developer: Guotong Zheng (Tony)
How can you avoid unexpected errors when you need to update your programming software to a newer version quickly? Let's look at the deployment pipeline methodology and its configuration using Gitlab on the example of a Drupal project.
Webform allows you to create powerful forms in Drupal without the need for any custom code. You can use it for a basic contact us form with a few fields such as name, phone and email, or it can also be used to create complex multi page forms with conditional fields.
If you want to allow your editors to create their own forms without the need of a developer then install and teach them how to use the module. If you want to learn more about webform we have a two part series which will help you get started; Getting Started with Webform in Drupal 8 and Moving Forward with Webform in Drupal 8.
Collecting submissions using Webform is easy, but what if you want to integrate the module with a 3rd party SaaS provider? What if you want to push all contact form submissions into your CRM system, or add a row into a Google Sheets spreadsheet.
Of course, this can be done by a developer through the right APIs but you can also do it without writing any code using a service called Zapier.
In this tutorial, you’ll learn how to send Webform submissions into Zapier which will then add it as a row into a Google Sheets spreadsheet.
Embetty displays remote content like tweets or YouTube videos without compromising your privacy.
It consists of two components:
Continuing with techniques from the “Acme” project, another ongoing feed I implemented was import from a JSON feed protected by OAuth2 authentication into “doctor” nodes. Let’s look first at the community contributions we needed to implement this.Community contributions
Provide authentication plugins to HTTP fetcher - Moshe Weitzman had already suggested (and provided a patch for) adding basic and digest authentication to the HTTP fetcher plugin. I broadened the scope to add an Authentication plugin type, and implemented an OAuth2 authentication plugin.
Implement xpath-like selectors for the JSON parser - The JSON parser, from Karen Stevenson’s original JSON source plugin, used a numeric depth to retrieve data elements. The JSON feed we had here did not work with that approach, because at the top level in addition to the array containing our data was another array (and the depth approach would draw from both arrays). Implementing a means to select fields with a /-separated syntax made this much more flexible.Project implementation
So, let’s look at the source plugin implementation:source: plugin: url # We want to reimport any doctors whose source data has changed. track_changes: true # Counting the available records requires fetching the whole feed - cache the # counts to minimize overhead. cache_counts: true # Until https://www.drupal.org/project/drupal/issues/2751829 is fixed, this # should be used in conjunction with cache_counts in most cases. It was not # strictly necessary in this project because this was the only cached ‘url’ # source plugin. cache_key: doctor data_fetcher_plugin: http data_parser_plugin: json item_selector: /providers # Note that the source .yml file does not contain the urls, or half the # authentication configuration - these are merged in using the configuration # UI (see http://virtuoso-performance.com/blog/mikeryan/configuring-migrations-form). # We present sample values here so you can see what the complete configuration # looks like. # The endpoint from which the data itself is fetched. urls: https://kservice.example2.com/providers # The http fetcher plugin calls the authentication plugin (if present), # which accepts plugin-specific configuration and returns the appropriate # authentication headers to add to the HTTP request. authentication: # migrate_plus also has ‘basic’ and ‘digest’ authentication plugins. plugin: oauth2 # The grant type used by the feed (other grant types supported in theory, # but untested, are authorization_code, password, refresh_token, and # urn:ietf:params:oauth:grant-type:jwt-bearer. grant_type: client_credentials # The base URI for retrieving the token (provided through the UI). base_uri: https://kservice.example2.com # The relative URL for retrieving the token. token_url: /oauth2/token # The client ID for the service (provided through the UI). client_id: default_client_id # The client secret for the service (provided through the UI). client_secret: abcdef12345678
The ids and fields configuration operate as they do with other JSON and XML feeds I’ve blogged about.Tags Planet Drupal Drupal Migration Use the Twitter thread below to comment on this post: June 4, 2018
Today, Microsoft announced it is buying GitHub in a deal that will be worth $7.5 billion. GitHub hosts 80 million source code repositories, and is used by almost 30 million software developers around the world. It is one of the most important tools used by software organizations today.
As the leading cloud infrastructure platforms — Amazon, Google, Microsoft, etc — mature, they will likely become functionally equivalent for the vast majority of use cases. In the future, it won't really matter whether you use Amazon, Google or Microsoft to deploy most applications. When that happens, platform differentiators will shift from functional capabilities, such as multi-region databases or serverless application support, to an increased emphasis on ease of use, the out-of-the-box experience, price, and performance.
Given multiple functionally equivalent cloud platforms at roughly the same price, the simplest one will win. Therefore, ease of use and out-of-the-box experience will become significant differentiators.
This is where Microsoft's GitHub acquisition comes in. Microsoft will most likely integrate its cloud services with GitHub; each code repository will get a button to easily test, deploy, and run the project in Microsoft's cloud. A deep and seamless integration between Microsoft Azure and GitHub could result in Microsoft's cloud being perceived as simpler to use. And when there are no other critical differentiators, ease of use drives adoption.
If you ask me, Microsoft's CEO, Satya Nadella, made a genius move by buying GitHub. It could take another ten years for the cloud wars to mature, and for us to realize just how valuable this acquisition was. In a decade, $7.5 billion could look like peanuts.
While I trust that Microsoft will be a good steward of GitHub, I personally would have preferred to see GitHub remain independent. I suspect that Amazon and Google will now accelerate the development of their own versions of GitHub. A single, independent GitHub would have maximized collaboration among software projects and developers, especially those that are Open Source. Having a variety of competing GitHubs will most likely introduce some friction.
Over the years, I had a few interactions with GitHub's co-founder, Chris Wanstrath. He must be happy with this acquisition as well; it provides stability and direction for GitHub, ends a 9-month CEO search, and is a great outcome for employees and investors. Chris, I want to say congratulations on building the world's biggest software collaboration platform, and thank you for giving millions of Open Source developers free tools along the way.
This module will help you prevent the loading of specific parts and related scripts of a page until consent for placing Cookies and related technologies is given.
With this module you won't need a complete Cookie wall. Blocked parts of your content will dynamically be loaded and shown only after giving consent. No page refresh is needed and no additional calls are made to the back-end.
Mopinion: User feedback software for websites and mobile apps
Fully understand why your users do what they do. With Mopinion you can easily collect and analyse user feedback from your website and mobile apps. Drive strategy, improve online channels and empower digital teams with faster and better decision making based on the Voice of the Customer.
Provides a scheduling feature for fieldable entities & integrates well with Drupal's Cache API. Entities can be scheduled either with a date range or recurringly on specific timeslots on specific week days.
Better description to follow.