Issues and Patches

Patches are a common thing when you work with Drupal. They are pieces of code that describes the changes between a before and after state of either a module or core. We commonly use patches to improve the code, add extra functionalities to a module or fix an existing issue. By applying the patch, the issue should no longer exist.

This item uses a few contributed Drupal modules that need to be patched for the theme to work as is designed. However, if you have purchased this item, you shouldn't worry about applying patches because the package includes already patched modules.

This document is for informational purposes only so that in the future if you update some of the modules below you should follow the module's issue, and you may need to apply a patch if the module maintainer does not have fixed the problem yet. If you use a composer managed version of the theme, you don't have to worry about applying patches. The patches are listed in the composer.json file, and they will be automatically applied when you perform an update on a patched module.


Drupal

issue: Form blocks rendered inside layout builder break save
patch: #66 - 2019-06-27/3045171-66.patch

issue: Drag-and-drop reordering doesn't work if the region content is nested in other elements
patch: #2 - 3062742_2.patch

issue: Real world rendering of a layout builder page is much slower with calls to ::filterPluginDefinitionsByContexts in SectionStorageManager::findByContext
patch: #5 - 3043319-5.patch

issue: Performance Degradation in Layout Builder and other places likely
patch: #20 - layout_builder_performance-2981889-20.patch


Poll

issue: Most Recent Poll - Question title is Displayed as Block Title
patch: #7 - question-title-is-displayed-as-block-title-2923946-8.x-1.x-dev-7.patch


Mailchimp

issue: Notice: Undefined property: stdClass::$size in mailchimp_insert_drupal_form_tag()
patch: #6 - suppress-size-notice-2936099-6.patch