I would like to stop certain images from being processed by Kirby and being copied to the media folder. I have a site that uses Krpano which allows zooming in on very very high resolution images, by using sets of tiles at different resolutions. These have been manually placed into the content folders, and are 300mb each.
Theres about 20 of them so, in the interests of saving space, I want to stop Kirby moving them to the media folder. This will save a few gigabytes, and make the site perform faster, since Kirby is not needlessly processing these images.
Is that possible? They are in a subfolder called “Tiles”, under each page. So bascially if the pages content folder is called “Tiles”, I want Kirby to ignore any images underneath that, recursively.
Nope, not at all. It happens when I browse the page and zoom in, then i see the tiles being created in the media folder. I’m not directly accessing those images in templates or snippets or anywhere at all, nor where they uploaded via the panel
Theres a “viewer” plugin from krpano in the template that loads them in from an XML file. It injects a canvas element onto the page via javascript and loads the images into that. When pano accesses the images, kirby moves them to the media folder.
I didn’t clear the entire media folder, just the folder for the page in question. The images inside are 1:1 copies of the original.
Perhaps its ignoring the plugin. How can see which plugins Kirby is using (as in ones its succesfully recoginsing)?
If i pull up the browser inspector and look at the images on the page, its says they are coming from http://website.test/macros/some-project/tiles/l6/08/l6_08_13.jpg. If i hit that file directly in the browser, it redirects me to the copy in the media folder:
I don’t think Kirby allows you to access files directly in the content folder (see the .htaccess).
If you don’t manage the images in the panel, you could move the tiles folder outside the content folder. Access images there directly if that is a public folder or define a route to it.
The .htaccess directive only blocks access to .txt/md/mdown files, you can access files in the content folder (unless you put the content folder outside the web root)
@jimbobrjames the url to the images should contain /content/ otherwise you go via the media routes. The fileurl component can be overwritten by every plugin that was loaded after yours (alphabetic order). There seems to be a conflict with that, so no valid solution.