Drupal

Webform Submissions Delete

New Drupal Modules - 19 July 2019 - 5:52am

This module cab be used to delete the
webform submissions using start date,
end date all at once.

This module will create menu under the webform
Results tab, with the help of his user can select
the submission(s) to delete.

Categories: Drupal

Gábor Hojtsy: First beta of Upgrade Status for Drupal 8 out with highly improved reporting, helps to best collaborate with project maintainers

Planet Drupal - 19 July 2019 - 5:31am

On our way to Drupal 9 every site will need to take care of making updates to their custom code as well as updating their contributed projects. However this time, instead of needing to rewrite code, only smaller changes are needed. Most contributed modules will only need to deal with a couple changes. Collaborating with project maintainers is the best way to get to Drupal 9. The first beta of the Upgrade Status module alongside recent drupal.org changes focus on making this much easier.

Upgrade Status beta provides better insight into Drupal 9 readiness

Take the first beta of the Upgrade Status module and run it on your site. It will provide executive summaries of results about all scanned projects and lets you inspect each individually.

Custom and contributed projects are grouped and summarised separately. You should be able to do all needed changes to your custom code, while for contributed projects you should keep them up to date in your environment and work with the maintainers to get to Drupal 9. The later is facilitated by displaying available update information inline and by pulling the Drupal 9 plan information from drupal.org projects and displaying it directly on the page.

This is how the summary looks like after scanning a few projects:

Digging deeper from the executive summary, you can review each error separately. The beta release now categorizes issues found to actionable (Fix now) and non-actionable (Fix later) categories with a Check manually category for items where it cannot decide based on available information. For custom projects, any deprecation is fixable that has replacements in your environment while for contributed projects supporting all core versions with security support the window is shifted by a year. Only deprecations from two or more releases earlier can be fixed (compared to the latest Drupal release) while keeping Drupal core support. So somewhat ironically, Upgrade Status itself has deprecated API uses that it cannot yet fix (alongside ones it could fix, but we have them for testing purposes specifically):

The module is able to catch some types of PHP fatal errors (unfortunately there are still some in projects that we need to figure out the best way to catch). The @deprecated annotation information guiding you on how to fix the issues found are also displayed thanks to lots of work by Matt Glaman.

Own a Drupal.org project? Direct contributors to help you the way you prefer!

If you own a Drupal.org project that has Drupal 8 code, you should specify your Drupal 9 plans. It is worth spending time to fill in this field to direct contributors to the best way you prefer them help you, so contributions can be a win-win for you and your users alike. Whether it is a META issue you plan to collect work or a specific time in the future you will start looking at Drupal 9 deprecations or a funding need to be able to move forward, letting the world know is important. This allows others to engage with you the way you prefer them to. Additionally to it being displayed in Upgrade Status's summary it is also displayed directly on your project page!

Go edit your project and find the Drupal 9 porting info field to fill in. Some suggestions are provided for typical scenarios:

This will then be displayed on your project page alongside usage and security coverage information. For example, check it out on the Upgrade Status project page.

Thanks

Special thanks for dedicated contributors and testers of the Upgrade Status module who helped us get to beta, especially Karl Fritsche (bio.logis), Nancy Rackleff (ThinkShout), Tsegaselassie Tadesse (Axelerant), Bram Goffings (Nascom), Travis Clark (Worthington Libraries), Mats Blakstad (Globalbility), Tony Wilson (UNC Pembroke), Alex Pott (AcroMedia, Thunder), Charlie ChX Negyesi (Smartsheet), Meike Jung (hexabinær Kommunikation). Thanks to Neil Drumm (Drupal Association) and Angela Byron (Acquia) for collaboration on the Drupal 9 plan field.

Categories: Drupal

Page Maintenance Mode

New Drupal Modules - 19 July 2019 - 5:04am

The Page Maintenance Mode module is very useful module. Site admin can put specific page into maintenance mode. Only site admin can see maintenance page. Using this module site admin can put multiple pages into maitenance mode and configure maintenance page message according to their requirement.

