shagel → created an issue.
shagel → created an issue.
Is there any solution here to avoid this ? I get this too.
I have a multisite setup (2 sites), site one has a quiz content type and a field that references a quiz_answer paragraph.
Since the site 2 doesnt have that content type and doesnt have the paragraph, i added this to full split.
I do a
drush @project1_alias si --existing-config -y
than
drush @project1_alias cex
and i get this notice
[notice] The Quiz answer bundle (entity type: paragraph) was deleted. As a result, the field_paragraphs entity reference revisions field (entity_type: node, bundle: quiz_question) no longer specifies a specific target bundle. The field will now accept any bundle and may need to be adjusted.
When i login to the backend everything seems fine.
I had this error message when i created a new FiledType.
I chose names for columns in the schema (example: this_is_an_example_schema_column_name) that were too long.
When i wanted to create the field in the backend with name mycustom_options (example: field_mycustom_options) than i got that error.
But when i created the field in the backend with name foo (field_foo) it worked.
The reason for that was, that the field name and the column names i chose in my schema were combined in the database as column name.
Example:
- field_mycustom_options_this_is_an_example_schema_column_name
- field_foo_this_is_an_example_schema_column_name
so - the problem was, that the resulting column name was too long for drupals column name restrictions and drupal obviously refused to create the schema with that nice message.
Solution for me was to shorten the column names in my Custom FieldType.
I had this error message when i created a new FiledType.
I chose names for columns in the schema (example: this_is_an_example_schema_column_name) that were too long.
When i wanted to create the field in the backend with name mycustom_options (example: field_mycustom_options) than i got that error.
But when i created the field in the backend with name foo (field_foo) it worked.
The reason for that was, that the field name and the column names i chose in my schema were combined in the database as column name.
Example:
- field_mycustom_options_this_is_an_example_schema_column_name
- field_foo_this_is_an_example_schema_column_name
so - the problem was, that the resulting column name was too long for drupals column name restrictions and drupal obviously refused to create the schema with that nice message.
Solution for me was to shorten the column names in my Custom FieldType.
To hide only the first h4 label but not the h4 labels of the subtables solution could be
/* Hide paragraphs field label in table header. */
.field--widget-paragraphs .paragraphs-tabs-wrapper table.field-multiple-table:first-of-type th {
background: var(--gin-bg-layer);
}
.field--widget-paragraphs .paragraphs-tabs-wrapper table.field-multiple-table:first-of-type thead th.field-label h4 {
display: none;
}
.field--widget-paragraphs .paragraphs-tabs-wrapper table.field-multiple-table:first-of-type table thead th.field-label h4 {
display: block;
}
Hey,
no we dont use the hooks anymore - it was just to get it compatible with Drupal 10
- saw that in the upgrade status module and just fixed it.
shagel → created an issue.
shagel → created an issue.
We used 2904705-128.patch with version 1.16 but with 1.17 it doesnt apply so i created a new one 2904705-128-1-17.patch
shagel → created an issue.
There was a security update [Security-news] GraphQL - Moderately critical - Cross Site Request Forgery - SA-CONTRIB-2023-051
i changed the patch, so that i can be applied but needs to be reviewd.
shagel → created an issue.
@swatidhurandhar
in our case (in Safari only !):
we install the redirect module
https://www.drupal.org/project/redirect →
we add a redirect to a node /admin/config/search/redirect/add
we go to edit the node, open the sidebar -> button is not clickable.
PS: my fix in a custom css was
#edit-url-redirects .gin-layer-wrapper {
position:relative;
}
#edit-url-redirects .gin-layer-wrapper .gin-table-scroll-wrapper {
position:relative;
z-index:1;
}
#edit-url-redirects ul.action-links {
position:relative;
z-index:5;
}
shagel → created an issue.
shagel → created an issue.
alexpott → credited shagel → .
shagel → created an issue.
shagel → made their first commit to this issue’s fork.
Hello, i made a branch of 2.0.x-dev.
I included the following patches / issues in it:
https://www.drupal.org/project/bridtv/issues/3266189 →
https://www.drupal.org/project/bridtv/issues/3229355 →
https://www.drupal.org/project/bridtv/issues/3241677 →
https://www.drupal.org/project/bridtv/issues/3218400 →
Also i fixed issues that where showing up in the upgrade status. And fixed phpcs errors i got.
see bridtv-3387026/2.0.x Comparecompare MR !7
shagel → created an issue.
shagel → made their first commit to this issue’s fork.
shagel → created an issue.
sidharth_soman thanks for the fast response!
I think thats what we need but its not only one plugin - sorry my description was a bit misleading in this case.
Basically all of the Plugins are affected - i created a new patch for that.
shagel → created an issue.
shagel → created an issue.