I encountered the issue once, which seemed to stem from a cache problem. It occurred while I was attempting to reproduce a different issue. The problem arose when I ran 'drush updb' without clearing the cache.
I can confirm this issue. Due to it is currently also not possible to create new groups.
The provided patch resolves this problem.
Not entirely. The plugin_id is requested in additional places, such as in the related issue mentioned by slowflyer.
Thanks. Based on the response to the other issue I commented on, I thought it might be a specific problem with my installation.
I was able to reproduce the bug and added steps to reproduce to mentioned issue.
Added steps to reproduce
this issue has nothing to do with it.
Indeed, seems so. If i rollback the line a different error gets thrown.
Can you please add error trace or specify which method is throwing this error?
I created a new issue: Group plugin_id not found π Group plugin_id not found Active
corn696 β created an issue.
Thank you for the response. The initial installation was on OS 7.
The error occurs when updating from OS 12.4.5 to OS 12.4.6, which introduces the change mentioned in this issue. The condition was updated to use gc.plugin_id
instead of gc.type
.
The group version should be locked by OS? Currently, itβs Group 8.x-1.6 (1.6.0).
It seems that the group_relationship_field_data
table does not exist at all.
After the update I get the following error:
Drupal\Core\Database\DatabaseExceptionWrapper: Exception in Benutzer Gruppen[groups]: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'gc.plugin_id' in 'where clause': SELECT "groups_field_data"."created" AS "groups_field_data_created", "groups_field_data"."label" AS "groups_field_data_label", "groups_field_data"."id" AS "id" FROM "groups_field_data" "groups_field_data" INNER JOIN "groups" "groups" ON groups_field_data.id = groups.id WHERE ("groups"."id" IN (SELECT "gc"."gid" AS "gid" FROM "group_content_field_data" "gc" WHERE ("gc"."entity_id" = :db_condition_placeholder_0) AND ("gc"."plugin_id" LIKE :db_condition_placeholder_1 ESCAPE '\\'))) AND ("groups_field_data"."default_langcode" = :db_condition_placeholder_2) ORDER BY "groups_field_data_created" DESC, "groups_field_data_label" ASC LIMIT 3 OFFSET 0; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => %membership% [:db_condition_placeholder_2] => 1 ) in main() (Zeile 19 in /os/html/index.php).
corn696 β created an issue.
Maybe related to latest CORE SA?
Drupal core - Moderately critical - Improper error handling - SA-CORE-2024-002 β
I also run into this if i try to update from latest OS11 to latest OS12.
Following comment pointed me in the right direction:
https://www.drupal.org/project/social/issues/3400861#comment-15376503 β
The mentioned update hook is not present in the lastest OS12 version anymore. It got removed in OS 12.2.0
So i had to update to OS 12.1.5 first.
I want to do some more testing
That would be good.
and eventualy also send the webform settings validation in plain js.
Do you mean the validation on the config form?
Take a look at Use form validation instead of custom js for exclusion dates and time intervals π Use form validation instead of custom js for exclusion dates and time intervals Needs review
Should consideration be given to using translated weekdays for the time intervals?
If no, it should be mentioned that it is necessary to use English weekdays.
Corn696 β created an issue.
I worked on the vanilla js branch.
I tried another approach and the code now removes the month without available slots from the select list.
If this would an option we would not need the "no slots available" message anymore or?
However the code still needs some work. I am not so familiar with the core/once implementation.
If two webforms are placed on a page with the same booking field id the second form does not work.
DamienMcKenna β credited Corn696 β .
From https://www.drupal.org/project/csv_serialization/issues/3344110 π CsvEncoder::encode must be compatible with Symfony\Component\Serializer\Encoder\EncoderInterface::encode Fixed
This is due to the difference in
EncoderInterface::encode()
signatures between Symfony 4.4 (D9) and Symfony 6.2 (D10).
So this release is not compatible with D9
What is the plan to handle this on this module?
Here is a patch as a workaround for users that are still on D9
Corn696 β made their first commit to this issueβs fork.
Seems to work without and with blur now thx :)
Yep happens.
Temporary solution till we fix the JS stuffs:
- Try enabling Add is-b-visible class at Blazy UI.
Thanks, already tried it. Does not work.
But I will just temporarily revert the CSS changes for my site. Blur is not in use on our site.
Corn696 β created an issue.
The cause for this, is the change introduced by following issue:
PubMed abst_e field - contains basic html (3079282) β
The abstract fields (english and french) have been changed changed from text (long) to text (formatted, long).
It seems that something is missing in the update hook for the english abstract field.
You should not turn aggregation off on production.
You could edit the files directly in the social blue theme. But you would need to apply your changes if an update overrides your changes.
Another option would be to create a custom module with custom css files. You can define libraries in a libraries.yml and attach these libraries with a hook in the .module or with the twig function attach_library() on the pages where you need those changes or globally.
The bibcite entity is a custom entity type.
You can configure it under structure -> bibliography
/admin/structure/bibcite
List of all types
/admin/structure/bibcite/reference/settings/types
If you want to create a custom view of references choose reference instead of content.