🇨🇦Canada @gwvoigt

+1 for this, that would be very helpful and probably a very common use case

Previous patches are not working with 8.x-1.5, so generated new patch file.

also +1 to release this fix... thank you!

I was having the issue on 10.2.6. On layout builder edit mode, I was clicking "add section", then closing the dialog. Then if I clicked "add block", it would trigger the ajax error. I've updated to 10.2.7 and applied the patch, it fixed my issue. Thank you for the patch!

Added a commit to make it compatible to D10 since QueryInterface::accessCheck is now required.

gwvoigt → made their first commit to this issue’s fork.

Directly accessing the 'styles' index in $this->getConfiguration()['properties']['styles'] (in ListPlugin.php) was throwing me warnings when editing nodes, so I'm using isset() to check if the index exists before accessing it.

gwvoigt → made their first commit to this issue’s fork.

Same issue as #12, the bulk generate works if I use whatever/[node:menu-link:title] but it fails if I use [node:menu-link:parents:join-path]/[node:menu-link:title]. I've updated pathauto and token module to the latest version but still having the same issues.

I'm using patch 42, but something is off:

In /admin/config/content/formats/manage/full_html I have the Autoplay - Autoplay the videos for users without the "never autoplay videos" permission. Roles with this permission will bypass this setting. set to Off.

When I edit a ndoe and add a video it has Autoplay marked as On, ant it should be off:

I could fix it in a hook_preprocess_entity_print:

$css = '
';
$variables['entity_print_css'] = Markup::create($css);

It's not ideal but it works, none of the patches provided worked for me unfortunatelly.

Same as @spiderman, I'm using patch #44 from https://www.drupal.org/project/entity_print/issues/2884806 ✨ Support multiple view modes for a given library Needs review (Support multiple view modes for a given library) and this patch conflicts with it. I tried adapting the patch locally to work with the patch from this current issue but no luck. Also tried @spiderman's fork (Merge branch '2884806-support-multiple-view-modes' into develop commit) but no luck either. I'm on:

Drupal 10.1.4
entity print 8.x-2.13
using the patches:
https://www.drupal.org/files/issues/2023-01-21/support-multiple-view-mod... →
https://www.drupal.org/files/issues/2023-07-10/entity_print-dompdf_page_... →

Fixing my previous patch, to be used with D10

One thing I'm not following is that this patch makes it D10 compatible but it has a dependency on "drupal/context": "^4.1" which is not D10 compatible and it does not have a patch to make it D10 compatible so how are people using this patch on D10? I mean it's compatible but can you actually be on D10 without updating context to ^5.0 as well?

Rerolled the patch to be used with https://www.drupal.org/project/entity_embed/issues/3272732 ✨ Drupal 10 & CKEditor 5 readiness Fixed with patch https://www.drupal.org/files/issues/2023-03-23/3272732-67-COMPOSER-ONLY-... →

Rerolled the patch to be used with https://www.drupal.org/project/entity_embed/issues/3272732 ✨ Drupal 10 & CKEditor 5 readiness Fixed with patch https://www.drupal.org/files/issues/2023-03-23/3272732-67-COMPOSER-ONLY-... →

Says it's in "Needs review" but there are no patches or MR information

Adding a patch that can be applied to D10.

Is there a patch that works with D10?

Thank you! I'm on 9.5.10 and still having issues when aggregation is on. In random instances the ckeditor don't load properly.

Does it work with 9.5.10? None of the patches apply to 9.5.10

+1 for this to be merged

Patch 17 applies correctly but it causes an error in QueueWorker.php in getStashedResultCount() function because it removes a + operator that shoudl stay there, otherwise it returns (int)(int) while should be (int)+(int), causing php error: Value of type int is not callable. Uploading a patch that fix that.

Uploading just so I can apply to 8.x-3.0-beta4

@kristiaanvandeneynde Thank you for your detailed reply. We are going to try to undo the patch and upgrade to 2.0.

@kristiaanvandeneynde If I'm in Group 1.4 and I'm using this patch, but it want to update to Group 1.5, what is the workaround? The patches do not work with 1.5 and this issue https://www.drupal.org/project/group/issues/3292139 → is for Group 2.0.

Same here, looking to upgrade a website to D10, so group will have to be upgraded to 2.0. Runnin into the same conflict with composer

Modified patch from #25 to address issues from #28

gwvoigt → created an issue.

Thanks chOP, I'm adding anew patch with your suggestion

I'm on 8.x-5.2. patch #6 does not apply. Patch #5, #4 and #3 applies but it doesn't solve my issue. When I select a date via datepicker it does not trigger an autosubmit. I have "Enable auto-submit" and "Exclude Textfield" both ON.

The patch should work with 2.1.0 as well.

I'm having the same issues on 3.1.0, this patch should check for the array key that is throwing the error before accessing it.

Last patch gives me:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /batch?id=410&op=do_nojs&op=do
StatusText: parsererror
ResponseText: Error: Call to undefined method Drupal\paragraphs\Entity\Paragraph::getTitle() in Drupal\scanner\Plugin\Scanner\Paragraph->search() (line 115 of /app/web/modules/contrib/scanner/src/Plugin/Scanner/Paragraph.php).

