#5030 closed defect (bug) (fixed)
WordCamp activity in Profiles shouldn't say "coming up on [date]" for past dates
Reported by: | valentinbora | Owned by: | dd32 |
---|---|---|---|
Milestone: | Priority: | low | |
Component: | Profiles | Keywords: | has-patch |
Cc: |
Description
Example:
- Joined the organizing team for WordCamp Jackson, Michigan 2019 coming up on October 4th
- Confirmed as a speaker for WordCamp Dayton, OH, USA 2019 coming up on March 1st
These are for last year's WordCamps but the activity says "coming up on [date]", and it doesn't include a year. This can be potentially misleading.
Attachments (1)
Change History (14)
#3
follow-up:
↓ 4
@
5 years ago
@dd32 could we instead change sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-participation-notifier/wordcamp-participation-notifier.php#L360 to provide the full year and maybe even pass along another parameter with the actual timestamp?
#4
in reply to:
↑ 3
@
5 years ago
Replying to valentinbora:
@dd32 could we instead change sites/trunk/wordcamp.org/public_html/wp-content/plugins/wordcamp-participation-notifier/wordcamp-participation-notifier.php#L360 to provide the full year and maybe even pass along another parameter with the actual timestamp?
Oh good the WordCamp side of that is open source :)
Yes, we could pass the full date through, but I was questioning whether including the year/date of the event is remotely useful there, especially with the present/past/future tense issues.
I don't think the date of the event is the important information here, rather it's the action & Event name/link.
#5
follow-up:
↓ 7
@
5 years ago
- Keywords has-patch added; needs-patch removed
@dd32 apparently not all of it is open source, so I'd love to fix history on the fly through an adaptation of the following:
add_filter( 'bp_activity_get', function( $payload ) {
if ( !empty($payload['activities'] ) && is_array( $payload['activities'] ) ) {
foreach ( $payload['activities'] as &$activity ) {
if ( 'wordcamp' === $activity->component ) {
$activity->action = substr( $activity->action, 0, strpos( $activity->action, 'coming up on' ) );
}
}
}
return $payload;
});
This ticket was mentioned in Slack in #meta by valentinbora. View the logs.
5 years ago
#7
in reply to:
↑ 5
@
5 years ago
Replying to valentinbora:
@dd32 apparently not all of it is open source, so I'd love to fix history on the fly through an adaptation of the following:
Not all of profiles.w.org is open-source, Only the activity handler I think.
Rather than using a display filter, I think I'd probably alter the existing DB records directly to remove the unnecessary text.
I'm happy to make this change if we can get some buy-in from a community team member (Just to verify they don't feel that it's an important detail to keep displayed)
edit: Followed up with #community-team on Slack
This ticket was mentioned in Slack in #community-team by dd32. View the logs.
5 years ago
#9
@
5 years ago
From my side I would say: remove that last part. As there is the link to the WordCamp site, there is no need for the date (what if it suddenly changes or gets canceled?)
#10
@
5 years ago
@casiepa, @sippis thanks for chiming in.
@dd32 looks like we have two buy-in confirmations, good enough to proceed?
The way BuddyPress Activity feeds works is that these are static strings stored in the database, they're not dynamic (although could probably be filtered at display)
Perhaps we should change the strings to just