Willkommen in meinem Blog, frohes Lesen! ツ

Do you see one of the following errors in your Drupal 8+ Status Report? Mismatched entity and/or field definitions The XXX field needs to be updated. The XXX field needs to be uninstalled. This is caused by mismatch in the field (storage)

The Drupal Form API (FAPI) #tree property is helpful and needed when using form containers like details, fieldset or others. Also it's helpful if you need to nest form values and also want to nest their results. On the othe hand it becomes

Drupal Form API doesn't offer a native HTML type="reset" button known from the W3C: https://www.w3.org/TR/2012/WD-html-markup-20121025/input.reset.html So if you ever need one, this might be a good starting point in Drupal 8+: 'reset' => [

How to reload the page after a successful Drupal AJAX Form submit? You many run into this question, for example, if you're using complex AJAX Forms and as a result so many things change, that you need to reload the current page or form

Just some notes on triggering an AJAX Form submit programmatically in Drupal 8+: AJAX properties can be found here, but the list was not complete. Especially useful is to know about ''disable-refocus' => TRUE' property, to prevent from

Knowing the old logics from Drupal 7, where you could place a "translations" folder into your custom modules, containing the language .po files, the situation is a bit different for Drupal 8+: You can find the related information (bit

As it sadly took me some time to find out and it's not very well documented, here's how you close a Drupal 8+ dialog (in this case the Off-Canvas) using JavaScript: Drupal.dialog(document.getElementById('drupal-off-canvas')).close(); You

Should you encounter an error like The specified #ajax callback is empty or not callable form Then presumably you're using something like this: '#ajax' => [ 'callback' => '::updateFormAjaxCallback', 'wrapper' => 'layout-wrapper', ], or an

If you're using the wonderful Drupal Commerce, you may run into situations, where the product prices should not be shown (yet), e.g. if you're just preparing the shop or orders should just be requests first. Sometimes you'd also want to

Adding a captcha to a Drupal Commerce Checkout step isn't as simple as expected, as adding it via "Captcha points" shows the captcha on any Checkout step. So you need to add a little snippet in a custom module instead: /** * Implements hook