Magento cache is turned off but still caching files - php

I am running magento 1.5.1 and when turning off caching for debugging, files are still being cached.
Can anyone advise on how to fully disable the caching mechanism in magento?

delete everything under var/cache/ to fully flush your file based cache. If your site is using APC, EACCELERATOR, MEMCACHED or other cache engines you might need to clear or disable those as well

Related

CSS / HTML / JS not updating XAMPP (local development)

I've tried to install Magento 2 locally using XAMPP. This works fine, except for the fact that when I alter my CSS, HTML or JS, XAMPP won't get the updated files. It just takes the file I initially created with it's content, but not the updated version.
I think this has something to do with caching of Apache itself? I read something about disable cache using .htaccess (http://httpd.apache.org/docs/2.0/mod/mod_cache.html) but I can't figure out how to implement this.
Anyone knows how I can fix this?
Flushing cache doesn't work. Deploy static content may work, but I don't want to do that every time I make one minor change in the CSS (when I worked remotely, I did not have to do that either)
I think this problem is not Magento related, but rather something with XAMPP (probably Apache).
I have developer mode enabled.
Press Ctrl-F5 to hard refresh the page (to not use Browser's cache).
If you still see the previous pages or changes, then Apache has
mod_cache caching them, or PHP has its opcode cache settings set to
not refresh changes for X amount of time.
Taken from Xampp and Ampps don't reload files when changed
If mod_cache that is causing the problem then this might help you implement the fix How to disable cache of Apache?
This is not a caching issue, but rather the deploy mode you're using.
You are probably in default mode, in which case you will have to deploy static content every time, however you can switch to developer mode.
https://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands-mode.html
This will stop magento having the need to generate the static content as it's done on the fly via the use of symlinks etc.
bin/magento deploy:mode:set developer
Or alternatively you can manually set this inside
app/etc/env.php
If developer mode isn't working it's more than likely down to permissions etc
Delete all files inside pub/static apart from the htaccess file, and make sure it's writable
In developer mode, M2 does not generate static files. It should create symlinks to them from the various modules. If you however have ran setup:static-content:deploy and have those files in place, it won't update them. Try to delete only those files inside pub/static folder on which you've worked and see if Magento links to them. If you delete all contents of pub/static/ folder, pages will take very long to load in browser.

Extension Modules disappeared

I don't have any error logs or other info that I can figure out what's the issue, is not the first time that it happens. In my case is when I installed an extension, basically I do what is recommended after uploading the extension, clean cache and login again on admin, and everything is ok when I installed, the only problem is that sometimes the module disappeares has nothing was installed, and only shows again if a go and "clean Cache" on the admin panel.
If you use multiple web-nodes, separate admin nodes then it can be possible that the new codes might have not deployed to one of your servers and the old xmls are cached.
And I understand that you are using redis as your caching layer, so sometimes flushing the cache from magento admin panel doesnt flush the entire redis cache.
So you would need to try to connect to the redis server using redis-cli command then issue 'flushall' there.

Magento plugins disable/enable problems?

I am noticing really weird problems after installing plugins.
Sometimes the plugins get disappeared in the backend when we refresh the backend and sometimes it appears in the backend.
I haven''t used magento connect for installing the plugins.
Can this be a caching problems, even though we are using AWS for hosting, we have redis cache.
Also after this whatever plugins we installed also has the configuration in the frontend, So once it has disappeared in the backend, this thing also gets disappeared in the frontend as well.
This problem is really gettting more weird and losing conversion very drastically.
Please someone let me know what can be the issue?
Switch off your Redis and Magento cache then check first.
if this problems does not persist( Try with Magento cache on but redis off ) then you need to check your cache configuration.
Generally it has been observed that on times redis configuration goes wrong resulting in such issues.
Before extension installation is always highly recommended to turn off all cache (magento cache, redis, apc, etc.) and compilation. After installation is recommended to flush magento cache storage.

Troubleshooting Joomla 3.3.4 Cache

This is the first time I've had this problem with Joomla cache on v3.3.4. What issues I'm having is when I enable cache under Joomla configuration either with conservative or progressive caching using "file", "apc" or "memcache" I keep getting the same results when I load my pages I start losing display modules then I loss the home page scrolling, so if you were to try scrolling down you can't scroll. This usually happens 2 to 5 minutes after you enable cache. I don't have "Joomla - Cache" or "Jotcache" enabled to get this situation.
It's very frustrating because I've run out of check list.
If I disable and clear cache I get everything back.
I checked all folder properties for right, all correct.
I've tried xcache, memcache, memcached and apc but issue still exists.
I installed from a previous backup and still nothing
I check php open_basedir for restrictions but it's setup correct.
I have all settings and configuration as specified from Joomla documenation
I've browsed with ipad, iphone and PC firefox, chrome, opera and same issue on all
When I tested cache with memcache, apc, xcache I uninstalled memory cache method as listed "memcache, apc, xcache" to avoid cache conflicts.
I did read everything I found from internet searches and nothing has resolved this issue.
I've even monitored cache and checked each file for issues thinking it might be php memory_limits with watch -n 2 ls -ahl and found nothing.
The template is compatible and working correctly without cache.
When I turn cache off completely it continues caching for about 5 minutes then I can clear cache and I get scrolling and modules back.
I do have sh404sef which is caching URLs and I've disabled/uninstall sh404sef without fixing issue.
I disable modules one by one to figure out the problem of cache but still nothing.
I have checked logs but on apache, php, and other daemon logs but no errors
Apache is v2 and running php5-fpm
I have RSFirewall installed but uninstalled and even disabled and still having cache issue.
I do have system cache plugins disabled during these tests so it's not assignments to end of system-cache plugins.
I have tried different modules and plugin assignments in Joomla but still nothing
I don't have any other cache plugins during my testing.
All cache plugins have been disabled during my tests.
The only thing I can think of is when the cache re-writes during a refresh it doesn't correctly write the data to cache again.
Any help would be appreciated
Problem was the template issued - Template has scrolling effects for Jomsocial which needs to be disabled but not documented in Joomla template. The non-scrolling pages resolved the caching issues as well.
Problem resolved.

Magento caching new file

I have created a php file and uploaded it to my Magento server but it's being cached. It's a standard .php file, but whenever I amend it, nothing changes. This has only just started happening.
Any ideas how I can stop this from happening?
Sounds like your server hosts have installed APC or another "opcode" cache. I'd start with clearing the APC cache, and if that doesn't help then escalate to your server host's support system. Being able to deploy new code is a reasonable feature to want in a server.

Categories