Reduce confusion about how up-to-date the open/clicks info is on the mailing report#36289
Closed
demeritcowboy wants to merge 1 commit into
Closed
Reduce confusion about how up-to-date the open/clicks info is on the mailing report#36289demeritcowboy wants to merge 1 commit into
demeritcowboy wants to merge 1 commit into
Conversation
|
🤖 Thank you for contributing to CiviCRM! ❤️ We will need to test and review this PR. 👷 Introduction for new contributors...
PR commands & links...
|
colemanw
reviewed
Jul 21, 2026
colemanw
reviewed
Jul 21, 2026
demeritcowboy
force-pushed
the
mailing-opens
branch
from
July 21, 2026 23:33
5a1b611 to
43e331c
Compare
colemanw
reviewed
Jul 21, 2026
| {if $report.mailing.open_tracking} | ||
| <tr><td class="label"><a href="{$report.event_totals.links.opened}&distinct=1">{ts}Unique Opens{/ts}</a></td> | ||
| <td>{$report.event_totals.opened} ({$report.event_totals.opened_rate|string_format:"%0.2f"}%)</td> | ||
| <td>{$report.event_totals.opened} ({$report.event_totals.opened_rate|string_format:"%0.2f"}%){if $report.event_totals.runQueue_date} {ts 1=$report.event_totals.runQueue_date|crmDate}(as of %1){/ts} <a class="crm-hover-button" id="refresh_opens" title="{ts}Run refresh job now{/ts}" href="#"><i class="crm-i fa-refresh"></i></a>{/if}</td> |
Member
There was a problem hiding this comment.
Suggested change
| <td>{$report.event_totals.opened} ({$report.event_totals.opened_rate|string_format:"%0.2f"}%){if $report.event_totals.runQueue_date} {ts 1=$report.event_totals.runQueue_date|crmDate}(as of %1){/ts} <a class="crm-hover-button" id="refresh_opens" title="{ts}Run refresh job now{/ts}" href="#"><i class="crm-i fa-refresh"></i></a>{/if}</td> | |
| <td>{$report.event_totals.opened} ({$report.event_totals.opened_rate|string_format:"%0.2f"}%){if $report.event_totals.runQueue_date} {ts escape='html' 1=$report.event_totals.runQueue_date|crmDate}(as of %1){/ts} <a class="crm-hover-button" id="refresh_opens" title="{ts escape='html'}Run refresh job now{/ts}" href="#"><i class="crm-i fa-refresh"></i></a>{/if}</td> |
Contributor
Author
There was a problem hiding this comment.
I thought about that but isn't it the default now? Or is that still pending?
Member
demeritcowboy
force-pushed
the
mailing-opens
branch
from
July 21, 2026 23:40
43e331c to
202f149
Compare
Contributor
Author
|
I need to rethink this a little:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Since the scheduled job was introduced, it's now always out of date.
Before
About once a month I get a support request that "mailings aren't working" since the number of opens is 0, or "too low". Since I keep forgetting that it's updated by a scheduled job now, I always waste time looking into whether mails are actually going, and then eventually hit on the reason.
After
Gives the date of the last Mailing.runQueue job run. Clicking the icon runs the Mailing.runQueue job and reloads the page.
Technical Details
Comments