Suggestion – feature request – issue

Hi,

Thanks a lot for your suggestions and we will have them into account because as you pointed out the cost is big.

1. Can you please remove feature where users are deleted from database, because VAPID key is wrong? This is one-(bad)-step suicide.

This is a bit tricky because the error is returned by the Push Services and the API response might not be the same for the different browsers. However we will investigate it: https://github.com/perfectyorg/perfecty-push-wp/issues/162

2. Plus if you could add checkbox to protect VAPID fields, so people can be protected from accidentally adding random keystroke in that garbled mess, because there’s no way to know if you pressed a key or not, unless you seriously pay attention at that, or when you figure your userbase is empty.

Absolutely! https://github.com/perfectyorg/perfecty-push-wp/issues/163

3. Also some error message ‘YOUR VAPID KEY IS INVALID, WOULD YOU LIKE TO CONTINUE’?
Or any similar protection step?

Good idea: https://github.com/perfectyorg/perfecty-push-wp/issues/164

4. Adding userbase backup? Auto-exporting in CSV, and one-click import? Only option to add users to that CSV, not being able to delete them for any reason? Easy userbase restore? Something along those lines?

Well, database backups should not be handled by the plugin directly but rather by the user through a different plugin/mechanism specialised on doing that.

About 4th point.

What I had in mind is not a regular MySQL backup button, or something like that.
It’s more of a parallel list of user details written in a file that’s more similar to a log file, than database, but also compatible with PHPMyAdmin import. So, whenever someone is subscribed, plugin adds his details to that log file. Doesn’t delete anyone, ever.

Kind of like extra layer of ‘I got your back’. So in case of any unpredicted failures, or whatever can possibly happen, log can be imported through PHPMyAdmin.
This way, when first notifications is sent, all users that are not subscribed, will be filtered out, and we’ll get clear database of users to work with.

And here’s the reason why:

I could have setup daily backups, which is good setup, I hope you agree.
This backup is taken at 3AM, when I have least amount of visitors, so least stress on the server. But, I can have 300, or 5000 daily subscribers, and between two backups in case of failure, I could lose them, by restoring a backup old 20h for ex., and I can’t take backups more often. But I would have a log file, that I can import, which contains all users ever, and I wouldn’t lose anyone.

This addon would contain two main parts:
one is one-time export of users from DB to log file,
second one is add users to log file, whenever someone is written to a database, at the same time.

Thank you.

The only way in which you could “lose” your users is the scenario you reported here and the appropriate solution corresponds to the points 1, 2 and/or 3.

What you want to do is already covered by the DB replication feature available in almost any modern DB Engine, including MySQL. In this case, you setup a DB replica where you have a master/slave DB that are in sync almost instantly. You might want to define specific points of backup, but considering that the plugin will not remove the users instantly once points 1, 2 and 3 are addressed, then it should be sufficient. Have in mind that even if apparently you “lose” some users, it’s not likely the case. When they approved to receive Notification, and whenever they visit your website, our JS SDK will automatically check their user subscription and re-subscribe in case it’s not found, so those users will be populated automatically in the DB.

• This reply was modified 2 years, 7 months ago by Perfecty.