Rowinson Gallego

This has been released in the v1.1.4 version

Apart from that there’s a bug in how we install the Perfecty Push Service Worker when there are other Service Workers. I’ve created a ticket here and the fix will be included in the next release: https://github.com/rwngallego/perfecty-push-wp/issues/42

You have enabled the “Remove conflicting workers” option, but you shouldn’t because the PWA service worker from Progressive WordPress will be removed. Please deactivate that option first.

I could see that now the redirection is fixed with the changes you did and the user registration is completed, however the Service Worker registration is not properly done. I will check if I can find something interesting there, if you could enable Debugging in the public widget, that would definitively help.

Hi @stkuhn we’ve updated the PR (https://github.com/rwngallego/perfecty-push-wp/pull/40) to use a button instead of a div, if there are any additional changes please let us know ??

Hi @stkuhn that sounds very cool, thank you! In regards to the font, we will go back to the font awesome SVG icon because of the license. I’ll update the PR and probably release it soon ??

If this helps in your diagnosis, in the first call there’s no o2s-chl cookie, while in the second call, it’s there. I found the following forum thread where something similar is reported. I don’t know if it’s related to o2switch itself or a cache plugin as mentioned there, probably you need to check with your hosting provider:

https://forum.opencart.com/viewtopic.php?t=216816&start=40

Hello @julien-alibert

I’ve tried to subscribe in your website and noticed that for the registration call your website is returning a 307 redirect to 185.246.45.132:443, and thus the registration fails in the first attempt. If I reload the page, the Perfecty JS SDK attempts to register again by himself and it succeeds. Could you please check your server configuration? I wonder if you have any special configuration in your server or if you use a cache or redirection plugin.

Details of the request:

Request URL: https://www.laclefdevoute.fr/wp-json/perfecty-push/v1/public/users
Request Method: POST
Status Code: 307 
Remote Address: 185.246.45.132:443
Referrer Policy: strict-origin-when-cross-origin

Hi @stkuhn, sure!

I’ve created this ticket: https://github.com/rwngallego/perfecty-push-wp/issues/39

The Pull Request is ready with your suggested changes, for the moment I’ve based part of the CSS styles to the example you’ve provided. Are you OK if we use them partially? Also, is the SVG the same as the one from font-awesome or where did you take it? I need to mention where we got it in the license notes.

Of course, if you want to help out with the styling that would be great!

This has been released in the v1.1.3 version (option to hide the bell)

This has been released in the v1.1.3 version

Hi, we’ve tested this and it’s currently working in Mobile devices with Android too (Tested subscription on Chrome, Firefox, Brave). When you send a Push Notification we could confirm if we received it or not, but it’s difficult to coordinate when to have the device up and running, otherwise the notification could be missed.

We don’t have access to any tablet with Edge on it, so unfortunately we cannot check if it works or not in that combination, but it should.

Copy comment from Github:

@kusattapan while implementing the IP transformation from CloudFare we’ve realised that it’s not a good idea to do it in Perfecty Push itself. Apart from the many different CDNs on the market different than CloudFare that we would have to support, there’s the security aspect for each of them that makes it out of the scope of the plugin (like keeping an updated list of approved ip ranges from the different providers for example). This is not only a problem that only affects Perfecty Push, but instead it’s a better solution to do it in front of the application itself (e.g. mod_remoteip/mod_cloudflare). Furthermore, how are you doing it for the other parts of your website where the IP is being logged/monitored (like Apache access logs/WAF/Load Balancer)?

That being said, we’re sorry but we will need to close this. As mentioned above, in case there’s any need to do any IP transformation, it will need to happen before our plugin.

Hi @stkuhn, thanks for your message.

Inactive: User has un-checked the “I want to receive notifications” option in the Bell.
Active: User who has recently subscribed or that decided to opt-in after opting-out.

an option to automatically delete unsubscribed users (not active) from the database?

This is clear and I’ve created a ticket here: https://github.com/rwngallego/perfecty-push-wp/issues/37

Basically we will remove users that have opted-out. (Users who initially allowed notifications in the browser, but then they un-checked the “I want to receive notifications” option in the Bell).

There’s no gain in having them in the DB, as usually they will not receive any push messages, and the subscription could expire in between opting out/in again.

Manual deletion of users in backend should only be an option for users, that did not unsubscribe but are not active any longer

Could you please clarify? Currently, if a user is still subscribed (opt-in) but if for any reason the endpoint has expired, they are deleted automatically so that next time the SDK will renew the subscription when the user visits the website.

Could you also implement an option to automatically delete unsubscribed users (not active) from the database?

That’s something different to what we’re discussing here, and I would like to understand it better, could you please create a new thread? Thank you!