Or maybe display a message when the trimming happens so at least the user knows that the result might not be complete? Or both?
I've added a fix which pulls each field's config to find out if there is a limit of characters set and then truncate the response to fit in.
Other improvements can be done with the AI prompting to ask for a character limit on the response amongst other things but for now I believe this should fix the error.
marcus_johansson → credited unqunq → .
Updating #36 ✨ Add time to views date filter Postponed to work with Drupal 10.3.2
Might be related to this: https://www.drupal.org/project/group/issues/3363130 🐛 Database update errors when upgrading from 1.5 to 2.1 pluginid not found Active
I think this is the history of when the update has been created https://www.drupal.org/project/group/issues/3278778 →
I have the same issue, running updates with drush 12.5.2 I get the same error while running the update directly in browser goes well.
I'm seeing this issue when trying to run a hook_update. In my hook I only check the existence and create some simple taxonomy terms. No logger is used.
I get:
In BatchStorage.php line 143:
Serialization of 'Closure' is not allowed
My hook function code:
$vocabulary_id = 'designation';
$term_names = ['term1', 'term2'];
foreach ($term_names as $term_name) {
// Check if the term already exists.
$existing_terms = \Drupal::entityTypeManager()->getStorage('taxonomy_term')->loadByProperties([
'name' => $term_name,
'vid' => $vocabulary_id,
]);
if (empty($existing_terms)) {
// Create a new term if it doesn't exist.
$term = Term::create([
'name' => $term_name,
'vid' => $vocabulary_id,
]);
// Save the term.
$term->save();
}
}
Hi, I'd like this merged please. My employer needs this done in order to approve the use of this module in Drupal 10. Thank you.
We have this patch in production and working well.
We also have updated the return type, can I update the patch to include those?
e.g.
- public static $modules = [
+ public static array $modules = [
Can we add the update of core_version_requirement as well to this patch or is that handled differently?
I had the same issue and my solution was to add ->id() to the comparison. I'm not sure if it will suffice but it got me going in my case:
if ($qra->id() == $this->id()) {
It comes up in multiple places.
I'm using a custom plugin for source and the
plugin: entity:eventseries
for destination.
As a quick fix I did a hook_entity_insert to copy the uid from series to instance.
I came to this page as I was testing these modules for a new client. The email field coming up for an authenticated user is too much work for the user and opens to typing mistakes when the user just wants to register themselves.
In this case @MrPaulDriver's suggestion would work for us. I'll try to allocate time for this in the next month or so (we're only starting the project now so it can take some time before I get to it.)
Fixing grammar/rewriting content to be easier to understand.
I'm getting the same error and I am on PHP 7.4. I tried upgrading but my site still uses some dependencies which are not ready for PHP 8+ making this impossible to use.
If anyone wants to get this working on PHP 7.4 then here is an article about the property promotion in PHP 8. https://stitcher.io/blog/constructor-promotion-in-php-8
I haven't tested the actual functionality of the module past fixing this file so there could be a lot more PHP 8 related parts that need downgraded in order to make this work with PHP 7.4
So I guess we just need to follow @abarrio's suggestion 🐛 syntax error, unexpected 'private' (T_PRIVATE), expecting variable (T_VARIABLE) in ResponseSubscriber.php:29 Fixed .