Featured Listing Shortcode Error for Individual Listings

Hey there, thank you for the detailed report on this! Just wanted to post a quick update that we do a have patch for this coming shortly, you should see a plugin update available today or tomorrow with a fix for the issue. I’ll leave this open for now and let you know once that’s available.

Thanks again.
Cody

Thank you!

I did test with the most recent version release (v. 3.0.2) and the links are working correctly now!

One additional issue though… some of the listings in the slider are not pulling the featured image – it shows blank for a couple of listings even though it is shown in the main listing shortcode.

Examples found here (refreshing a few times): https://www.searchlightproperties.com/dev-rets-test/

See also: https://gyazo.com/a475b00a2c26b98f48e784f992b01b3a

Let me know if you need any further information.

Thanks!

Hey @nickiova — thanks for the the update with v3.0.2! Glad that fixed the the link issue for you.

The first time I click the link, everything works, and then subsequent reloads show what you’re seeing. Fortunately I know what this is and it is not actually related to this plugin and is easy to fix:

The issue happens when there is a lazyloading conflict on the site. The listing slider already lazy loads itself, but some other plugin (or sometimes a theme) has a lazy load setting that is causing an conflict trying to load the image.

See if you can figure out which plugin is doing the lazy loading. Most caching, optimization, performance, etc, related plugins may have this functionality.

Once you know who is causing the conflict, there _should_ be a setting to bypass certain images by class name (.sr-listing-slider-item-img) or URL (https://media.crmls.org/). This is the easiest solution. For example with Smush, Elementor, W3 Total Cache, etc, all have this setting with the option to bypass I mentioned.

I’ll go ahead and close this since it’s not related to this specific bug, but feel free to reach out via email or open another thread if needed!

Cody

Thank you! Yes, the Lazy Loading was causing the issue and we were able to get that fixed.

Thank you again for your responsiveness and support!