phantom plugin

I discovered a plugin was not updating after changes are made. It will save the plugin just fine. The cached version does not update. So I cleared cache, in browser also, restarted just to be sure. Still wouldn't update so I deleted that plugin and it still wont go away. I can clear cache just fine but it comes back even though now it does not exist.

Where is it picking this cached plugin back up from?

You manually deleted the folders under the core/cache directory, or just refreshed the cache from the Manager menu?

Yes tried in the manager and also deleting them manually also. No problems performing either. The problem comes when it regenerates them.

I've managed to fix it. I'm trying to duplicate it again so I can confirm my suspicions. I believe this happened when the cache system settings were adjusted.

I could update the plugin before the system setting were changed. It wasn't until I adjusted them again that it went away. I just don't know right now which one caused it to lock up.

If you couldn't change the plugin, maybe you can't delete it either. You'd have to check in the modx_site_plugins table in the database to see if you really deleted it (I'm guessing not). So it's appearing to come back because it was never really gone.

I can't think of a System Setting that would do this. Are you sure you weren't messing with the permissions on a Policy, or changing the Policy in an ACL entry? That would explain what's happening.

To see if it's permission-related, try this:

• Update your user profile and make yourself a sudo user.


• Flush permissions and flush all sessions.
• Delete all files in the core/cache directory
• Log back in.

If your problem is gone, it was a permission/policy issue.

If you couldn't change the plugin, maybe you can't delete it either. You'd have to check in the modx_site_plugins table in the database to see if you really deleted it (I'm guessing not). So it's appearing to come back because it was never really gone.

I thought the same thing, checked the database and it was not in the table modx_site_plugins. Cleared cache in manager, confirmed cache was gone on server. Reloaded a page and the old cached version of the plugin came back into the cache. That's when I came to the forum in defeat.

The system settings I was tweaking were cache_scripts, cache_context_settings and cache_alias_map. When I get a little more time to debug it, I will see which one it was or what combination of them it was.
Once these were changed back to defaults, everything worked fine again.

Quote from: geeble at Aug 30, 2014, 06:00 PM

The system settings I was tweaking were cache_scripts, cache_context_settings and cache_alias_map.

I suspect that since the cache was not cleared before changing cache_scripts. The plugin cache somehow got locked into some place in the database. (IDK if this is even possible) And since cache_scripts was turned off there is no reason for it to flush cache when updating the plugin, so the old version stays in cache even though it has been updated.

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.

I have, on more than one occasion, actually done something in a different site than I thought I did, having the wrong tab open in my browser or FTP client, and wondered why it wasn't working. Those range from clearing the cache to editing a .css file.

I've worked on sites I thought were connected to one db when they were actually connected to another one. I couldn't figure out why my changes to the site weren't showing up in the database.

Is it gone from the _transport_packages table as well?