This module will create an admin configuration page.
admin/config/pagemaintenance/settings
This configuration page will have three option checkbox, page url and maintenance mode message.

Categories: Drupal

Ecomail webform

New Drupal Modules - 19 July 2019 - 4:41am

Ecomail webform adds Webform handler to add contact to the list of direct e-mailing service Ecomail.cz.

Categories: Drupal

Drupal marketplace

New Drupal Modules - 19 July 2019 - 4:33am

Simple UI tool that will help to find and install module/themes without help of the Drupal Console/Drush or attendance of the drupal.org

Categories: Drupal

Themes marketplace

New Drupal Modules - 19 July 2019 - 4:26am
Categories: Drupal

heykarthikwithu: Configure Redis, Set & Get Cache key values from Redis in Drupal

Planet Drupal - 19 July 2019 - 2:30am
Configure Redis, Set & Get Cache key values from Redis in Drupal

Redis is an open-source, networked, in-memory, key-value data store that can be used as a drop-in caching backend for your Drupal, Add the Redis module from Drupal.org, Enable the module & Verify Redis is enabled.

heykarthikwithu Friday, 19 July 2019 - 15:00:23 IST
Categories: Drupal

Mediacurrent: Rain Walk-Through for Authors & Admins

Planet Drupal - 18 July 2019 - 11:49am

Mediacurrent created the Rain Install Profile to build fast, consistent Drupal websites and improve the editorial experience. Rain expedites website creation, configuration, and deployment.

In this article, we will walk through each of the main features that ship with the Rain distribution. This tutorial is intended to help content authors and site administrators get set up quickly with all that Rain has to offer.

Have a question or comment? Hit me up @drupalninja on Twitter.

Content Moderation

A question we often hear when working with a client is, “how can Drupal help build a publishing workflow that works for my team and business?"

Drupal 8 marked a big step forward for creating flexible editorial workflows. Building on Drupal 8's support for content moderation workflows, Rain comes pre-configured with a set of Workflow states. The term “states” refers to the different statuses your content can have throughout the publishing process - the four statuses available by default are “Draft”, “Needs Review”, “Published” and “Archived.” They can be easily enabled for any content type. As with everything in Drupal, these states and workflows are highly configurable. 

Once enabled, using content moderation in Drupal 8 is straightforward. After you save a piece of content, initially it will default to the “Draft” status which will remain unpublished. The “Review” status also preserves the unpublished status until the current edits get published. What’s great about Workflow in Drupal 8 is that you can make updates on a published piece of content without affecting the published state of that content until your changes are ready to be published. The video below demonstrates how to enable workflow and see draft updates before they are published.

To review any content currently in a workflow state you can click on the “Moderated Content” local task which is visible from the main Admin content screen (see below).
 

​​

Revisions

As a best practice, we recommend enabling revisions for all content. This allows editors to easily undo a change made by mistake and revisions keeps a full history of edits for each node. By default, all of Rain’s optional content features have revisions enabled by default. As illustrated below once you have made a save on a piece of content, the “Revisions” tab will appear with options for reviewing or reverting a change.

Media Library

Coming soon to Drupal core is an overhauled Media library feature. In the meantime, Drupal contrib offers some very good Media library features that are pre-configured in Rain. The Rain media features are integrated with most image fields including the “thumbnail” field on all content type features that ship with Rain.

The video below demonstrates two notable features. First is the pop-up dialog that shows editors all media available to choose from within the site. Editors can search or browse for an existing image if desired. Second is the drag-and-drop file upload which lets the editor user drag an image onto the dialog to immediately upload the file. 

 

WYSIWYG Media

Media is commonly embedded within the WYSIWYG editor in Drupal. Rain helps improve this experience by adding a button which embeds the Media library feature to be used within WYSIWYG. The key difference between the Media library pop-up you see on fields versus the pop-up you see within WYSIWYG is that here you will have an option to select the image style. The video below illustrates how this is done.

 

WYSIWYG Linkit

Another WYSIWYG enhancement that ships with Rain is the integrated “Linkit” module that gives users an autocomplete dialog for links. The short video below demonstrates how to use this feature.

Content Scheduling

