Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Make the {% image %} tag support other images known to django, not just wagtailimages
See original GitHub issueFor example on a current project, users upload a photo to represent an event, but events are submitted by the public and not everyone will have a suitable photo, so a placeholder is displayed alongside their event instead.
That placeholder image is something the developer has had to create, but as event photos get displayed in numerous places, we need to create numerous versions of that placeholder to suit the placement, which is tedious.
It would be great if the {% image %} tag could be given a path to a static image, and automatically generate the images at the dimensions we specify.
Issue Analytics
- State:
- Created 9 years ago
- Reactions:8
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Curious whether this is going anywhere, or has been forgotten about or replaced with other functionality that I’m not aware of?
I’m VERY new to wagtail, but already really wishing I could pass a static image path to the
{% image %}tag so that I can resize user avatar images as needed in my templates.On a more practical point, users may be integrating Wagtail with existing products and may find it tedious to have to install multiple thumbnailing tags. If wagtail could thumbnail anything, it could be a replacement.