robwent

@mattthomas-photography Sorry, I was just trying to add a temporary solution for anyone else finding the thread as I saw 4 recently opened threads about the same problem.

Download the last version until the issue is fixed: https://www.ads-software.com/plugins/instagram-feed/advanced/

• This reply was modified 3 years, 12 months ago by robwent.

Download the previous version from here until it’s fixed: https://www.ads-software.com/plugins/instagram-feed/advanced/

Download the previous version from this page until they fix it: https://www.ads-software.com/plugins/instagram-feed/advanced/

The update fixes it for me.

Unfortunately, once you manually trigger the cron, it then seems to run as normal again.

So when I checked just now, this install now seems to be running as normal again.

Hi,

Just opening this again as I noticed the same thing happening on another install.

This time nothing was changed, just mainwp updated.

It was running version 4.0.1 and all crons seem to be fine other than the one that checks for available updates.

Like the other install, this one also has wp cron disabled and runs a server cron.

Image of cron status

I needed to get this going so installed crontrol again and ran all the jobs manually.
I also updated to the latest version at the same time, so it’s possible that this is something that was fixed after 4.0.1.

Hi,

Thanks for the reply.

I’m not exactly sure what I did the other day, but it now looks like the cron last run times are correct.

I’ll mark this as resolved. I think it must have been some issue on my end.

Sorry to waste your time!.

I had it installed on a site using Newspaper 8 and it worked without any problems.

Might be an issue with another plugin?

It adds a popup on supported devices which allows users to add a shortcut to your site on the home screen of their phone.

It’s a shortcut to going to a web browser and typing in the address.

You don’t need to do anything with the play or ios store.

This is how progressive web apps work. There is no ‘native app’ as it is a web page that gets opened in a browser.

What pwa features do you want to use?

Click on the link to view the manifest file in the plugin settings.

It should say : “display”:”standalone”

If that’s the case then it might be a caching issue.

Try removing the app and then add it again with a different browser (I think brosers cache manifest files for a long time. At least that’s my experience with chrome not picking up changes with app icons).

It also looks like the manifest file does not use versioning, so if you have anything like cloudflare or a cdn in use then you may need to purge the cache for that file for any changes to show.

The add to home screen prompt comes from the browser, not the website.
So I don’t think any of this is possible.

You could link to a page explaining how the user can install to home screen through the browser settings if they have dismissed the previous prompts?

Try testing on another phone or in another browser.

Whilst testing, I just found that chrome stops showing the popup after you ignore it for a while.
I would guess that they do that to stop annoying the user.
When I check in the browser options there is still a link to add to the home screen.

I think in this case ‘dynamic’ just means that it’s not an actual file and requests to the manifest url serve content that is generated dynamically.
Anything asking for the file would have no idea if it is a static file or generated dynamically or not (Without caching a dynamic one may be slower to access).

I’m new to this plugin, but in the changelog, they added a setting as to how the app should be opened.

Maybe the previous option is no longer the default and you are now seeing the default behaviour.

You can set it to open like an app, in a browser or in a browser with minimal controls.

I’m seeing that phones heavily cache the app though, so changing things like icons doesn’t show unless you clear the application cache in chrome.
Unfortunately, I find that that deletes all of my history rather than just for that website.

But… check the settings of the plugin and wait.