Last patch gives me:

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /batch?id=410&op=do_nojs&op=do
StatusText: parsererror
ResponseText: Error: Call to undefined method Drupal\paragraphs\Entity\Paragraph::getTitle() in Drupal\scanner\Plugin\Scanner\Paragraph->search() (line 115 of /app/web/modules/contrib/scanner/src/Plugin/Scanner/Paragraph.php).

+1 for #12, fixed my issue.

Not working for me... my Search view loads fine, then I select a facet, the results are updated correctly with ajax. I unselect the facet and the results are not updated... I'm using the dev version and I have this patch applied

I got around this issue removing the simplesamlphp_auth module via composer, updating core to 10 and then requiring the simplesamlphp_auth module again. Closing the issue.

gwvoigt → created an issue.

Same error as #27

I case you are using https://www.drupal.org/project/entity_print/issues/2823430#comment-13909604 ✨ Adding page numbers in footer in pdf Active , this patch will fail. So here's one that will work with that other issue combined

Thanks, patch from #41 working on 3.x for me

gwvoigt → made their first commit to this issue’s fork.

Thanks Sergey Gabrielyan, I'm using your patch #33 and it fixed the issue here using Group 3.x

gwvoigt → created an issue.

With Group module having its 3.x available as a release candidate and being recommended on fresh installs, is there any plan to have a branch of this project to target compatibility with Group 3.x? I assume not all of the sites using this module that are on group 1.x are going to upgrade right away. There are some issues regarding 3.0 compatibility that were addressed with patches however it's very unlikely for it to be commited since it would break on sites that are still on Group 1.x.

gwvoigt → created an issue.

This patch is causing an issue when I create a node and add to a group using /node/add route:

The website encountered an unexpected error. Please try again later.
TypeError: Drupal\Component\Utility\NestedArray::getValue(): Argument #2 ($parents) must be of type array, null given, called in /app/docroot/core/lib/Drupal/Core/Field/WidgetBase.php on line 426 in Drupal\Component\Utility\NestedArray::getValue() (line 69 of core/lib/Drupal/Component/Utility/NestedArray.php).
Drupal\Component\Utility\NestedArray::getValue(Array, NULL) (Line: 426)
Drupal\Core\Field\WidgetBase->flagErrors(Object, Object, Array, Object) (Line: 268)
Drupal\Core\Entity\Entity\EntityFormDisplay->flagWidgetsErrorsFromViolations(Object, Array, Object) (Line: 255)
Drupal\Core\Entity\Entity\EntityFormDisplay->validateFormValues(Object, Array, Object) (Line: 762)
Drupal\entitygroupfield\Plugin\Field\FieldWidget\EntityGroupFieldWidgetBase->elementValidate(Array, Object, Array)
call_user_func_array(Array, Array) (Line: 282)
Drupal\Core\Form\FormValidator->doValidateForm(Array, Object) (Line: 238)
Drupal\Core\Form\FormValidator->doValidateForm(Array, Object) (Line: 238)
Drupal\Core\Form\FormValidator->doValidateForm(Array, Object) (Line: 238)
Drupal\Core\Form\FormValidator->doValidateForm(Array, Object, 'node_page_form') (Line: 118)
Drupal\Core\Form\FormValidator->validateForm('node_page_form', Array, Object) (Line: 588)
Drupal\Core\Form\FormBuilder->processForm('node_page_form', Array, Object) (Line: 320)
Drupal\Core\Form\FormBuilder->buildForm(Object, Object) (Line: 73)
Drupal\Core\Controller\FormController->getContentResult(Object, Object)
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 564)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 159)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 265)
Drupal\shield\ShieldMiddleware->bypass(Object, 1, 1) (Line: 132)
Drupal\shield\ShieldMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 23)
Stack\StackedHttpKernel->handle(Object, 1, 1) (Line: 709)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

I thought it was permission related but I gave the editor role full permissions in both global and group permissions and that error would still happen. I have no issues when I create a node using the /group/4/content/create/group_node route. In this case, my editor role is a mapped to the global editor role.

Group 3.x has different naming pattern in its machine names for 2 entity types so I added a condition to account for the new version as well when checking if it is a content form or not.

Not sure if it's related since I'm not using Group Term or Groupt Term Menu.

I'm using the patch from #5 and still getting an inconsitency when comparing the node add form to the group node add form:

The sidebar does not render correctly, it renders at the bottom of the form, and the toggle doesn't work either

Thank you kristiaanvandeneynde, I'm testing thie patch on 3.0.x and so far it solved the issue with the members view list.

Just saw that this is a duplicate of https://www.drupal.org/project/group/issues/3319432 🐛 group admin with insider scope & global role can't list group members Fixed

Happening in my site as well with 3.x.

gwvoigt → created an issue.

I'm on Group v3, I've installed this module, I ran into the error, coudl not apply the patches and now I can't uninstall and remove this module.

I think I finally could uninstall the module with no issues. In my site, I've started with 8.x, upgraded to 2.0 then 3.0. Maybe I missed database update sor something went wrong in the update. I could uninstal after downgrading it to 2.0, and then removing the module via composer.

I'm having the same issue. With drush pmu group gnode I get:

In EntityTypeManager.php line 139:
The "group_content" entity type does not exist.

Tried #4 suggestion with no luck