A common task for content editors is scheduling content to be published at a future date and time. Rain gives authors the ability to schedule content easily from the content edit screen. Note that this feature will override the Workflow state so this should be considered when assigning user roles and permissions. The screenshot below indicates the location of the “Scheduling options” feature that appears in the sidebar on node edit pages.


Clean Aliases

Drupal is usually configured with the ability to set alias patterns for content. This will create the meaningful content “slugs” visitors see in the browser which also adheres to SEO best practices. Rain’s approach is to pre-load a set of sensible defaults that get administrators started quickly. The video below demonstrates how an admin user would configure an alias pattern for a content type.

XML Sitemap

By default, the Rain distribution generates a sitemap.xml feed populated with all published content. For editors, it can be important to understand how to exclude content from a sitemap or update the priority for SEO purposes. The screenshot below indicates where these settings live on the node edit page.

Metatag Configuration

The default configuration enabled by the Rain install profile should work well for most sites. Metatag, a core building block for your website’s SEO strategy, is also enabled for all optional content features that ship with the Rain distribution. To update meta tags settings on an individual piece of content, editors can simply edit the “Meta tags” area of the sidebar on the edit screen (see below).

Google Analytics

Enabling Google Analytics on your Drupal website is a very simple process. The Rain distribution installs the Google Analytics module by default but the tracking embed will not fire until an administrator has supplied a “Web Property ID.” The Google Analytics documentation shows you where to find this ID. To navigate to the Google Analytics settings page, look for the “Google Analytics” link on the main admin configuration page. Most of the default settings will work well without change and the only required setting is the “UA” ID highlighted below.

Enabling Content Features

Rain comes with many optional content features that can be enabled at any time. This includes content types, vocabularies, paragraphs, search and block types. Enabling a content feature will create the corresponding content type, taxonomy, etc. that can then be further customized. Any paragraph feature that is enabled will be immediately visible on any Rain content type that has enabled. Watch the video below to see an example of how to enable these features.

Wrapping Up

Mediacurrent created Rain to jump-start development and give editors the tools they need to effectively manage content. All features that ship with Rain are optional and highly configurable. We tried to strike a balance of pre-configuring as many essential modules as possible while still allowing site administrators to own the configuration of their Drupal site.

In the next tutorial, we will “pop open the hood” for Drupal developers to explain in technical detail how to build sites with Rain.

Categories: Drupal

Lullabot: Lullabot Podcast: Talking Continuous Integration

Planet Drupal - 18 July 2019 - 8:06am

Mike and Matt gather a fleet of Lullabots to talk the ins and outs of continuous integration (CI) in 2019.

Tools and Services mentioned in this episode:
  • Prettier - Code formatter

  • CircleCI - Continuous Integration service

  • Tugboat - Full website with every pull request

Categories: Drupal

wishdesk.com: Registration Confirm Email Address: simple module for Drupal

Planet Drupal - 18 July 2019 - 5:02am
We love to say that Drupal has modules for absolutely everything. Some modules are simple but still important because they cover specific details in the website’s work. They are like the missing pieces of the puzzle that makes your website more user-friendly, secure, reliable, and so on. One of them is Registration Confirm Email Address, which that we will describe today.
Categories: Drupal

OSTraining: Control User Access to Restricted Pages in Drupal 8 with Rabbit Hole

Planet Drupal - 18 July 2019 - 2:38am

Sometimes, you would want to restrict access to certain pages on your site to users who do not have a specific role. You would want users to upgrade to a paid plan. Or you would just want to collect some more information from them.

The Rabbit Hole module controls what should happen when a user clicks the link to the entity or enters a URL in the address bar. It redirects such users to another page in the site.

The Rabbit Hole module works with different types of entities. They could be nodes, users, taxonomy terms and files, to name a few.

This tutorial will explain the basic usage of this module. Let’s start!

Categories: Drupal

Social LMS Quiz

New Drupal Modules - 18 July 2019 - 1:43am

The module adds quizzing functionality to Drupal and Social LMS.

Categories: Drupal

Automatic Mail

New Drupal Modules - 18 July 2019 - 12:46am

