🇬🇧United Kingdom @tce

I think it was a PHP setting in the end. I'd changed the command line to use PHP 8.2 instead of 8.1, but I hadn't increased the settings. For example, I changed memory_limit from 128M to 512M and the database backup via Drush now works

I tried upgrading core after reading this 👉 https://www.drupal.org/project/drupal/issues/3443108 📌 Optimize AssetResolver caching Fixed but I still get the issue with Drupal version 10.3.6

I have started experiencing this, it might be the same issue as it's a fairly recent bug for me.

AJAX on forms stop working and work again after clearing cache. I can replicate the issue by following the below steps...

1) Clear the Drupal cache
2) Visit the page the form is on but have the ajax related params in the URL. E.g. https://www.mysite.com/form?ajax_form=1&_wrapper_format=drupal_ajax&_wrapper_format=drupal_ajax
3) Visit the form page as usual, AJAX is now broken

It seems that in step 2, caching for the form is happening, but it's caching empty values. It's caching empty values in the cache_data table. The cid is like js:theme_name:en:xxxx

I'm no expert, but to me the issue is the way the AssetResolver::getJsAssets creates the Cid name. It creates the same Cid name, even if the cache data is an array of empty/false values

I finally got this working using the code below. It seems like the selector isn't there in the code example, so wrapping in a <div class="signature"> was needed. Also, the signature_data element selector is wrong in the example, the id is signature-data and not signature_data

<?php
    $form['signature'] = [
      '#type' => 'container',
      '#prefix' => '<div class="signature">',
      '#suffix' => '</div>',
    ];
    $form['signature']['signature_field'] = [
      '#type' => 'signature',
    ];
    $form['signature']['signature_data'] = [
      '#type' => 'textarea',
      '#attributes' => [
        'id' => ['signature-data'],
        'class' => [
          'signature-data',
        ],
      ],
    ];
?>

I have installed and enabled this module, but when I put the below code into a custom form it does nothing - I also noticed the library assets are not loaded, so I feel like it's not doing anything. Is there anything else I need to do to make this work?

<?php
    $form['signature_field'] = [
      '#type' => 'signature',
    ];
    $form['signature_data'] = [
      '#type' => 'hidden',
      '#attributes' => [
        'id' => ['signature_data'],
      ],
    ];
?>

Do we need to use once? For example...

      $(once('myId', '[data-bs-toggle="tooltip"]')).each(function() {
        var tooltip = new bootstrap.Tooltip(this);
      });

Otherwise won't the function keep triggering multiple times with AJAX?

I'm having a similar issue. I am using REST to post content from one site to another.

I upgraded Drupal from 9 to 10 and I believe the user I use for REST is using an older password scheme, so this is why user save is being triggered when I try to POST some data to the site. I get the error:

Error: Undefined constant "Drupal\Core\Entity\SAVED_UPDATED" in Drupal\Core\Entity\ContentEntityStorageBase->doSave() (line 704 of /app/web/core/lib/Drupal/Core/Entity/ContentEntityStorageBase.php)

I'm getting this error for Drupal 10.1.6, Redirect 8.x-1.9 😬

Drupal\Core\Database\DatabaseExceptionWrapper: Exception in Redirect[redirect]: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'FROM "redirect" "redirect" ORDER BY "unknown" ASC LIMIT 50 OFFSET 0' at line 3: SELECT FROM "redirect" "redirect" ORDER BY "unknown" ASC LIMIT 50 OFFSET 0; Array ( ) in main() (line 19 of /home/mysite/public_html/web/index.php).

I get the error:

Message = JSMinPlus had a possible error minifying: themes/contrib/seven/js/nav-tabs.js. Using uncompressed version. Error: Parse error: Unexpected token; token : expected in file '[inline]' on line 39

Any solutions for this?

Thanks bjc2265 specifiying the version worked

composer require 'drupal/bootstrap_horizontal_tabs:2.0.4'

tce → created an issue.

This module is the only thing blocking me upgrading to Drupal 10.

How can bypass the composer "Your requirements could not be resolved" error just to install and then patch the module?

@gayathri09: Putting the below into my settings.local.php file worked

$settings['locale_custom_strings_en'][''] = [
  'Generated by the <a href="@link-xmlsitemap">Drupal XML Sitemap module</a>.' => '',
];