I have been developing the website with Silex and I experienced that the frontend just doesn't update immediately when I upload an image from the backend. Even I set the cache mode to be false it seems not to fix the problem.
So how can i disable cache/ refresh cache so it can update at frontend side? Please let me know if more info is needed.
Related
I've installed my laravel project on shared hosting. Everything was fine until when server starts loading old pages and scripts after uploading changes.
I've checked and cleared browser and laravel caches every time but the problem still. Then I've deleted laravel files but the server still loads main page while it should loads main directory content.
Now after installing laravel again the server loads the directory content for main url and works fine for other laravel routs.
The most confusing issue is the when trying to refresh browser several times, it loads the actual pages for one or two times then it back to load old cached files.
That was because of cloudfare caching.So I've to develop locally then upload the final release to remote server
Make sure that you are not using any caching services for page caching(actually page caching is a good feature), if yes please try invalidating the page cache.
If you are using Cloudflare, purge your cache. you can purge the cache of objects or full objects.
I created a website here - http://sdl2.alphalogichq.com/index.php/customer/account/login/
When I enter any email, for ex. abc#xyz.com and password - pass123 (both of them are wrong), it should ideally give me error Invalid login or password.
But here it just loads from cache and doesn't show the error. I need to force reload (CTRL + F5), and then it shows the error.
How can I change the behavior so it works properly?
I found X-Cache, X-Cache-Hits and X-Cacheable in response header that shows you are using some kind of caching. This is caching is implemented in server not by magento. I think this is Varnish cache as i found X-Varnish response header.
Cache HIT occurs when page load normally and cache miss occurs when you reload when load with CTRL+F5.
To resolve this issue ask your web hosting provide to disable Varnish cache. And i suggest you to use magento's cache and you can use Lesti FPC which is better to optimize website.
I am working on a Joomla 3.3.6 site and after making changes to articles I have to keep manually clearing the cache
This was not the case before we had issues server side
Is their something I can do
My system settings are:
cache off
cache handler file Time 15
Please help its driving me crazy
Thanks
E
We having Magento Enterprise and using Redis for caching. any changes on site with contents, Images is not reflecting (old contents/images showing) until browser get cleared.
Please help me to find exact root cause, it this issue related to key expiry?
Thanks in advance.
I have a magento install on a staging environment, everything is working except the catalog backend page and the frontend layered navigation. Look at the image below. There is a backend within the backend. When visiting the page it refreshes to infinity. See this identical problem
My first guess is there is a bug in the template file but an identical template file on my local machine does not cause any issues. Additionally the database between my local and staging site are identical minus the core_config_url. The only difference is local I am running Apache and on staging I am running nginx.
The second issue which I imagine is related is that the filters on the frontend catalog page dont work. They are visible but clicking on them reloads the page without changing the products.
Any help would be appreciated. Thanks
UPDATE: After switching from NGINX to Apache the issue disappeared. I still would like to figure out what is causing the problem
I take for granted that you had already tried different browsers/clearing your browser cache and Magento cache (empty the cache directory), etc.
Are you sure you put the correct value in the cookie_domain setting? Many users that had your same problem seem to have setted up an incorrect value in that setting.
Take a look here and let me know.
I have found that usually this is caused by a server-side error on the ajax request. If there is any kind of error response returned, it will just continue to spin. Either check your Chrome console for a 500 response, or look in your server's error logs.