Marco Castelluccio

We write the articles in wordpress directly, so that they are first saved some times an then published! Maybe that is the problem, but i have tested this and it seems not!

Yes, the plugin only sends the notification when a post goes into the ‘published’ state. I wonder if one of the plugins is making the post go into the published state multiple times.

I’ve noticed a problem, I don’t know if it is related to yours, the option to not send notifications on updates is not honored when you apply a quick edit.
I will fix this problem in the next release. Could this be the cause of your issue?

Most times it is when i start the computer at the morning…then there are much doubled messages. The day on it is not often!

So you see doubled messages both when you start the computer and when you’re using it?
Are the doubled messages that you see when you start the computer new, or do you see a message that was already sent the day before?

Thank you for helping me fixing this issue!

I still don’t understand why you would want to publish a plugin that won’t work for 3/4’ths of the userbase.

Samuel, often a plugin might include optional code that only works with PHP 5.5+.
The plugin would still work with older versions of PHP, but would offer the optional functionality to users with PHP 5.5+.

An example is https://www.ads-software.com/support/topic/svn-commit-fails-because-of-yield-keyword.

Thank you, Thomas.

I’ll look into it more.

It’s weird that multiple notifications are sent, but it’s even stranger that they aren’t collapsed (since I’m now using a ‘tag’ parameter that should make new notifications replace old ones, which is the workaround I was mentioning).

Can I ask you how are you publishing the posts? Is there any chance there are multiple transitions of the post to the ‘published’ state?

Could you tell me which other plugins you’re using? Maybe there’s a conflict.

I have released a new version that contains the workaround for the multiple notifications problem and supports sending notifications for scheduled posts.

Let me know if it works for you!

Interesting, this is a really hard to diagnose problem.

I have a workaround though, which will be in the next version of the plugin (I think I’m going to release it today or tomorrow).

Could you check if there are multiple rows with the same “endpoint” in the wp_webpush_subscription table?

I was reading the VIP WordPress.com documentation, looks like plugins aren’t allowed to create custom tables (‘The plugin should use the existing database tables and structure (no alterations). Custom post types, custom taxonomies, post meta, etc. are incredibly flexible.’).

Unfortunately the Web Push plugin requires a table to store information about subscribers.

Which database are you using? And which version?

Are you able to run SQL queries against your database? To debug the issue, I would need some information.

I’ve created an issue on my GitHub repo to support planned posts: https://github.com/mozilla/wp-web-push/issues/275.

About the other issue, could you describe how you installed the plugin? I want to reproduce exactly the same conditions on my local machine.

It’s weird that sometimes it works and sometimes it doesn’t.

I’ve registered to notifications on your website, I’ll see if I can reproduce the error.

I haven’t looked into planned posts yet, I’ll try to implement support for it in the future.

Do you mean a post is sent multiple times to the same user?

The plugin by default sends a new push message when there’s an update to the post, you could change this option in the settings page.

I will update the plugin shortly with a fix for the arrow function usage (it was in a library that the plugin is using).

I’ve just released version 1.1.6, which should fix the Safari issue (note that Safari doesn’t support Web Push, so the plugin won’t do anything in Safari).

Could you test again?

Is the stage server public? I’d like to debug the issue, it would be easier if I could see your website.