blogtutor
commented
3 months ago Just FYI, here are the other messages we're returning. They will use the setting that was returned in the most recent snapshot -- so if you change a setting it won't "take effect" until you send a snapshot back to relay. (But the Onboarding tag will override the Firewall setting.)
If set to Sucuri:
If set to Other/None:
If the Site has a Site Tag of Onboarding in the relay (we need to start setting this for onboarding it, and then removing the tag when no longer onboarding):
(I think we started building this without having an Issue in this repo, so I'm starting one now as I think we'll be having more ongoing discussion as this expands. I don't know how to deal with a single issue across repos, so I'm starting this thread for things that need to be handled on the Client Plugin side of things. Here's the issue on the Relay side.)
So far, Brian's created a couple of PR's in the Relay to handle catching and returning client stats to a widget on the client's /wp-admin/ dashboard. History (partial, I think):
https://github.com/blogtutor/np-dashboard/pull/483 https://github.com/blogtutor/np-dashboard/issues/507
And in the client plugin: https://github.com/blogtutor/blog-tutor-support/pull/337
At the moment it looks like this:
(If the site is set to Sucuri or Other/None, it will return a relevant message to let the client know we don't have the stats and to contact us if they want them.)
The widget header is controlled by the Client plugin, and everything inside the box is served by the relay. So any changes to the content can be modified at the relay without releasing a new version of the NerdPress Support plugin.
The plan is to use the widget as a highlight/preview, which will then link to a larger stats page inside their dashboard, which will be something like (TBD)
https://www.domain.com/wp-admin/admin.php?page=nerdpress_stats. The client report email will also link to this larger stats page.