Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Admin Page: Monitor data requires the user to be linked with WordPress.com #5208

Closed
jeherve opened this issue Sep 27, 2016 · 0 comments · Fixed by #5366
Closed

Admin Page: Monitor data requires the user to be linked with WordPress.com #5208

jeherve opened this issue Sep 27, 2016 · 0 comments · Fixed by #5366
Labels
Admin Page React-powered dashboard under the Jetpack menu [Feature] Monitor [Type] Bug When a feature is broken and / or not performing as intended
Milestone

Comments

@jeherve
Copy link
Member

jeherve commented Sep 27, 2016

Steps to reproduce the issue

  1. Activate Jetpack, connect it to WordPress.com.
  2. Activate Monitor.
  3. Go to Jetpack > Dashboard: the Monitor card is displayed properly:

screen shot 2016-09-27 at 11 42 30

  1. Go to Users > Add New, and create a new admin.
  2. Log out.
  3. Log back in with the new admin.
  4. Go to Jetpack > Dashboard.
  5. The Monitor card won't load:

screen shot 2016-09-27 at 11 43 07

The wp-json/jetpack/v4/module/monitor/data call returns a 500 error:

screen shot 2016-09-27 at 11 43 59

The response is Jetpack: [missing_token]

@jeherve jeherve added [Type] Bug When a feature is broken and / or not performing as intended [Feature] Monitor Admin Page React-powered dashboard under the Jetpack menu labels Sep 27, 2016
@jeherve jeherve added this to the 4.3.2 milestone Sep 27, 2016
@jeherve jeherve modified the milestones: 4.3.4, 4.3.2 Oct 12, 2016
@jeherve jeherve modified the milestones: 4.3.3, 4.4 Nov 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Admin Page React-powered dashboard under the Jetpack menu [Feature] Monitor [Type] Bug When a feature is broken and / or not performing as intended
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant