🇩🇪Germany @Antonnavi

Hello yabikami,

User email verification module does not provide "real" additional User entity field which can be used by ECA module. It provides 2 extra (kinda virtual) fields on User entity display. So, the case which you asked about can not be implemented right now.

ECA module integration is still in progress in this https://www.drupal.org/project/user_email_verification/issues/3387439 ✨ ECA integration? Active issue.

Hello Sariga Raghunath,

As mentioned in comment above please provide more clean description of an issue & a proposed solution.
Also, module does not have a "hard" dependency from Rules module, see https://git.drupalcode.org/project/user_email_verification/-/blob/8.x-1.... line.

Hello yabikami,

I just tested locally with the latest module development branch (8.x-1.x) code version, Drupal 11.1.6, Easy Email 3.0.4 (with Easy Email Overrides enabled to override system user registration email template). I used [easy_email:recipient_uid:0:entity:verify-email] token inside template. And it works fully correctly.

The Easy Email module setup was done by this webinar https://www.youtube.com/watch?v=2pjFr3cf9uw video.

Please try again using this webinar video and module latest development version. If you'll still have this issue - provide step by step instruction how to make the same as your local setup and step by step instruction how to reproduce this issue.

This issue is already fixed in the development (8.x-1.x) branch.

Test implementation of this functionality was added into development (8.x-1.x) branch.

antonnavi → created an issue.

Please provide step by step instruction how you adding block in layout builder via lb_plus.

This issue was fixed on module DEV branch.

Hello Nick Abbott (sirclickalot),

I just tested latest DEV module version with latest stable Field Group 8.x-3.6 module version. I can not reproduce this issue.
Test again and if this issue still presented - please provide an instruction how to reproduce (including core/modules versions).

Hello Jay Huskins ( jayhuskins → ),

I tested this issue on current latest Drupal 11.0.6 core version and there is no such issue.
Please provide more information and steps how to reproduce this issue.

--
Best regards,
Anton

Hello all,

The code:

    if (!$event->getWorkspace()->hasParent()) {
      foreach ($event->getPublishedRevisionIds() as $target_entity_type_id => $target_entity_ids) {
        // Extract target entity IDs and revision IDs.
        $target_entity_ids_list = array_keys($target_entity_ids);
        $target_entity_revision_ids = array_keys($target_entity_ids);

        $this->deleteAssociations(NULL, $target_entity_type_id, $target_entity_ids_list, $target_entity_revision_ids);
      }
    }

which was committed to the core, there is a bug in this line:

        $target_entity_ids_list = array_keys($target_entity_ids);

The $target_entity_ids variable is an array where keys - revision IDs and values - entity IDs. So instead of:

        $target_entity_ids_list = array_keys($target_entity_ids);

should be:

        $target_entity_ids_list = array_values($target_entity_ids);

to get entity IDs instead of revisions.

Hello all here,

I had the same bug and fixed it in the way of adding additional cleanup on publication to Live workspace.
See details in attached patch file.

Hello all here,

Here is implementation of Batch usage on publishing (to Live workspace).

+

Thank you for help!

--
Best regards,
Anton

Hello all here,

Thank you for your help!

--
Best regards,
Anton

Hello all here,

Thank you for your help! Merged.

--
Best regards,
Anton

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

Hello all here,

Thank you for your help! Merged.

--
Best regards,
Anton

Hello all here!

Thank you for help!

Hello aharown07 → ,

Flag counter can be added in the template, as described by Anssi ( anderz → ) above.

--
Best regards,
Anton

Hello all here,

Thank you for your help! Merged.

--
Best regards,
Anton

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

Hello all here,

Thank you for your help! Merged.

--
Best regards,
Anton

Thank you for help! Fixed.

Hello all here,

Thank you for your help!

Hello sorlov → ,

Thank you for your help!

Hello all here,

Thank you for your help!

Hello all here,

Thank you for your help!

Hello all here,

Thank you for your help!

Hello all here,

Thank you for your help.
Changes were committed to the development branch.

Hello Daniel ( dsp1 → ) !

If attached patch solves your issue - it means you just need to set up user entity view mode (disable display of Email verified and Email verification date fields). And your problem will be solved without this patch.

--
Best regards,
Anton

Hello Gorka G. (gorkagr) → ,

Thank you for your help! Merged.

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

Hello all!

Thank you for help! Changes were committed to the development branch.

Reviewed & tested. Was added to the new release.

@tim.plunkett or @joachim is it possible to add changes:

diff -u b/core/modules/layout_builder/src/Section.php b/core/modules/layout_builder/src/Section.php
--- b/core/modules/layout_builder/src/Section.php
+++ b/core/modules/layout_builder/src/Section.php
@@ -16,7 +16,7 @@
  * @see \Drupal\Core\Layout\LayoutDefinition
  * @see \Drupal\layout_builder\SectionComponent
  */
-class Section implements ThirdPartySettingsInterface {
+class Section implements ThirdPartySettingsInterface, \JsonSerializable {
 
   /**
    * The layout plugin ID.
@@ -441,2 +441,11 @@
 
+  /**
+   * Returns a representation of the section for use in JSON serialization.
+   *
+   * @return array
+   *   Representation of the section.
+   */
+  public function jsonSerialize() {
+    return $this->toArray();
+  }
+
 }

to the issue branch (to be able to export of sections through the jsonapi module on request like /jsonapi/page_variant/page_variant).

UPD: Added, found how to do it by myself. Sorry for bothering.

Patch for core 9.3.x (posted in #178) was updated:
Added exposing of sections on request (through jsonapi module /jsonapi/page_variant/page_variant) of page variant which was built as a "Layout Builder". See more details here: https://www.drupal.org/project/page_manager/issues/3170526 →