I am working on a site. I got this from a client to be redesigned. The old design was made by some other agency. Once I was done, and changed old DNS records to the new server and went live with the new design, everything worked OK. Except, for old users of the site.
All old users couldn't see the new design. I did everything I could to force the browser to forget cache by using HTTP Headers, .httaccess etc. Nothing worked.
I later found that the old design was built on PWA technology. Progress Web Apps which can be installed as an app on the device. And this app used something called worker cache to store static files in the Cache Storage and Application cache.
Now for some reason, old users' browsers are not willing to forget that cache at all. Looks like the browser isn't even hitting my new server / DNS settings for the new design. It just takes the content from the worker/application cache and displays the old site.
I can't ask users to clear their cookies or cache, or uninstall the app individually. How can I get rid of this cache from old users' browsers so that the new design is working on those devices too?
Any ideas?
Related
I have an app which is already published in app store, I need to send mail to users with link clicking on which it should open the app if its installed or should go to app store. I'm aware of the URL schemes and universal links and that would require modification in my app. I was wondering if there is any other way that this could be achieved where I could create a link maybe using itms-app or some other method where I don't need to make any changes in the app. Any help is appreciated
Unfortunately, not. For a phone to open your application, it needs a way to recognize your application.
URI Schemes
The URI scheme information is configured in the .plist file and is local to the application and therefore cannot be changed without an update. Although you probably don't want to use URI schemes anyways since they will present the user an error if they don't have the app instead of taking them to the app store.
Universal Links
This is the new way Apple performs deep linking and the only other way a link could open up the app. These require a locally stored entitlements file along with an .apple-app-site-association that is hosted on your own website domain and cached when the app is downloaded or updated. These also do not take users to the app store, they take users to the domain in which the AASA file is hosted.
Best Solution
Use Branch's iOS SDK to handle all of the AASA file hosting and App Store redirection. This would still require you to push out a new update, but that is the only possible way to accomplish this.
EDIT This issue seems to only affect Chrome and Safari on my Macbook Pro. I can't replicate this issue on other computers and browsers. I thought it might have been malware or virus, so I reformatted my Macbook. Didn't fix the issue All of a sudden, I am running into this issue when developing on my local server as well with MAMP. Assets are missing everywhere and some pages fail to load all together
I've noticed recently when I refresh my Vue SPA with the cache disabled, the page tends to look messed up with missing images/resources.
When I check the console, I see a lot of ERR_CONNECTION_REFUSED for resources that are definitely there. If I refresh the page, the errors go away. It tends to happen after I clear cache and load up the webpage for the first time, or if I disable cache in the developer console.
It turns out there had recently been a DDos attack against my IP address so my hosting service forced rate limit connections to my IP address. So if you ever run into the same issues, check with your hosting company first.
In other words - they got a new website and used the domain that was assigned to the old site.
When I google it or yahoo or bing it, on the three browsers on my Mac, I find the new website.
I think he's saying the old website still comes up. It's been a month. they're using I.E. not sure what version. He claims they're seeing the old site on pc's that have never before been used to view the old site, so the cache is not an issue.
I don't see how this is possible. Is this possible?
He may be having the old website's IP address cached. Ask the client to open command prompt and type ipconfig /flushdns.
I am launching a new redesigned website on windows hosting. I am wondering what is the best way to launch this new website without having any downtime on the existing one?
MY only fear is having a user go to visit a page and it's not there or the supporting files are not uploaded yet.
One of the simplest ways to handle this is to put a load balancer or proxy server in front of the application server. Then set up another application server with the new code. Once it is ready, you can change the proxy server to point to the new application server with the new code. Once you are sure nobody is using the old application server, you can shut it down. This, of course, relies on your ability to get that setup in place. If you are on a budget, you might be able to do it all on a single box. For instance, you could use nginx as a reverse proxy to your application on the same box. Getting that in place could potentially cause a tiny window of downtime - not sure if that's acceptable. Then you might be able to set up the new application on the same box with a different port - again, I'm not sure if that would work for your setup. Anyway, the reverse proxy approach is a pretty common one, and one of the great reasons for deploying to the cloud. You only pay for the short period of time when you need both boxes.
You should make sure that your new website launches all at once and that you set up the proper redirection rules for all previous pages. Once you are launching the new website, pick a time at night where you have low traffic volume, and simply upload all the new code at once to the webserver. This eliminates the fear you have of the "supporting files not uploaded yet". One of the key things to do is make sure all your old pages redirect and map over to new pages on the site just in case anyone clicks into your site using external links.
Two good resources to read:
http://www.rise.net/blog/ideal-way-launch-website-rebrand
http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html
The best methos is to upload the site via FTP, and if you have RD access to login into the Windows server and to copy the new site for a few seconds. In this way you will not have any downtime as when you directly upload the site via FTP.
A client has asked me to update their EE site. On the homepage, there is a small slider that shows text data. For each slide, the original creator of the site made entries and is displaying all of them in the slider as a channel called footerstats. The footer template references this channel.
I went to each entry, changed the info, saved. I then updated the footer template and channel just for the heck of it. I even cleared all caches. Still, the old info is still showing up on the homepage. Any tips? I am new to EE.
Did you clear the cache folder directly instead of via EE? Sometimes I notice that with aggressive browser caching (Chrome) and sometimes just general clearing, it helps to actually manually delete the contents of the cache folder instead of just using the EE interface.
Have a look in the add-ons -> modules list to see if CE Cache or Template Morsels are installed. Those are the two third party caching add-ons that immediately come to mind that could directly lead to EE's "clear caches" not changing what you're seeing in the site, as they cache to the database. You could also look for Stash - that also saves data outside of EE's native caching, but in a different manner than CE Cache or Template Morsels.
I would suggest looking for CE Cache and clear any cache if it is installed.