I have VBO exporting recurring calendar dates as ical. The calculateEntityBulkFormKey function had the same id generated for the recurring events.

    $key_parts = [
      $base_field_value,
      $entity->language()->getId(),
      $entity->getEntityTypeId(),
      $entity->id(),
      uniqid(),
    ];

This was the change i added to calculateEntityBulkFormKey, patch is following.

CommentFileSizeAuthor
#8 vbo_unique_id-3131303-08.patch2.01 KBrahulkhandelwal1990
#2 vbo_unique_id-3131303.patch482 bytesrhiss

Comments

rhiss created an issue. See original summary.

rhiss’s picture

rhiss commented
StatusFileSize
new vbo_unique_id-3131303.patch482 bytes
ey’s picture

ey commented
Status: Active » Needs review
graber’s picture

graber commented

You have a view that displays same entities multiple times, just with different field values?

rhiss’s picture

rhiss commented

Usecase was for Recurring dates using "RRULE" for repeating occurrences. One event node where the content ist stored.

graber’s picture

graber commented
Status: Needs review » Needs work

Review: uniqid doesn't guarantee uniqueness of return value, it'd be better to pass the view result index to the generating method.

styrbaek’s picture

styrbaek
Primary language Danish
commented

I have the same issue.
One View with the same entity-a multiple times grouped by entity-b that reference them.

When I select a entity for VBO it process the wrong entity-b.

I need to pass both the entity-a and entity-b on the same row.
Is that possible without hacking the VBO module?

rahulkhandelwal1990’s picture

rahulkhandelwal1990 commented
Status: Needs work » Needs review
StatusFileSize
new vbo_unique_id-3131303-08.patch2.01 KB
graber’s picture

graber commented
Version: 8.x-3.x-dev » 4.1.x-dev

graber’s picture

graber commented
Status: Needs review » Fixed

Pushed to latest dev. Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

graber’s picture

graber commented
Status: Closed (fixed) » Active

We have a regression: persistent selection breaks when we change sorting options.

When a user selects some view results and changes sorting of the view, row indexes change and the selection info no longer applies to the current results. We have to find a different solution unfortunately. Will revert this.

  • Graber committed ccb18215 on 4.2.x 
    Reverted previous solution of Issue #3131303.
graber’s picture

graber commented

The only thing that currently comes to my mind is to dispatch an event where those bulk key parts could be altered..