Muut Archive Legend
@Muut · Joined 9 years ago · 18337 posts · 3878 topics · 137 reputation
Badges
Recent posts
-
What happens with images, generated and cached, when changed?
· 11 years ago
In case this points out something of an issue: I have repeatedly and manually cleared images from the cache without the newer version being taken into account. I published blog posts (antimatter them
-
What happens with images, generated and cached, when changed?
· 11 years ago
Thanks a lot Andy, I am checking with my hosting provider to navigate to the root directory. That will clearly help me better administrate my grav instances) Now I have changed the images several time
-
What happens with images, generated and cached, when changed?
· 11 years ago
Every time you change something that is applied to the image, it should re-cache. For example, say you have: {{ page.media['myimage.jpg'].quality(85) }} Just changing one paramater: {{ page.media['my
-
What happens with images, generated and cached, when changed?
· 11 years ago
Hi Andy, I have experienced a recurring issue with images when I want to update them (e.g. to upload better compressed versions). I confirm that keeping the same file name doesn't flush the image cach
-
What happens with images, generated and cached, when changed?
· 12 years ago
The easiest and most reliable solution is to flush the Grav cache with bin/grav clear-cache command. This will clear all the generated images and force them all to be regenerated. We use the Gregwar
-
What happens with images, generated and cached, when changed?
· 12 years ago
You just need to delete the image it has generated. If you use firebug or inspect element feature you can easily track down where it is getting the header image from. It looks something like this: i
-
What happens with images, generated and cached, when changed?
· 12 years ago
The fact that Grav can generate optimized images at specified sizes is great, but what happens to them once they are generated? Lets say I want to give a new header image a try, so I load a new heade
-
Cannot link media using absolute or relative URLs
· 11 years ago
Okay, I understand. Thanks for your time.
-
Cannot link media using absolute or relative URLs
· 11 years ago
Well you have lots of options really: 1) add another header variable for imagepage like: imagepage: "/images/folderA" imagelink: "imagea.jpeg" Then combine those two in the template: {{ page.find('pag
-
Cannot link media using absolute or relative URLs
· 11 years ago
Wow, what a qucik response - thanks. I get the logic, thanks. However I have an issue here - what if I want to have subfolders underneath images, because loads of images should be stored and I want to