Not works for my site

Hello @locky089

Thanks for using SuperPWA.

While I am not familiar with bedrock, it sounds like WordPress URL and site URL in General settings is different.

Can you please do a couple of edits to verify this for me and I will add the fix in the next release:

– Change network_home_url to network site url in https://github.com/SuperPWA/Super-Progressive-Web-Apps/blob/master/public/manifest.php#L51
– Same change here: https://github.com/SuperPWA/Super-Progressive-Web-Apps/blob/master/public/sw.php#L48

Looking forward to your feedback.

@arunbasillal, thanks for your help! I did this changes and Manifest link works fine on the settings page. But add to home screen notice don’t show up.

Glad to see progress. Jose pointed out a valid issue. The scope in the manifest needs to be ./ or simply / but its picked up as /wp/ since that’s the location of the file.

I am not familiar with the bedrock (roots.io) folder structure, but it seems like we will have to do some custom compatibility for this.

Can you edit the manifest manually and change the scope to a / like this: https://superpwa.com/superpwa-manifest.json and let me know if that takes care of it?

Sorry for the multiple edits, but your feedback will help us improve the plugin for everyone else as well.

Looking forward to your feedback.

The latest version, 1.7 that was just release fixes the original issue of the wrong manifest url.

I will wait for your feedback on the scope. I also need to find a way to understand the bedrock folder structure in depth.

I fixed manifest scope. But, it didn’t help.

The organization of Bedrock is similar to putting WordPress in its own subdirectory but with some improvements, including renaming wp-content/ to app/.

── web
├── app
│ ├── mu-plugins
│ ├── plugins
│ ├── themes
│ └── uploads
├── wp-config.php
├── index.php
└── wp
────└── composer.json
────└── superpwa-manifest.json
────└── wp-blog-header.php
────└── wp-cron.php
────└── wp-login.php
────└── wp-trackback.php
────└── index.php
────└── superpwa-sw.js
────└── wp-comments-post.php
────└── wp-includes
────└── wp-mail.php
────└── xmlrpc.php
────└── license.txt
────└── wp-activate.php
────└── wp-config-sample.php
────└── wp-links-opml.php
────└── wp-settings.php
────└── readme.html
────└── wp-admin
────└── wp-content
────└── wp-signup.php

I am not a developer but i am glad if i can to help you.

• This reply was modified 6 years, 10 months ago by locky089.
• This reply was modified 6 years, 10 months ago by locky089.
• This reply was modified 6 years, 10 months ago by locky089.
• This reply was modified 6 years, 10 months ago by locky089.
• This reply was modified 6 years, 10 months ago by locky089.

About bedrock folder structure: https://roots.io/bedrock/docs/folder-structure/

Thanks for the feedback @locky089

The folder structure above creates a problem for the scope of the service worker. A service worker can handle only the folder its in and its sub-folders. (There is a workaround, but SuperPWA doesn’t do it yet)

So if the service worker is in the /wp/ folder, it cannot only handle requests from example.com/wp/ and example.com/wp/files etc.

Something I notice is that https://grischun.ru/wp/superpwa-sw.js returns a 404 while it seems like SuperPWA is indeed installed and active. Any idea why?