Comment in code says:
Test for the page_cache module, which is required for cache invalidation.
This is not valid. Page cache module is not needed when having an external caching solution.
Warning says on status page:
Please install the page_cache module. The page cache acts as a 'second layer of defence' by keeping copies of all generated pages, which protects you from widespread performance degradation in case of emergencies.
This should be bad practice, caching a lot of objects that you do not need to cache, if, for instance, varnish has problems, this will not help at all in a high traffic situation. It could do things even worse, if using db for cache, also the warning could make devs believe that Page cache module is needed for make purging work.
Suggestion:
Remove PageCacheCheck.php
| Comment | File | Size | Author |
|---|---|---|---|
| #18 | purge-2803607-18.patch | 2.54 KB | krzysztof domański |
| #14 | Remove-PageCacheCheck-2803607-14.patch | 2.54 KB | jjcarrion |
| #9 | Remove-PageCacheCheck-2803607-9.patch | 2.53 KB | jjcarrion |
| #3 | Remove-PageCacheCheck-2803607-2.patch | 2.72 KB | misc |
Comments
Comment #2
misc commentedComment #3
misc commentedComment #4
wim leersIf the maintainer decides to keep this, then they should at least document very clearly/explicitly why they think this is necessary.
Comment #5
misc commentedComment #6
caspervoogt commentedI agree with this suggestion.
Comment #7
dragonwize commentedThe description of the page_cache module in core even reads:
Comment #8
moshe weitzman commented+1 to removing this warning. Its a bit too opinionated IMO.
Comment #9
jjcarrionReroll to work with 3.0.0-beta9
Comment #10
gaëlgIf I understand well the guidelines (https://www.drupal.org/node/156119), it's RTBC, right?
Comment #11
mpp commentedRTBC++
"The page cache acts as a 'second layer of defence' by keeping copies of all generated pages, which protects you from widespread performance degradation in case of emergencies." => as mentioned in the issue description there's no use for page_cache when using an external cache.
Comment #12
lisa.rae commentedMarking Needs Work, patch is failing testing.
Comment #13
misc commentedIt is not just the pull request that is falling testing, it is also the main main 8.x-3.x-dev that is failing:
https://www.drupal.org/pift-ci-job/1595419
Comment #14
jjcarrionReroll to work with 3.0.0
Comment #15
mpp commentedThanks for the reroll, setting back to rtbc.
Comment #16
zero2one commentedRTBC
Comment #17
simepage_cache is a really bad decision on some of my sites. So suggesting that administrators install purge is a big problem for me. :D
Could this get merged?
Comment #18
krzysztof domańskire-rolled, it was unnecessary, the same as previous patch.
Comment #19
japerryI also support removing this unneeded check.
Comment #21
nielsvm commentedThanks everybody, it is gone now due unpopular demand :-) :
https://www.drupal.org/project/purge/issues/3236847
Comment #23
murat_halici commentedRemoval of PageCacheCheck in 8.x-3.1 is causing a fatal error in all of our sites due to cached plugins.
Clearing caches resolves the issue. However, I was wondering if anyone knows of a way to prevent the error from occurring without having to do that.
Comment #24
ralphvdhoudt commentedAdded a dummy page_cache plugin file to be used as a temporary patch when updating/deploying your code
Fixes:
Uncaught exception 'Drupal\Component\Plugin\Exception\PluginException' with message 'Plugin (page_cache) instance class "Drupal\purge\Plugin\Purge\DiagnosticCheck\PageCacheCheck" does not exist.' in /mnt/www/html/cbappcontent/docroot/core/lib/Drupal/Component/Plugin/Factory/DefaultFactory.php:97Patch is not intended to be included in the module itself