BuddyDev

Search

[Resolved] Recent Visitor Break / Error !!

  • Participant
    Level: Initiated
    Posts: 15
    enrons on #437

    Hi πŸ˜‰

    In last (2013) i bought the recent visitor plugin / version 1.1.3 .
    This plugin was very small and enough for me, but in new theme installation WP notice a error – rather breaks the website. I try to fix that, but i did not make quite.

    The Error:
    Fatal error: Call to undefined function bp_get_settings_slug() in … / recent-visitors.php on line 53

    I change this line, that the plugin and the website can run:

    —————– LINE 76 ————————-
    ### I change the line:
    $settings_link = trailingslashit( $user_domain . bp_get_settings_slug() );

    ### To
    $settings_link = trailingslashit( $user_domain . $this->slug );

    ————————————————————-

    Now the old plugin run, but i have other mini-error and mini-problems.

    ————– New Error —————————————

    Warning: call_user_func_array(): First argument is expected to be a valid callback, ‘BP_Visitor_Helper::setup_nav’ was given in …. wp-includes/plugin.php on line 503

    —————————————————————–

    Before i lost time, i thought to myself i buy the last version of the recent visitor plugin / version 1.2.8
    But the plugin completely brakes the site, i can not activate the plugin πŸ™

    —————- The Error in New Plugin ——————

    Fatal error: Call to undefined function bp_get_settings_slug() in … /recent-visitors-for-buddypress-profile/visitors-component.php on line 163

    ————————————-

    Can you fix that, please.
    The old version or the new plugin.

    Thank you!

    p.s.
    You know i have other problems, too. Perhaps the database or my installation is wrong? I donΒ΄t know.

  • Keymaster
    (BuddyDev Team)
    Posts: 21067
    Brajesh Singh on #438

    Hi Enrons,
    It seems you have settings component disabled for BuddyPress.
    I am sorry for the fatal error tough, we should have checked for the state of settings component. I will put an update in 30 -45 minutes to do that.

    Please do note that the recent Visitors plugin needs Settings component to be active otherwise a User won’t be able to update his/her preference.

    PS: It is originating from your other problem where you are not able to update the settings. The Settings component can be enabled from that page.

    Thank you
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 21067
    Brajesh Singh on #440

    Hi Enrons,
    I have updated the plugin. Version 1.2.6 will not throw any fatal error.

    Please do note that I have changed the directory name of the plugin from bp-profile-visibility to bp-profile-visibility-manager

    That name change was required to allow us provide you automatic upgrades in future via BuddyDev dashboard plugin.

    Please upgrade and do let me know how it went.

    Thank you
    Brajesh

  • Keymaster
    (BuddyDev Team)
    Posts: 21067
    Brajesh Singh on #442

    Here is the link to plugin for your convenience.
    https://buddydev.com/plugins/bp-profile-visibility-manager/

  • Participant
    Level: Initiated
    Posts: 15
    enrons on #444

    Ah ok .. ,
    i understand .. πŸ˜‰

  • Keymaster
    (BuddyDev Team)
    Posts: 21067
    Brajesh Singh on #458

    Hi Sebastian,
    I am Sorry, I updated the wrong plugin.

    here is the update to recent visitor plugin
    https://buddydev.com/plugins/recent-visitors-for-buddypress-profile/

    Thank you
    Brajesh

  • Participant
    Level: Initiated
    Posts: 15
    enrons on #473

    Sorry.. !!

    IΒ΄m very angry of me ..

    This was not your fault .. ! ,
    the wp-theme is fault ..

    I should have to know that.
    I know, why i building my own theme, even if it costs a lot of time .. πŸ˜‰

    Thanks for your fast help πŸ˜‰ πŸ˜‰

  • Keymaster
    (BuddyDev Team)
    Posts: 21067
    Brajesh Singh on #474

    Hi Sebastian,
    No problem. It happens with all of us. That’s why it is called learning πŸ™‚

    All the best with your site. Closing this topic as resolved.

    Thank you
    Brajesh

You must be logged in to reply to this topic.

This topic is: resolved