Sadly nothing is generated — not on the fly when loading a page nor through the panel even when uploading new media (the same media that is successfuly converted with the resize pluging).
Yes, which makes it all the more odd why Kirby cannot seem to generate thumbs on its own.
@texnixe do you know which lines of code in Kirby trigger thumbs generation when a url is called?
I added echo ("ImageMagick command: " . $command); to ImageMagick.php at line 161.
This has revealed that the command is in fact not being triggered.
The command is however triggered by Blurry Placeholder Images for Kirby plugin, which is recorded in the log thanks to the echo ("ImageMagick command: " . $command);.
In short: I need to identify why the thumbs code is not being triggered like normal.
This may only have been the case for the Blurry Placeholder Images for Kirby plugin, which is succesfully generating placeholder thumbs when a url is called — just the actual image isn’t having it’s thumb generated
My understanding is that thumbs method is used to generate the “thumbs” for all page media? (but correct me if I’m wrong!)
So the issue is that media uploaded through the panel results in no “thumbs” being generated in the /media/.../page directory (nor when a URL is called). Same for the panel.
One last pathway I could try. Do you know how I might log an error in the Kirby code so that any failure of media thumbs generation when uploading an image via the panel might be seen?
Hey, just wanted to bring this thread back from limbo to say that I was able to solve this issue on my end with the thumbnail generation not working on CloudPanel by removing some code from my nginx Vhosts config file. Specifically, I removed the following lines:
I was cracking my head open with this one, but thankfully it turned out to be a simple solution.
I figured this one out by seeing that I could not access any file with the extensions mentioned in that line. I asked ChatGPT about this and it kinda explained it pretty well:
This location block is defining a regular expression that matches any URL path that ends with a file extension specified in the parenthesis. The directive add_header Access-Control-Allow-Origin "*", adds a response header Access-Control-Allow-Origin with a value of *, which allows any website to access the content of the resource.
The expires directive sets a cache expiration time for the resources, which is set to max, indicating that the resource should be cached indefinitely. The access_log directive is set to off, disabling access logging for these types of resources.
It’s possible that this block was causing issues because it was too broad in its matching and was potentially interfering with other parts of the configuration. However, if you want to enable the Access-Control-Allow-Origin header for specific resources, you can modify this block to match only those specific resources instead of matching all files with certain extensions.
Hope this helps someone else who may be experiencing a similar issue with Kirby in CloudPanel servers/sites.