Rowinson Gallego

Thanks guys for your feedback. We haven’t started implementing this because we were collecting more information about it, but now it’s the right time. We will not collect that information by default, but will be part of the optional user information the sites could collect in the future (IP address, OS, Browser, localisation, etc). It’s up to the website to enable it and to inform the users appropriately.

This has been released on v1.1.2

For the option to hide the subscription bell on subscribed users, I’ve created a ticket: https://github.com/rwngallego/perfecty-push-wp/issues/35

I would appreciate if there will be an option to send the short url instead of full post url.

It’s not possible to use auto send with a static url, as usually when you publish a post and send a notification, it should link to the post you’ve published.

Could you please try this scenario:

– Publish the post
– You will receive a notification in your browser
– Click on the notification pop-up (it should open a web page with the post you’ve published)
– Take a screenshot of the url address and paste it here (don’t copy/paste the url because it will replace the characters)

Thank you!

It’s the Service-Worker-Loader which is loaded directly from the plugin-folder (/wp-content/plugins/perfecty-push-notifications/public/js/service-worker-loader.js.php) and I really dont know why

Oh, I see, this is only for adding the Service-Worker-Allowed: / header, which is important to register the JS Service Worker in any scope chosen by the user (This is also done by OneSignal and other Push providers), and shouldn’t represent any major security concern.

In admin part jquery would be no problem cause performance doesnt matter here. But jquery is still needed on the frontend. The script “js/perfecty-push-sdk/dist/perfecty-push-sdk.min.js” requires jquery. Could this be fixed?

Yes, we’ve noticed this is only for the public facing. Sure, we’re already addressing this in the github ticket and will be included in the next release. Thanks for reporting this!

I think the arabic issues is similar to this:

https://www.ads-software.com/support/topic/arabic-in-permanent-link/

So, as I said, when the post is published, the notification arrives and we click on it, the url is opened correctly. However, if you try to copy-paste the url that it opened, they will appear as an encoded url.

Closing this as inactive. If needed please open it again.

No sign of the notification on my phone or tablet.

Have in mind it only works on Android devices. Could you please confirm the model and the browser you used in the mobile devices? Thank you!

Hi @abdobasha2004,

Or support Arabic urls.

I’ve tried to reproduce this and it worked correctly, unless I’m missing something. I created a post called ????, then mark it to send automatic pushes and the resulted link was correct (I clicked in the notification message that arrived after publishing and it opened the correct post url in Arabic)

Other thing, Is there an option to hide the subscribtion bell, I think it will be better as an option?

Yes, sure. I think this has been mentioned by other users before, so it’s worth it but just as an option. Just to clarify, it will be hidden after the user has subscribed, otherwise it will be always visible to allow users that didn’t want to subscribe initially to later subscribe by clicking in the bell icon.

Hi @stkuhn, and thank you for your comment.

Why do you directly execute php-code from the plugin-folder

Sorry, could you please clarify this? I don’t see where we are doing these executions? Do you mean the wp-cron execution? If there’s something we are not doing it right, sure, we can fix it, specially for security concerns.

Is there a way to use Perfecty Push without jquery or do you plan a vanilla javascript solution?

Of course, we’ve done the biggest part to achieve this in our last release. There are some small scripts where we use jquery in the admin part, so for sure we will take a look at this. For the moment, I’ve created a ticket: https://github.com/rwngallego/perfecty-push-wp/issues/32

(I can see it running as scheduled), but I have not received any notifications on the three devices

Could you please confirm if the notification job got completed? I’ve received some reports of some conflicts with plugins that use an old version of the Guzzle library. Is it also possible to check the php error logs? You can check: https://askubuntu.com/questions/14763/where-are-the-apache-and-php-log-files

it doesn’t change the browser settings. Do I still get notifications or does the bell remove the user from the plugin?

No, when the user opts out, they just mark themselves as inactive in the DB. When you send a new Push Notification, they will not receive anything because they are excluded from the execution. You can see in the user list that they change from Active: Yes to Active: No.

On the other hand, the Browser permissions cannot be modified from the websites, so this is something we cannot change but the user himself.

Ok, thank you. I’ve created a ticket to address this. We probably will add a checkbox to disable the collection of the IP address: https://github.com/rwngallego/perfecty-push-wp/issues/28

Hello, maybe we could implement it, could you please let us know your use case? Is it for any regulation, any special requirement or how exactly would you like it to work? Thank you!

Hello,

We can see that it’s receiving a 403 Forbidden from Nginx when loading the Service Worker Javascript.

This is the file we try to load: https://meeplescorner.co.uk/wp-content/plugins/perfecty-push-notifications/public/js/service-worker-loader.js.php

It should have return the service worker content but it’s not. This looks like a configuration issue in Nginx. Maybe you want to check the location section:

    location ~* \.(js|css|png|jpg|jpeg|gif|ico|html)$ {
            expires max;
    }

If you want to provide us more details feel free to write to our email: [email protected]

This has been fixed in v1.1.1