🇵🇹Portugal @saidatom

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

Current behavior:
With the settings shown in the attached image, users are currently receiving notifications 7 days before any of the configured rules expire.

Expected behavior:
Logically, notifications should be sent 7 days before the specific rule configured for each case.

Example:

• User A: Has not logged in for 8 months
• User B: Has not logged in for 2 years

Currently, both users receive a notification about account cancellation. However, based on the rule that specifies "1 year of inactivity," only User B should receive the notification (since 8 months is not enough to trigger it).

What I'm correcting:
I’m updating the logic so that the system sends notifications only to users who match a specific rule's condition — and only 7 days before that rule’s threshold is met.

saidatom → created an issue.

saidatom → created an issue. See original summary → .

Great! Looks good.

Great! Looks good, moving to RTBC.

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

Great! Looks good, moving to RTBC.

Looks good, thanks

Looks good, thanks

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

saidatom → created an issue.

Great! Looks good, moving to RTBC.

Great! It looks good, moving to RTBC.

saidatom → created an issue.

saidatom → changed the visibility of the branch 3347280-translated-entity-doesnt to active.

saidatom → changed the visibility of the branch 3347280-translated-entity-doesnt to hidden.

Great! Looks good, moving to RTBC.

saidatom → created an issue.

saidatom → created an issue.

saidatom → created an issue.

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

Thanks @Grimreaper

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

saidatom → created an issue.

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

saidatom → created an issue.

saidatom → created an issue.

@c_archer can you share the exact steps and modules used?

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

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

RTBC #24 - https://www.drupal.org/files/issues/2024-03-29/stage_file_proxy-3402972-... → works fine

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

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

"fileeye/pel": {
      "Unknown format: 0x0. @see https://github.com/FileEye/pel/issues/23": "https://patch-diff.githubusercontent.com/raw/FileEye/pel/pull/24.patch"
    }

Great! Looks good, moving to RTBC.

Return type of Drupal\cached_computed_field\ExpiredItemCollection::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

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

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

saidatom → created an issue.

Reroll #30

saidatom → created an issue.

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

saidatom → created an issue.

Twig Coding Standard (twig-cs-fixer) found 120 errors, check attachment.

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

Great! Looks good, moving to RTBC.

@catch yes, you are right i have facets enabled and that causes the issue without console or php errors.

For me its RTBC.