The Automatic Mail module automatically send email to selected node type and specific user role. This module will send email after cron run.

Categories: Drupal

Microserve: 5 steps for a successful integration project

Planet Drupal - 18 July 2019 - 12:22am
5 steps for a successful integration project Ashley George Thu, 07/18/2019 - 07:22

At Microserve we're always ambitious about the solutions that we design and develop from scratch, but we're also conscious that there's no point in 'reinventing the wheel' when perfectly good solutions already exist. Our clients usually have third-party systems that they rely on for all kinds of business-critical services like CRM, marketing automation, authentication, recruitment and lots more. It's our job as technical architects to understand where those systems end and where the system that we’re developing begins. Crucially, we need to plan how data flows between those systems to get them working seamlessly together. In other words: how to integrate the systems.   

Categories: Drupal

Paragraphs Sets Alter

New Drupal Modules - 17 July 2019 - 10:45pm

Allows modification of the Paragraphs Sets selection/add dialog. More specifically, allows other modules to limit and/or extend which paragraphs sets are available on a paragraphs field. Primary use case is something like Paragraphs Selection.

Categories: Drupal

Premium Updates

New Drupal Modules - 17 July 2019 - 4:47pm

A module to display updates for premium modules.

Categories: Drupal

Palantir: DrupalCamp Colorado 2019

Planet Drupal - 17 July 2019 - 3:52pm
DrupalCamp Colorado 2019 August 2 - August 4, 2019 brandt Wed, 07/17/2019 - 17:52 King Center, Auraria Campus, Denver, Colorado DrupalCamp Colorado 2019 (Official Site)

Palantir is excited to return to Denver as a sponsor for DrupalCamp Colorado 2019, featuring a keynote from our CEO, Tiffany Farriss. Tiffany will be discussing the role of organizational culture and open source projects like Drupal in the success of tech companies. We hope to see you there!

  • Location: TBD
  • Date: August 3rd, 2019
  • Time: 9 AM - 10 AM MDT
Wed, 07/17/2019 - 12:00
Categories: Drupal

Lullabot: How to Enforce Drupal Coding Standards via Git

Planet Drupal - 17 July 2019 - 11:25am

The Drupal community maintains its own evergreen coding standards that differ from those of the broader PHP community (e.g., PSR-2). It's encouraged to pore through the standards line-by-line and memorize each for perfect real-time compliance, but for those with better things to do, fear not! The standards will come to you.

Categories: Drupal

Security advisories: Drupal core - Critical - Access bypass - SA-CORE-2019-008

Planet Drupal - 17 July 2019 - 9:05am
Project: Drupal coreDate: 2019-July-17Security risk: Critical 17∕25 AC:None/A:None/CI:Some/II:Some/E:Theoretical/TD:DefaultVulnerability: Access bypassCVE IDs: CVE-2019-6342Description: 

In Drupal 8.7.4, when the experimental Workspaces module is enabled, an access bypass condition is created.

This can be mitigated by disabling the Workspaces module. It does not affect any release other than Drupal 8.7.4.

Drupal 8.7.3 and earlier, Drupal 8.6.x and earlier, and Drupal 7.x are not affected.

Solution: 

If the site is running Drupal 8.7.4, upgrade to Drupal 8.7.5.

Note, manual step needed. For sites with the Workspaces module enabled, update.php needs to run to ensure a required cache clear. If there is a reverse proxy cache or content delivery network (e.g. Varnish, CloudFlare) it is also advisable to clear these as well.

Reported By: Fixed By: 
Categories: Drupal

OSTraining: How to Embed a Google Docs Viewer in Your Drupal 8 Site

Planet Drupal - 17 July 2019 - 8:07am

The Embedded Google Docs Field allows the site administrator to change the display of normal file fields, making them viewable directly on the node with the help of the Google Docs Viewer.

This tutorial will explain the usage of this module through an example.

Let’s start!

Hint: Google has to be able to locate your site on the web, in order to embed the viewer. This module will not work in a local environment.

Categories: Drupal

Pages

Subscribe to As If Productions aggregator - Drupal