kungfunefar

Sorry, this is a bug on my side! The plugin works like charm!!!

Hi fabian,

thank you so much, this is F A N T A S T I C !!!

Best regards, Torben

Hi and thanks for the response!

Thank you barcelo for your assistance. You aksed the right thing at the end of your post:
How do I get/ display the values of fields which are nested inside a group field?

If I use the Insert field Button I only get access to the groups fields but not the nested fields. What is the correct syntax for displaying fields of a group?
Example:
An ACF Field Group, which is used as contact form, contents two fields of the field type group.
Address (Field Type: Group, Field name: address)

• Name (Field Type: Text)
• Street (Field Type: Text)
• City (Field Type: Text)

Additional Information (Field Type: Group, Field name: info)

• Contact Reason (Field Type: Select)
• Message (Field Type: Textarea)

So, how do I display the field street e.g. inside a notification?
{field:address->street}
or
{field:address[street]}

What is the right syntax?

Thanks and best regards!

This setting would really make sense, e.g. there could be a simple checkbox inside the accordion element which is labeled “Open first element on page load”. It is only a JS setting so this does not seem to be very difficult to implement.

In fact I had the same problem today, I created a workaround, which closes the first item again on document ready state with a tiny timeout. Code is Javascript:

jQuery(document).ready(function ()
{
  setTimeout(function () { jQuery('.elementor-widget-accordion .elementor-accordion-item:first-child .elementor-accordion-title').click(); }, 100);
});

Solution:
Apply the acf filter for including a custom google maps api key like this:
File: acf-google-map-extended-v5.php

function input_admin_enqueue_scripts() {
		$gm_api = apply_filters('acf/fields/google_map/api');
    wp_register_script("googlemaps-api", "//maps.googleapis.com/maps/api/js?key=".$gm_api['key']."&v=3&sensor=false&libraries=places",array(),'3',false);
    wp_register_script($this->settings['script-handle'], $this->settings['url'] . '/js/input.js', array($this->settings['acf-script-handle'],'jquery','googlemaps-api'), $this->settings['version'],false);
    wp_register_style($this->settings['script-handle'], $this->settings['url'] . '/css/input.css', array($this->settings['acf-script-handle']), $this->settings['version']);

    wp_enqueue_script(array($this->settings['script-handle']));
    wp_enqueue_style(array($this->settings['script-handle']));
  }

So now I found your plugin files where you enqueue you custom google maps script:
wp_enqueue_script(array($this->settings['script-handle']));

• acf-google-map-extended-v4.php, line 34
• acf-google-map-extended-v5.php, line 31

which you register before without GM API key:
wp_register_script("googlemaps-api", "//maps.googleapis.com/maps/api/js?v=3&sensor=false&libraries=places",array(),'3',false);

You have no filter for adding an API key but acf has, so why do you enqueue your own script? If I delete the line:
wp_enqueue_script(array($this->settings['script-handle']));
in both mentioned files, everything works fine.

Can you please change this behaviour, so that not everything crashes with the next update?

It seems that there are missing Gooogle Maps Api keys, because if I deactivate your plugin, browser console is empty but If your plugin is active, console logs:

maps.googleapis.com/maps-api-v3/api/js/26/16/intl/de_ALL/util.js:210 Google Maps API warning: NoApiKeys https://developers.google.com/maps/documentation/javascript/error-messages#no-api-keys
TA.j @ maps.googleapis.com/maps-api-v3/api/js/26/16/intl/de_ALL/util.js:210
maps.googleapis.com/maps-api-v3/api/js/26/16/intl/de_ALL/util.js:210 Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required

Now I am asking myself, why do you include your own google maps api scripts and not the once from the default acf google maps fields.? For acf I have added an API Code Like this:

function acf_init_gmaps_api_key() { acf_update_setting('google_api_key', 'AIzaSyAFpWUhAGXWIXnh-mBNCtfCCHPRxd8qCmA'); }
add_action('acf/init', 'acf_init_gmaps_api_key');

function my_acf_google_map_api( $api ) {	$api['key'] = 'AIzaSyAFpWUhAGXWIXnh-mBNCtfCCHPRxd8qCmA';	return $api; }
add_filter('acf/fields/google_map/api', 'my_acf_google_map_api');

That’s right. The default ACF Google Maps Field finds everything, as if you where searching directly on the google maps website.
If I change the field type to Google Maps Extended, almost nothing is found (Console logs: ACF Google Map Extended: Google Geocoder gescheitert : ZERO_RESULTS).
An Example: Search for Bradfield College

• This reply was modified 8 years, 3 months ago by kungfunefar.

I use a form that only consists of ac-fields and publish the form in the fronted by the function acf_form. In this case the recaptcha field appears without any problems so I think it has something to do with your configuration of the fronted form. Do you use the acf_form function?

OK I found the mistake:
Delete the empty lines 253 and 254 in acf-recaptcha-v5.php, so that there is no space or anything else left after the closing PHP tag ?> in line 252.

! ! ! P L E A S E H E L P ! ! !

Same error here:
Warning: Cannot modify header information - headers already sent by (output started at /wp-content/plugins/acf-recaptcha/acf-recaptcha-v5.php:254) in /wp-includes/pluggable.php on line 1228

The error appears in two situations and will leave the whole site blank white:

1. When saving the ACF Field group which contains a recaptcha field
2. When submitting an ACF fronted form

Please help !!!
Can you also tell me the difference of this plugin and the one created by Irvin Lim, which is called Advanced Custom Fields: reCAPTCHA Field.

Thanks in advance and best regards

@waffl: very good idea I think. Is there anyone who would host a consistent qtranslate version on githup?

This sounds really promising. I haven’t tried it out yet but i will as soon I have time. THANK YOU !!!

Although it is only a solution until the next WP update I think. The problem that qtranslate is not supportet consitently still exists ??

@getintothejam: Wouldn’t that be the same like using the development Version of qtranslate? I tried the dev version and it still caused errors. Or am I wrong?

I have donated [Donation details moderated – please take this discussion off the forums] via paypal. Who is next?