Closed dannystarkDE closed 3 years ago
Is it possible that the plugin also affects the thumbnail size in the backend? Currently, images are no longer reduced and always included in full size.
Yes, it actually does affect the sizes in the backend. Because Timmy hooks into how images are generated in WordPress core, this also affects the admin. When thumbnails are loaded in the backend, Timmy should load the thumbnail size.
I just checked with the newest version of WordPress and your filter settings. For me, all works as expected.
The HTML that I see in your small developer tools preview looks like you’re looking at the markup for the big preview for an image. Could that be the case?
Compare to this. Here, it’s supposed to load the full size of the image.
In cases like these, it’s also helpful to look at the Network tab in your browser console and filter it by graphics to see what actually gets loaded by the browser:
If the full image size is loaded in your case, I’ll have to look into that more closely.
Hey. Thanks for your answer. I found my mistake.
It looks like the Timmy Config was too deep down in the functions.php. (At the end of the "function theme_supports()") Now i include the Timmy config in the Timber Constructor and everything worked as expected.
Hey @dannystarkDE
Thanks for posting how you solved this issue. I think it’s good to configure Timmy as early as possible, which means not putting it into a special hook.
Hello!
I have a question about the image size in the Media Library. Is it possible that the plugin also affects the thumbnail size in the backend? Currently, images are no longer reduced and always included in full size.
What could be the reason for this?
My config: