FYI – Events Manager uses a lot of output buffering functions. Here’s why that’s a bad idea in the context of a WordPress site: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1422
./admin/em-docs.php: ob_start();
./admin/em-options.php: ob_start();
./classes/em-booking.php: ob_start();
./classes/em-booking.php: ob_start();
./classes/em-booking.php: ob_start();
./classes/em-calendar.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event.php: ob_start();
./classes/em-event-post.php: ob_start();
./classes/em-events.php: ob_start();
./classes/em-location.php: ob_start();
./classes/em-location-post.php: ob_start();
./classes/em-person.php: ob_start();
./classes/em-taxonomy-frontend.php: ob_start();
./classes/em-ticket-booking.php: ob_start();
./classes/em-ticket.php: ob_start();
./templates/placeholders/bookingbutton.php: ob_start();
./em-actions.php: ob_start();
./em-actions.php: ob_start();
./em-actions.php: ob_start();
./em-actions.php: ob_start();
./em-actions.php: ob_start();
./em-events.php: ob_start();
./em-functions.php: ob_start();
./em-shortcode.php: ob_start();
./em-shortcode.php: ob_start();
./em-shortcode.php: ob_start();
./em-shortcode.php: ob_start();
./em-shortcode.php: ob_start();
./em-shortcode.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./em-template-tags.php: ob_start();
./events-manager.php: ob_start();
./events-manager.php: ob_start();
js.
Hi Andy 😉
Another EM User here.
That “search and replace” probably means the EM Placeholders. 😉
Reading the WPSSO reply, the thing that comes to my mind, is that you are using a #_EVENTIMAGE{x,x} placeholder. And with the Pinterest button, you are basically processing a processed image…
Getting the exact right images is always a “happy” challenge within WP, but when resizing by/with EM even more. Over the past few years I found that a lot of plugins do not cope well with the by EM resized images.
“JetPack”: Enabling their CDN results in completely different (wrong) dimensions.
“Network Shared Featured Image”: will only load the full version and only scale it width css absolute width and relative height styling (still loading the full sized image).
What I personally did, was add the “scaled EM image” sizes with add_image_size() to my functions.php (I use 85×85 for example). Then using Regenerate Thumbnails plugin, I (re)created the files (only needed for previously uploaded files). That way, EM doesn’t really resize anymore; WP recognizes there is properly scaled file in your upload folder.
That way you should “bypass” the EM scaling, but it is also better for your actual page load, since a smaller image is loaded. 🙂
Hope it helps.
