Closed (fixed)
Project:
Scheduled Updates
Version:
3.0.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Apr 2016 at 02:31 UTC
Updated:
1 May 2026 at 21:05 UTC
Jump to comment: Most recent, Most recent file

Comments
Comment #2
larowlanComment #3
bkosborneI'm guessing this was probably left out from the initial implementation because it's a bit complex to retrieve the target entities. There can also be multiple entities that a scheduled update affects. So the UI for that wouldn't be great if you had any more than a couple.
But yeah, without the info of the "what" the scheduled update is affecting, this page is quite confusing.
Comment #4
realityloop commentedworks as advertised... I do wonder if this should possibly be a view though?
Comment #5
chop commentedWorks well. Using this patch in production.
Comment #6
shaktikit's working fine.
Comment #7
mhavelant commentedIt's working well, however, if you have lots of revisions then it looks pretty overwhelming and every link points to the latest revision.
Comment #8
tedbow$target_fields will be empty if
\Drupal\scheduled_updates\Plugin\UpdateRunner\IndependentUpdateRunneris the update runner.This is when
$entity->entity_idsis not empty.Basically
IndependentUpdateRunnerdoesn't rely on an entity reference field on the target entity type. It uses the entity reference field on the Scheduled Update entity to allow targeting of multiple entities with 1 update.So will cause an error in the current patch.
Comment #9
tedbowAlso we should have test for each type of update, loading the update list page and confirming the title is shown.
Comment #10
ygstnd commentedI got the error like this:
Here's a patch that works for me. It's based on the previously added one.
Comment #11
henry tran commentedI've rerolled to latest version
Comment #15
smustgrave commented