-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cv ext:list -L returns incorrect results on WordPress #46
Comments
Just to cover our bases... the cache is there to avoid filesystem scans. If you manually update the filesystem, then it won't pick up on the new things... until the cache is cleared. Some interesting edge-bits:
In your example, could it just be that the Drupal site had a more up-to-date cache than the WP site? Aside: Operating under the theory that
|
Hmm, this isn't what I'm seeing. I wonder what the difference is. Note that the extensions in the extensions folder show as "Missing":
|
If they're all missing, then maybe something went wonky with the parent dir's config? Might be worth double-checking the paths:
|
I think this is the same bug referenced in https://lab.civicrm.org/dev/core/issues/385. I'm not sure I'm going to move on this at the moment, but I'm cross-referencing them in case one day someone does :) |
This seems to be a problem with the core caching class, but I was unable to trigger this problem except through
cv
so I'm filing it here.Using
cv ext:list -L
on WordPress only returns the extensions that ship with core (iats and api4). The problem seems to be in this line, because\CRM_Extension_System::singleton()->getFullContainer()
returns a bad cache. Below is the output from placingprint_r($containers['default']->cache);
at this line. Note howvalueCache['default']
is empty under WordPress:WordPress (incorrect)
Drupal (correct)
The text was updated successfully, but these errors were encountered: