Magento程序化刷新缓存无效，手动操作正常问题求助

Hey there, let’s troubleshoot this frustrating Magento cache refresh issue together. It’s weird when your programmatic approach doesn’t match the backend button’s behavior—here are targeted steps to figure out what’s going on:

1. Expand Cache Type Coverage (or Use Full Cache Flush) #

Your current code targets 8 specific cache types, but the backend’s "Flush Magento Cache" button does two key things your script might miss:

• Cleans all Magento cache types (not just the 8 you listed)
• Flushes the entire cache storage (e.g., file system directories, Redis/Memcached databases)

Try replacing your per-type clean with a full cache flush that matches the backend button’s logic:

// Matches the "Flush Magento Cache" button's behavior exactly
Mage::app()->getCacheInstance()->clean(Mage_Core_Model_Cache::CLEANING_MODE_ALL);
Mage::dispatchEvent('adminhtml_cache_flush_all');

If you still want to use per-type cleaning, expand your $types array to include all available cache types (check System > Cache Management in the backend for the full list—common missing ones include full_page, config_webservice, or extension-specific caches).

2. Verify Permissions & Execution Context #

When you run your script (especially via CLI), it might be using a different system user than your web server. This can lead to:

• Cache files not being deleted (since the CLI user doesn’t have write access to web-owned cache directories)
• New cache files being created with permissions the web server can’t read

Double-check that:

• Your script runs with the same user permissions as the web server (e.g., www-data on Apache)
• The var/cache and var/full_page_cache directories have correct read/write permissions (typically 775 or 777 for development environments)

Also, confirm the adminhtml_cache_refresh_type event is triggering all necessary observers—some extensions hook into this event to clean their own custom caches, and a misconfigured dispatch could leave those caches intact.

3. Handle External Cache Storage (Redis/Memcached) #

If you’re using an external cache system like Redis or Memcached, the cleanType() method might only invalidate Magento’s internal cache entries, not the entire external storage. The backend button sends a full flush command to these systems, so add storage-specific logic to your script:

// Example for Redis (if using Cm_RedisCache)
if (Mage::helper('core/cache')->canUseRedis()) {
    $redisBackend = Mage::getSingleton('core/cache')->getBackend();
    $redisBackend->flushDb();
}

4. Debug Cache State Before/After #

Add debug code to confirm if the cache is actually being cleared. For example:

// Check if the config cache (which controls controller registration) is cleared
$configCacheEntry = Mage::app()->getCacheInstance()->load('config_global');
var_dump($configCacheEntry); // Should return false if the cache is properly cleared

// List remaining cache entries to see if your controller's config is stuck
$cacheDir = Mage::getBaseDir('cache') . '/' . Mage::app()->getCache()->getFrontend()->getId();
var_dump(scandir($cacheDir));

This will help you narrow down whether the issue is with cache not being cleared, or your new controller failing to register even after a cache refresh.

Yes, sharing your full script code would absolutely help! For example:

• Are you initializing Magento correctly at the start of your script?
• Is the script running inside a custom controller (which might be cached before your refresh runs)?
• Are there any error logs (in var/log/) that show issues during cache cleaning?

内容的提问来源于stack exchange，提问作者Vitali