Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 170

Home Forums Theme Support Fitness Google Maps Error

Topic Resolution: Resolved

Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #16929

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
    jverbosky
    Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 109

    The Google Maps feature in the Fitness theme (current version 1.4.1, just downloaded yesterday) isn’t working, confirmed on the demo site as well:

    1) Go here: https://www.skat.tf/redirect/?theme=fitness
    2) Select Features > Google Maps
    3) Confirm that maps aren’t working

    I worked around this for the time being (not using the Google Maps shortcode, using my own HTML for the map), but I’m seeing errors in the browser inspect console and don’t want to hack the theme to suppress the errors.

    FYI on the console errors that I’m seeing in Google Chrome (I replaced the API key listed):

    util.js:222 Google Maps JavaScript API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required
    $w.j @ util.js:222
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:163
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:67
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:64
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:67
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:140
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:67
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:140
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:67
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:140
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:67
    (anonymous) @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:140
    be @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:66
    Wd.wa @ js?key=***&callback=initMap&sensor=false&ver=4.9.8:140
    (anonymous) @ common.js:1
    js?key=***&callback=initMap&sensor=false&ver=4.9.8:42 Google Maps JavaScript API error: DeletedApiProjectMapError
    https://developers.google.com/maps/documentation/javascript/error-messages#deleted-api-project-map-error

    Thanks!

    John

    #16941

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
    skat
    Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 109

    Hi there,

    Google requires an API key now for their maps so you’ll need to create one and add it with the help of this plugin: https://wordpress.org/plugins/api-key-for-google-maps/

    Cheers!
    Chris

    #16957

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
    jverbosky
    Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 109

    Thanks for your reply, Chris!

    I did as you suggested, however this did not resolve the errors in the inspection console as the shortcodes plugin continues to reference the invalid API key.

    For the time being I’ve commented out lines 68 and 78 in sd-shortcodes.php (wp-content/plugins/sd-shortcodes/sd-shortcodes.php), but this should probably be updated in the next version of the theme if it isn’t already on your list.

    Thanks!

    John

    #16962

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
    skat
    Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 109

    That’s weird. Are you sure the notices were triggered by the theme files? Because I’ve checked it on my demo page and cannot replicated the problem.

    Cheers!

    #16969

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 657

    Warning: range(): Argument #1 ($start) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658

    Warning: range(): Argument #2 ($end) must be a single byte, subsequent bytes are ignored in /home/skattf/public_html/wp-content/plugins/buddypress-first-letter-avatar/buddypress-first-letter-avatar.php on line 658
    jverbosky
    Warning: Attempt to read property "supported_until" on string in /home/skattf/public_html/wp-content/themes/helpdesk/core/libraries/vendors/bbpress/init.php on line 109

    Hi Chris!

    OK, I determined the issue.

    Line 68 of the sd-shortcodes.php file (for the sd-shortcodes plugin, which comes with the Fitness theme) has the following (I masked the key here):
    wp_register_script(‘gmap’, ‘http://maps.google.com/maps/api/js?key=***************&callback=initMap&sensor=false’, array(‘jquery’));

    However the sd-shortcodes.php file from the 1.4.1 version of the Fitness theme has the following for line 68:
    wp_register_script(‘gmap’, ‘http://maps.google.com/maps/api/js?sensor=false’, array(‘jquery’));

    I didn’t update the sd-shortcodes plugin when I updated the theme, as it was listed as being version 1.0 in the 1.4.1 version of the Fitness theme (which is the same as what the site was already using).

    Honestly, since I recently inherited this site, it’s entirely possible that the original dev changed this line (no child theme was used, so it may have been one of many changes to the main theme files).

    Anyways, just wanted to let you know for completeness’ sake.

    Thanks again for your help!

    John

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.