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

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Duplicate Page titles #8355

    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
    djelusive
    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 Chris,

    Duplicate titles gone.

    Superior support, as always! 🙂

    in reply to: Grid Elements Builder error #5389

    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
    djelusive
    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,

    I too am receiving this same error.
    After upgrading to the latest version of the theme.

    The error appears in the bottom left of the admin dashboard after clicking on grid elements on the left pane.

    It appears to not be loading properly as the entire plugin fails to function for me.

    I have tried deleting it, re-downloading & re-installing it, only to get the same problem.

    in reply to: Visual Composer failing to load #4714

    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
    djelusive
    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,

    I found the problem. It was actually the proxy server I have been behind not allowing it to load.

    All good now.

    Thanks for your support.

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