WPLake

Hi @interdixit

Thank you for taking the time to report this and for providing such clear context and screenshots — it’s incredibly helpful.

We’re currently working on recreating the issue based on your description, and if there’s a bug in the update, we’ll prioritise fixing it in an upcoming release.

We’ll keep you posted as soon as we have more information. In the meantime, staying on version 3.7.14 is a good call to maintain functionality.

Thanks again for your support and patience!

Best regards,
The WP Lake Team

Hi @tricheryltops

Thanks for the details! Since I’ve tested this on my end and the marker is displaying correctly, it seems like there might be something specific in your setup affecting the frontend rendering. Let’s try narrowing it down together.

Could you please share the following:

1. Theme details – Are you using a custom theme or child theme? Any custom JavaScript that might interact with maps?
2. View template output – Please share the full template used in the View (from the “Template” tab), especially if it’s been customised. You can copy/paste the code here or export it if needed as part of the debug dump.
3. Frontend errors – Open the page in Chrome, right click > Inspect > Console tab, and let me know if there are any errors or warnings showing. A screenshot or link would be great.
4. Google Maps API – Check the Network tab in your browser’s inspector while reloading the page. Make sure the Maps JS API is loading successfully (no permission or billing errors).
5. Map field data – On the frontend page, can you check if the map field’s data (like latitude and longitude) is actually output in the page source? Sometimes the marker won’t render if no data is being passed in.
6. Optional test – If you’re able to, try creating a blank page with just a basic map view (no styling or other plugins) and check if the marker shows up. This can help isolate the issue.

Once you send over those details, I’ll help you figure out exactly what’s going on.

Thanks!

HI @basudebbasu

If you’re using Elementor, shortcodes won’t work inside a standard Text Editor widget.

Please try using the ‘Shortcode’ widget instead, or add the shortcode inside an HTML widget. Let us know if you need further assistance!

Hi @genepine

Thank you for reporting the issue.
We’ve updated our plugin, and this error will no longer appear in the latest version of Advanced Views.

Hi @ismet1960

Thank you for your feedback! It sounds like there may be a conflict between Advanced Views and the caching plugin. We’d love to investigate this further to find a solution.

Could you let us know which caching plugin you’re using and if any specific settings (such as HTML minification, JavaScript optimization, or object caching) might be affecting it? If possible, checking for errors in the browser console or server logs would also help us pinpoint the issue.

We appreciate your time in reporting this and would love to work toward a fix. Looking forward to your response!

We’re closing this ticket as there’s been no reply.