Conversation
…e if we can't use it
|
Looks like it's working. I'm using default values for the audience (origin of the WordPress site), subject (email address of the administrator), private key (generated when installing the plugin), so VAPID will be enabled by default. I'd like some help with the wording (names and description of the fields): @digitarald @groovecoder @jrconlin can you help? |
|
Wow, that's great to see! Here's the text blurbs I'm using to describe VAPID to dev dashboard users:
On this push app side of the experience (i.e., generating the VAPID public key), I've added this copy to the WebPushDataTestPage:
This last bit can/should probably be a step-by-step instruction list? I.e. ... To monitor your push messages to Firefox
|
|
An amazing experience would be a simple button: "Click here to register this push application with the Mozilla Push Dashboard" |
| <table class="form-table"> | ||
| <h2 class="title"><?php _e('Voluntary Application Server Identification (VAPID)', 'web-push'); ?></h2> | ||
| <p><?php _e('VAPID is useful to monitor your push messages. It allows your server to submit information about itself to the push service, which improves application stability, exception handling, and security.', 'web-push'); ?></p> | ||
|
|
There was a problem hiding this comment.
Could we always show this top of the VAPID table, regardless of whether or not it's supported by the PHP platform? I.e., include just the description and link to VAPID docs with a message like "VAPID requires PHP 5.5+, mcrypt, gmp, and openssl extensions."
There was a problem hiding this comment.
There's a list now, satisfied prerequisites are green, unsatisfied red.
|
I'll take care of the integration with a dashboard in a follow-up. |

Fixes #120.