I am trying to:
Display a map and a marker based on a post field. When I embed shortcodes in Divi builder, the map and marker rendered properly, which means the shortcodes and the API key worked. Since Divi Builder inserts another div with an ID of "et-boc", I was getting duplicated ID within the HTML. So I had to disable Divi Builder and just write the HTML. When I insert the same map & marker shortcodes into HTML, the same shortcodes wouldn't render at all.
Link to a page where the issue can be seen:
See URL to dev site in access details, the page with the problem is:
/event/yxe-fireworks-test/
I expected to see:
Map & marker rendered
Instead, I got:
DIVs that take up space but completely blank inside.
Note:
The username and password to get past .htaccess are the same as the WordPress credential provided. Please look into this, this is quite urgent as my client wants to launch the site on Sep 30th.
Thank you
Hi Devin,
Thank you for contacting us and I’d be happy to assist.
During troubleshooting, I noticed a couple of script errors recorded in the browser’s error console.
( ref: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors )
A “custom.js” file ( hidden link ), seems to include a number of functions which are dependant on some other plugin or theme and are not available.
( e.g. “et_pb_init_nav_menu”, “et_pb_form_placeholders_init”, “et_duplicate_menu” etc )
In my localhost tests, removing these parts of the scripts fixes the script errors and the map starts loading correctly.
I hope this helps! Please let us know if you need any further assistance.
regards,
Waqar
Turned out that I have a plug-in called Divi Nitro which optimizes Divi's performance. One of the options I checked was to disable Divi scripts when DIvi Builder isn't used for the page. Sinec this particular page doesn't use Divi builder, DIvi scripts were disabled. I disabled this setting and Toolset Maps started rendering.
However, I don't get why or how that would've prevented Toolset Maps from rendering. Either way, it's working now, thank you.
