PWA Cache rules affecting Homepage

  • Resolved Anonymous User 13308688

    (@anonymized-13308688)


    6 years, 9 months ago

    A important problem appears, like in other PWA Apps.

    The Service-Worker files creates some caching rules that overwrites the regular caching plugin of wordpress and affecting this instantly, also if i set ‘no caching for admin users’. We using wp-rocket and once the pwa plugin is active, the regular homepage will not updating anymore, until you delete the browser cache. This is not ideal and i think it has something to do with the service-worker, because this is located in the root directory, while wordpress caching plugins are located below this.

    I talked to the wp-rocket developers about this and they would look deeper into this.

    This is what they wrote:

    https://www.ads-software.com/support/topic/cache-on-pwa-start/#post-9930398

    maybe you will finding a solution together.

    regards

    • This topic was modified 6 years, 9 months ago by Anonymous User 13308688.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)

  • Hey @trooper_d5x

    Thanks for sharing the feedback. Once the service worker is installed as of now, pages are served first from the cache.

    This is not ideal as you said and I am working on adding cache busting features so that browser cache is cleared when new content is added. This will be out with version 1.3 of SuperPWA (eta this week).

    Hey @trooper_d5x

    I have addressed this in the latest release, version 1.3. Please upgrade and see how that goes.

    Here is the changelog:

    = 1.3 =
    * Date: 10. February.2018
    * New Feature: Added support for high-quality splash screen. You can now set the 512×512 icon for the splash screen of your Progressive Web App.
    * Enhancement: Super Progressive Web Apps now accounts for content updates and will update the cache as you update the website.
    * Enhancement: Improved in-browser service worker update handling.
    * Enhancement: Added automatic upgrade of manifest and service worker on plugin upgrade.
    * Bug fix: Only GET requests are served from the cache now.

    Best regards.

    Thread Starter Anonymous User 13308688

    (@anonymized-13308688)

    Hi there,

    it seems to be working now .. thx.

    But some last things and ideas:

    Important: If i start the PWA App they load the right landing page, but if i clicked on post, they open this in the normal browser view, including Adress Bar and Navigation on the bottom. I think that′s not correct and i have also seen with other pwa apps that they hide this both.

    Some ideas for the future:

    the manifest offers more option that could also available in admin menu, like Theme Color, Display etc.

    Hey @trooper_d5x

    If i start the PWA App they load the right landing page, but if i clicked on post, they open this in the normal browser view, including Adress Bar and Navigation on the bottom. I think that′s not correct and i have also seen with other pwa apps that they hide this both.

    So are you saying that the links open in a new browser window instead of the staying in the PWA itself? This is not what I see in our tests on other websites. I noticed that SuperPWA is not active anymore, can you please activate it so that I can check it out?

    the manifest offers more option that could also available in admin menu, like Theme Color, Display etc.

    Yes, we are looking forward to adding these. Sticking to the basics until we figure out all the other pressing issues.

    Thanks for your feedback. Best regards.

    • This reply was modified 6 years, 9 months ago by Arun Basil Lal. Reason: corrected typos
    Thread Starter Anonymous User 13308688

    (@anonymized-13308688)

    It is now active …

    and yes, it shows the normal browser if i click on a post (deep) link. See here or live

    https://www.flickr.com/gp/74713339@N03/17wyK2

    best regards

    Thanks for activating SuperPWA again and for the screenshot.

    Can you remove /amp/ from the start_url settings? We are wondering if this is an AMP related issue.

    Thread Starter Anonymous User 13308688

    (@anonymized-13308688)

    Yes, without AMP Landing Page it works fine.

    Just to give you an update, we haven’t forgotten your case. In fact, I just opened a GH issue to track this.

    https://github.com/SuperPWA/Super-Progressive-Web-Apps/issues/8

    I will update you as soon as I make progress. Jose and I are working hard at it.

    Hello @trooper_d5x

    We have done a lot of tests and we think we have figured this out.

    Can you please update to the latest release of SuperPWA and let us know your feedback in regards to compatibility with your AMP plugin?

    Here are the release notes for version 1.4:

    * New Feature: Added UI for default orientation of your PWA. Orientation can now be set as “any”, “portrait” or “landscape”.
    * New Feature: Added UI for theme_color property in manifest.
    * Enhancement: Improved compatibility with all major Accelerated Mobile Pages (AMP) plugins.
    * Enhancement: Improved handling of external resources.

    Looking forward to it.

    @trooper_d5x

    Did you get a chance to try out version 1.4? Very excited to hear your feedback.

    Thread Starter Anonymous User 13308688

    (@anonymized-13308688)

    Hi there,

    the project is currently on hold, so we waiting a while until pwa′s has a wider distribution. But good to hear you making progresses. I take a look at this on my test server.

    Thank you for the support ??

    Sounds good @trooper_d5x . If you have any feedback, do not hesitate to let us know!

    Some exciting things are about to happen soon ??

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘PWA Cache rules affecting Homepage’ is closed to new replies.