{"id":2355,"date":"2026-10-20T08:32:18","date_gmt":"2026-10-20T07:32:18","guid":{"rendered":"https:\/\/wpgeodirectory.com\/documentation\/article\/images-or-maps-not-showing-with-divi\/"},"modified":"2026-10-20T08:40:20","modified_gmt":"2026-10-20T07:40:20","slug":"images-or-maps-not-showing-with-divi","status":"publish","type":"gd_place","link":"https:\/\/wpgeodirectory.com\/documentation\/article\/troubleshooting\/images-or-maps-not-showing-with-divi\/","title":{"rendered":"GeoDirectory images or maps not showing with Divi"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">GeoDirectory works with the Divi theme and builder, and you do not need one of our themes to use it. When listing images stay blank or the map keeps loading with Divi, a JavaScript error on the page is the usual cause, and it often comes from a second copy of jQuery added by a child theme or plugin.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why the images go blank<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">GeoDirectory lazy loads listing images. The page first loads a tiny placeholder image (its src starts with <code>data:image\/png;base64<\/code>) and keeps the real address in <code>data-src<\/code>. Our JavaScript then swaps the real image in. If another script throws an error first, that swap never happens. Maps rely on JavaScript the same way, so they stop at the loading stage.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to check<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the page, press F12 and look at the Console tab for red errors. Errors such as &#8220;is not a function&#8221; that mention jQuery point to a script conflict.<\/li>\n\n\n\n<li>View the page source and search for jquery. WordPress already loads its own copy. If your child theme or a plugin loads another jquery.min.js, remove that line (usually a <code>wp_enqueue_script<\/code> call in the child theme&#8217;s functions.php).<\/li>\n\n\n\n<li>Clear your caching or minify plugin&#8217;s cache, and exclude GeoDirectory scripts from JavaScript combining or deferring if the problem returns. See <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/caching\/geodirectory-and-caching-compatibility\/\">GeoDirectory and Caching Compatibility<\/a>.<\/li>\n\n\n\n<li>Check your Google Maps API key, or switch to OpenStreetMap, if the console shows a Google Maps error rather than a script conflict.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If the error comes from a script you cannot remove, try ticking Disable Scripts On Call at GeoDirectory > Settings > General > Developer. That setting is meant for pages where GeoDirectory&#8217;s on demand script loading clashes with other JavaScript.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Building GeoDirectory pages in Divi<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">You can design the GeoDirectory templates (details, archive and search pages) with the Divi Builder using our blocks and shortcodes. The content of each listing itself is entered through the listing form, not the Divi Builder. <a href=\"https:\/\/wpgeodirectory.com\/documentation\/article\/builders\/getting-started-with-divi-builder\/\">Getting started with Divi builder<\/a> covers the setup.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>GeoDirectory works with the Divi theme and builder, and you do not need one of our themes to use it. When listing images stay blank or the map keeps loading with Divi, a JavaScript error on the page is the usual cause, and it often comes from a second copy of jQuery added by a [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"article\/tags":[],"article\/categories":[211,437],"class_list":["post-2355","gd_place","type-gd_place","status-publish","hentry","gd_placecategory-tips-tricks-more","gd_placecategory-troubleshooting"],"_links":{"self":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/types\/gd_place"}],"author":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/comments?post=2355"}],"version-history":[{"count":1,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2355\/revisions"}],"predecessor-version":[{"id":2416,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/2355\/revisions\/2416"}],"wp:attachment":[{"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/media?parent=2355"}],"wp:term":[{"taxonomy":"gd_place_tags","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/tags?post=2355"},{"taxonomy":"gd_placecategory","embeddable":true,"href":"https:\/\/wpgeodirectory.com\/documentation\/wp-json\/wp\/v2\/article\/categories?post=2355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}