WordPress Events in the Dashboard

Since WordPress 4.8, there has been Dashboard widget showing upcoming local events. The widget shows upcoming WordCamps and meetup events inside wp-admin, making it easier for people to find out what’s happening in their local communities.

If a site has multiple users, each one will be shown the events that are close to their individual location. The dashboard widget will try to automatically detect their location, but they’ll also be able to enter any city they like. Users can click on a pencil icon and type in the location of their choice. Automatic location detection and the event data for the plugin is provided by an api.wordpress.org endpoint.

The radius for pulling events from users location is 100 kilometers for meetups and 350 kilometers for WordCamps. Events for each location are cached for 12 hours.

How can I attend an event that I see in the WordPress Events and News widget? How can I attend an event that I see in the WordPress Events and News widget?

If you see an event on the Events and News widget that you would like to attend, just click on the event name to be taken to a page with more information. You’ll be able to RSVP for the meetup event via meetup.com, or buy a ticket for a WordCamp on the local WordCamp website. If you have any trouble, you can email support@wordcamp.org for more information. And welcome to the WordPress community!

Top ↑

I belong to a WordPress meetup group, and our events don’t show up on the widget! Is it broken? I belong to a WordPress meetup group, and our events don’t show up on the widget! Is it broken?

Only groups that are part of the WordPress meetup chapter program are listed on the widget. If your local group’s events aren’t showing up, it’s possible that it just hasn’t joined the chapter program yet! Joining is free, and requires following a few good-faith rules that were created by a group of volunteer meetup organizers. Information on joining the WordPress meetup program can be found here.

Top ↑

What information is collected, and what is it used for? What information is collected, and what is it used for?

The plugin sends each user’s timezone, locale, and partially anonymized IP address to api.wordpress.org, in order to determine their location, so that they can be shown events that are close to that location. If the user requests events near a specific city, then that is also sent. The data is not stored permanently, not used for any other purpose, and not shared with anyone outside of WordPress.org, with the exception of any conditions covered in the WordPress.org privacy policy.

Top ↑

How to debug functionality and report a bug? How to debug functionality and report a bug?

Following instructions and details are bit developer orientated. If you don’t feel comfortable with code and technical terms, the #community-events Slack channel is the place to get help and report problems with WordPress Events functionality.

Before submitting a bug report, please check that you are not in a local development environment and expecting Events API to detect your location. That will not work, since location detection can’t be done with IP address of local environment. Currently, the ip2location database is used as the source for detection and the data is updated oncea month.

On the Dashboard side, the Events widget saves a few database records to store necessary data. One is `community-events-location` inside `wp_usermeta`, which stores either the location detected or the location manually set by each user. The other record is a transient to store the cached event data. That transient is shared across users, so if you have 500 users, but they’re all in Seattle, then there will only be 1 transient to cache the events for all of them.

If you are availabe to add plugins and read error logs, add this plugin to your `mu-plugins` https://core.trac.wordpress.org/raw-attachment/ticket/41217/log-community-events-requests.php. It will give you the exact api.wordpress.org/events URL that is being queried, making it easier to troubleshoot parameters.

Possible bugs can be discussed in #meta-wordcamp on Slack and reported in Meta Track ticket if the bug seems to be in the Events API. Bugs in Dashboard widget can be reported in Core Track.