Hi Rikard,

Thanks, but this won’t work. The slider caption needs it’s width changing to 100% and (potentially, depending on the amount of text in the caption) the top-margin reducing. For anyone else that wants a solution for both the iPhone X and Pixel 2XL in landscape mode, you can use the following media queries:

/* change fullscreen slider caption to fit on iphone X landscape */
@media only screen and (min-device-width : 375px) and (max-device-height : 812px) and (-webkit-device-pixel-ratio : 3) and (orientation : landscape)   { 
      .slideshow_caption {
      width: 100%!important;
      padding-top: 20px!important;
}
}

/* change fullscreen slider caption to fit on Pixel 2XL landscape */
@media only screen and (min-device-width : 412px) and (max-device-height : 823px) and (-webkit-device-pixel-ratio : 3.5) and (orientation : landscape)   { 
      .slideshow_caption {
      width: 100%!important;
      padding-top: 20px!important;
}
}

For anyone else looking to do the same, don’t contact a developer. I just installed this free plugin: Mappress. No conflicts found so far and runs alongside the Enfold built in Google map element with no apparent errors.

The free version of this plugin did everything I needed but you could also try the pro version of WP GoogleMaps. I very nearly bought it (only $19.99 for a 3 site license) and I’ve seen others on here who have used it OK with Enfold.

Hi guys,

Maybe you can help me now I’ve worked out where the other instances of maps.google.com, that affect the WP Store Locator plugin, are located:

file affected: wp-content/themes/enfold/framework/php/class-framework-widgets.php
function I commented out (line 1133 onwards):

function helper_print_google_maps_scripts()
        {
            $prefix  = is_ssl() ? "https" : "http";
            wp_register_script( 'avia-google-maps-api', $prefix.'://maps.google.com/maps/api/js?sensor=false', array('jquery'), '3', true);
            wp_enqueue_script( 'avia-google-maps-api' );

            $is_widget_edit_page = in_array(basename($_SERVER['PHP_SELF']), array('widgets.php'));
            if($is_widget_edit_page)
            {
	            wp_register_script( 'avia-google-maps-widget', AVIA_JS_URL.'conditional_load/avia_google_maps_widget.js', array( 'jquery','media-upload','media-views' ), '1.0.0', true);
	            wp_enqueue_script( 'avia-google-maps-widget' );

	            $args = array(
	                'toomanyrequests'	=> __("Too many requests at once, please refresh the page to complete geocoding",'avia_framework'),
	                'latitude'			=> __("Latitude and longitude for",'avia_framework'),
	                'notfound'			=> __("couldn't be found by Google, please add them manually",'avia_framework'),
	                'insertaddress' 	=> __("Please insert a valid address in the fields above",'avia_framework')
	            );

	            wp_localize_script( 'avia-google-maps-api', 'AviaMapTranslation', $args );
            }
        }

File affected: wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/google_maps.php
Function I commented out (line: 31 onwards):

function extra_assets()
			{
				if(is_admin())
				{
					$prefix  = is_ssl() ? "https" : "http";
            		wp_register_script( 'avia-google-maps-api', $prefix.'://maps.google.com/maps/api/js?sensor=false', array('jquery'), '3', true);
					wp_enqueue_script(  'avia-google-maps-api' );
					
					$args = array(
		                'toomanyrequests'	=> __("Too many requests at once, please wait a few seconds before requesting coordinates again",'avia_framework'),
		                'notfound'			=> __("Address couldn't be found by Google, please add it manually",'avia_framework'),
		                'insertaddress' 	=> __("Please insert a valid address in the fields above",'avia_framework')
		            );
	
		            wp_localize_script( 'avia-google-maps-api', 'avia_gmaps_L10n', $args );
					
				}
			}

After commented out these 2 functions the WP Store Locator plugin now works as it should, but obviously this is a temp fix as I will need to repeat the process after every update. Therefore, now you can see which functions are affected, would it be possible to provide me with some code I can add to my child theme’s functions.php? I know it’s a big ask (or not – not sure how easy it is for you guys!), but this would be a massive help if it’s not too much trouble for one of you php gurus?

Many thanks

Matt

Hi Ismael,

Thanks and I appreciate you can’t support 3rd party plugins, so I am grateful. However, I’ve just tested a clean install of Enfold with just this WP Store Locator plugin installed and I am still getting the Google Maps API warning. I’ve changed themes to twentyfourteen and it works fine with that, so it must be Enfold is using the Google Maps API somewhere, even though I haven’t put any google maps on the test site (clean install)??

I’ve set-up a temporary test site with only Enfold and WP Store Locator installed and have given a login to the plugin author, so hopefully he’ll try and find a fix – I reminded him how popular Enfold was and that it would be beneficial to have his theme working with such a top seller, so hopefully he’ll help!

However, if you did want to just test it yourself with Enfold and WP Store Locator, please feel free and let me know if you work anything out! Or if you can point out where the other instance of Google Maps API is being included?

Many thanks,

Matt

• This reply was modified 9 years, 5 months ago by meanster99.

Hi Devin,

I was hoping that your tagging of Kriesi would provide a definitive answer. If I’ve deleted my previously downloaded theme files, where will I find a copy of version 2.5.4 please?

Thanks,

Matt

OK, I can get the CALL US to work OK now with the following CSS:

#advanced_menu_toggle {line-height:14px;}
#advanced_menu_toggle:after { content: ‘CALL US’; font-size: 14px;}
#advanced_menu_toggle:before { display: none; }

But I would still prefer a phone icon please, if you can help?

Thanks,

Matt

• This reply was modified 9 years, 7 months ago by meanster99.

Hi Yigit,

Yes I’ve sort of figured it out thanks. It looks OK on my iphone now but it may appear quite a bit off centre on smaller tablets or very large phones (as the ‘left’ property is still set to 10%). It’s not perfect but at least it looks better than it did. Thanks for all your help.

Cheers,

Matt

Thanks Ismael, already using the latest update. It must be a either something local to me or the very specific circumstances I am using for the portfolio preview (which may be difficult to replicate, and so prove). As it’s just my problem I will have to put the   before and after punctuation marks. Thanks anyway…