Users report a bug where, after increasing the image size limit (e.g., from 4096KB to 12288KB), posts still display the misleading error message “(image larger than 12288KB)” — even for images under the new limit. Stephen notes this occurs despite rebaking not resolving the issue, and resorted to appending query strings to force re-validation. sam questions whether a rebake should be triggered automatically when limits change. Stephen confirms rebake and rebuild HTML didn’t help, emphasizing the message is inaccurate and unhelpful. renato confirms the issue and shares a workaround: deleting the large_images array from post custom fields via Rails console, which resolved it for them. The core problem is stale or cached file size data causing incorrect error messages after config changes.
I embedded a series of URLs to some particularly large images, and when I checked back the expected ‘image larger than 4096kb’ message was displayed next to the links.
As it’s a private instance I amended max attachment size kb and max image size kb to 12288kb (12MB) and went back to the topic.
Now all of the images instead bear the message (image larger than 12288KB) despite only one being >12MB.
Steps to repro:
Link a large image which exceeds limit
Wait until file sizes are checked and local download attempted
I couldn’t wait for a rebake as the embedded images had turned into links and people needed to see the imagery. I can retest later to see if it’s the case.
The bug is that the error message reflects the file size, even if the file isn’t larger than the new specified value. I get bringing the value into the message, but it’s not helpful if it’s not accurate.
Rebuild HTML definitely didn’t work.
In the end I threw a garbage querystring on the back of the image URLs so that they would be considered different and be checked again.