Open kenmanheimer opened 6 months ago
@kenmanheimer Thank you for your report.
We used this add-on mainly with a Plone 4 back-end and it requires eea.depiction Plone Backend add-on.
Now, using image/image_*
depiction is in general a bad idea, because you will have issues with cache invalidation, SEO, etc.
That's why, if you're using Plone 5/6, you should rely on Image scales. @@images/<scale-uid>.png
@kenmanheimer Here is an example of an output from RestAPI on https://demo.plone.org for an Image content-type:
{
"@id": "https://demo.plone.org/2-1.jpg",
"@type": "Image",
"UID": "3b75a909666a4dcb8c20fc8237beb786",
"image": {
"content-type": "image/jpeg",
"download": "https://demo.plone.org/2-1.jpg/@@images/image-1440-a7251717990b93362dccd2c30e0485a9.jpeg",
"filename": "2-1.jpg",
"height": 960,
"scales": {
"great": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-1200-3e3e92cd46e7fffcac3f6aa8bf37780f.jpeg",
"height": 800,
"width": 1200
},
"huge": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-1600-881d67e7a229ea7d1099c03423a73a43.jpeg",
"height": 960,
"width": 1440
},
"icon": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-32-579e7393ca93608184dd1527b2dfb468.jpeg",
"height": 21,
"width": 32
},
"large": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-800-af233b2e542d0b5d03fd6b30baa9cd0f.jpeg",
"height": 533,
"width": 800
},
"larger": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-1000-a6d867dee85e30094910db4becdb52a8.jpeg",
"height": 666,
"width": 1000
},
"mini": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-200-794d60fa226f49c38baea97e14189945.jpeg",
"height": 133,
"width": 200
},
"preview": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-400-84e647c058830c50fec90f68ccc02317.jpeg",
"height": 266,
"width": 400
},
"teaser": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-600-81283d7b7abaf9eaec93291cd849bc85.jpeg",
"height": 400,
"width": 600
},
"thumb": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-128-bcd63489d2996195c82df81d0460397c.jpeg",
"height": 85,
"width": 128
},
"tile": {
"download": "https://demo.plone.org/2-1.jpg/@@images/image-64-df2ee3b64d8e882fd502725819d3af14.jpeg",
"height": 42,
"width": 64
}
},
"size": 168735,
"width": 1440
},
...
}
Thanks for this info. I have specific responses which I will include inline with your cited text.
We used this add-on mainly with a Plone 4 back-end and it requires eea.depiction Plone Backend add-on.
I knew about and installed the Plone backend add-on.
Now, using
image/image_*
depiction is in general a bad idea, because you will have issues with cache invalidation, SEO, etc.
I did not use image/image_*
, nor did I intend to do so. It was web indexing spiders who visited those addresses and triggered the crashes.
This is why it is important that you make it clear that this add-on should not be used except in special cases! (Eg, use only if you need it for use with a Plone 4 backend?)
That's why, if you're using Plone 5/6, you should rely on Image scales.
@@images/<scale-uid>.png
Please make this kind of thing clear in the README so others don't make the mistake I made of using volto-depiction
when I didn't need it, and in fact are going to cause experience frontend crashes every time the site is indexed!
With
volto-depiction
installed visits to<path-to-image>/image_mini
or.../image_large
or any applicable.../image_*
causes Volto to crash. I am including a copy the backtrace from the instance launch terminal at the bottom of this issue.The problem happens when
volto-depiction
is included in my build and stops when I remove it.This is a critical bug because indexing robots trigger this, crashing Volto sites at random (and preventing indexing completion besides). Very not good.
Here's the sample backtrace: