OK, I took a little time to confirm which setting was doing this. With cache_context_settings set as No, I cannot update the plugin. What I mean is: The plugin saves to the database fine. The old version of the plugin gets locked into the cache. Clear cache either through the manager or deleting cache folder both work. The old version of the plugin will come back in to the cache. Checking modx_site_plugins table, the plugin is updated in the table and there is no other entry for the older version. The only way to get it to update is to set cache_context_settings back to yes and clear cache.
Maybe you have a non-standard location for the cache. The default is core/cache, and if you delete all files in core/cache and the plugin is not in the DB, there's no place for it to be coming from unless you have the cache in a different place, or you're running a separate cache (e.g. Varnish or memcached) on the server.
Cache is the standard location. No other caching is installed.
Is it gone from the _transport_packages table as well?
This is just a standard plugin not an extra.
I have VersionX installed and thought that might be the culprit. So I uninstalled it but same results from these tests.
I am stumped as to where it is getting the old version of the plugin from to regenerate the cache for it. The problem is not holding me up any as I was just tweaking settings to see what kinds of results I would get from them.
