Hey Alex,
Thanks for checking out Super Progressive Web Apps! Thanks for the kind words, “sexy” that is new 😉
This is quite strange. Can you give me the link to your PWA website? I will add it on my phone and wait for an update on the site. Would love to see what is happening and why this is happening.
Looking forward to it.
Hi Arun,
Thanks for that. The site is eboek.info, but if you install it, you will see the updated posts because you didn’t cache the old versions?
Is it normal that if you click a cached post, you will see it immediately (so the plugin doesn’t check for a new version on the net)? Before I used Mozilla’s plugin, and that one downloaded everything except when there was a weak connection – then it showed the cached version.
Alex
Hey Alex,
Thanks for the website. Even though Lighthouse shows a 100 score for PWA, neither I nor Jose got an “Add To Home Screen” notice.
Please try these:
– Disable Cloudflare rocket loader.
– Exclude SuperPWA service worker from Autoptimize, your sw is at – https://www.eboek.info/superpwa-sw.js
As of now it isn’t behaving as a PWA, at least not the ones we have seen so far.
Please let me know how it goes.
That’s weird, I tried it without too many problems on a couple of phones.
Anyway, I followed your suggestions, so let’s see what it gives.
Best regards,
Any update about this? Tried a couple of things but nope, I still see no updates.
One of the things I tried was letting Cloudflare respect the existing headers as according to this article it might be a problem with max-age headers. Didn’t work…
Looks like I found the problem, had to create a page rule in CF to avoid that superpwa-sw.js will be cached by the browser.
Thanks
Alex
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Sigh. Now I need to review and redact all of the author’s replies…
@arunbasillal I’ve deleted your offer to login to your user’s site. I’m am 100% sure you mean well but please never ask for credentials on these forums.
https://wordpress.org/support/guidelines/#the-bad-stuff
Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER.
If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty.
Please be aware that repeatedly asking for credentials will result in us asking you to repeatedly stop before escalating up to the plugins team.
Hello Jan,
Thanks for taking time time to review and share your feedback.
Even though I had read the guidelines a few times over the years, I had forgotten about that. Thanks again for the reminder.
In fact, from your review for Jose yesterday, I had come to know about this. The point about legal implications is very valid and you never know when something might fire back. We had never thought about it until now and we will be considering this moving forward (even when users contact us directly).
When something goes wrong, not all users might care about intentions or that we were trying to help them for free. So you are right. (Not a generalization of course, but it only takes one bad apple to ruin the batch.)
Wish I could have amended my posts myself, but since I have no way to edit my older posts, the best I can do is to not do this in the future.
Both Jose and I, take the guidelines seriously. So if you (or other mods) notice something, please do not hesitate to let us know.
Thanks again so much. Best regards.
