Plugin Contributor
Brian
(@brianjessee)
Hi,
Thanks for using our plugin.
I am seeing this css:
.tribe-events-list .tribe-events-event-image {
float: none;
margin: 0 0 8px;
width: 100%;
}
Our plugin by default sets that width to 30%. So changing that back to 30% will fix the issue.
If you would like to keep that try adding this:
.tribe-events-list .tribe-events-event-image {
width: auto;
}
That is width: auto; instead of width: 100%;
Thanks
Sadly that does not address the question. It does make the images not blurry because it makes the resized image load in it’s auto resized resolution. The key question is we do not understand why the featured image is being auto resized at random. If you look at some of the other events on the feed there are ones that are loading the actual featured image for the event that we chose where as the ones that we are concerned with are loading some “filename-300×44.png” rather than the chosen “filename.png”. Hopefully that clarifies the question.
Plugin Contributor
Brian
(@brianjessee)
Oh I see now. That is controlled directly, but a function so can only be changed my editing the template:
You can follow our themer’s guide:
https://theeventscalendar.com/knowledgebase/themers-guide/
And move and edit this file:
the-events-calendar\views\list\single-event.php
There look for this line:
<?php echo tribe_event_featured_image( null, ‘medium’ ) ?>
And you change medium to large, full or a custom size.
That is the only method to change this.
Okay I think I found the line your speaking of but this is what it shows:
<?php echo tribe_event_featured_image( $event_id, 'full', false ); ?>
Being the line of code differs from what you thought it was how should I proceed? I was going to change it to full so it always used the original image, but that’s already there. Could the “false” part throw things off? Also I don’t recall this file ever being edited.
Hello placidsolace,
It sounds like you are looking at:
the-events-calendar/views/single-event.php:55
Instead of :
the-events-calendar/views/list/single-event.php:74
It’s an easy mistake to make. They are both single-event.php files, but they server different purposes. In this case you want to go with the second one that Brian pointed you to.
Cheers!
– Brook
That does it! Thanks @brook for following up and guiding me appropriately. 😀