#52280 closed defect (bug) (invalid)
Persistent object caching is not enabled
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Site Health | Keywords: | |
| Focuses: | Cc: |
Description
I am a retired veterinarian. Two month ago, I made the mistake of attempting to enable persistent object caching. As soon as I did, all images disappeared from my website. I restored my site to the previous day. That had no effect. My images were still gone. If I disabled Classic AMP, the images came back. If I installed AMP for WP, I had no image loss. I struggled for 2 months with Inmotion Support, Boldgrid Support and internet help pages attempting to return to Classic AMP. Finally, a savvy IT guy with Inmotion hosting deleted some files and my images were back. YOU NEED TO PUT WARNING OF POSSIBLE DANGERS IN FOLLOWING YOUR ADVICE! Now I totally ignore Site Health. I am even afraid to update AMP because I do not want to go through the grief I experienced the last time I followed your advice.
Sincerely, Ron Hines DVM PhD
Hello @ronaldhines and welcome to Make Core Trac.
Sorry to hear that you have had such trouble.
This Trac is a tool for developing the WordPress core software. WordPress itself emits no warning telling users to enable object caching. This message is added to Site Health section by your AMP plugin. It's the makers of that plugin who can change that recommendation.
Adding object cache to WordPress can certainly be tricky, and can be damaging if not made properly. Checking required support for the various kinds of it with your hosting provider is highly recommended. To inform about this is a task for the makers of caching plugins.
So I have to close this ticket as "invalid". Your warning/recommendation is highly valid, but have to evaluated or acted upon by makers of the AMP plugin in question. Nothing we can do from here.