Making WordPress.org

Opened 5 years ago

Closed 4 years ago

#4636 closed enhancement (reported-upstream)

Remove global sponsor details from flagship event sites

Reported by: hlashbrooke's profile hlashbrooke Owned by:
Milestone: Priority: normal
Component: WordCamp Site & Plugins Keywords: needs-patch
Cc:

Description

Currently, all WordCamp sites explicitly thank all of the global sponsors on the ticket page after purchase, as well as in the footer of all ticket purchase emails.

According to [our global sponsorship program](https://make.wordpress.org/community/2019-wordpress-global-community-sponsorship-program/), however, the global sponsorship funds do not apply to flagship events, but the thank you text is displayed for them too.

We should remove the global sponsor text from events that don't make use of global sponsor funds - currently, that includes WordCamp Europe, US and Asia and they all have their "Multi-Event Sponsor Region" setting set to "Excluded". It should be relatively straightforward to choose not to show the global sponsor thanks based on that field.

I don't currently have a local dev environment setup, but it looks like we should be able to do that in the camptix-tweaks.php file here: https://meta.trac.wordpress.org/browser/sites/trunk/wordcamp.org/public_html/wp-content/mu-plugins/camptix-tweaks/camptix-tweaks.php#L907

I think this should do the trick:

if( 436028 == $region_id ) {
  break;
}

(436028 is the ID for the 'Excluded' region).

Am I perhaps underestimating the amount of work here?

This change would do a lot to remove the confusion that these messages create for attendees.

Change History (3)

This ticket was mentioned in Slack in #meta-wordcamp by hlashbrooke. View the logs.


5 years ago

This ticket was mentioned in Slack in #meta-wordcamp by coreymckrill. View the logs.


4 years ago

#3 @dd32
4 years ago

  • Resolution set to reported-upstream
  • Status changed from new to closed

This ticket has been moved to GitHub https://github.com/WordPress/wordcamp.org/issues/636

Note: See TracTickets for help on using tickets.