Skip to:
Content
Pages
Categories
Search
Top
Bottom

PHP Fatal error RC2 -> RC3

  • Avatar of intimez
    intimez
    Participant

    @intimez

    PHP Fatal error: Call to undefined function bp_dtheme_show_on_frontpage() in /wp-content/plugins/buddypress/bp-themes/bp-default/home.php on line 9

    RC2 was fine. Just copied RC3 on top of it overwriting.

    [wordpress2.9.1 + 1.2-rc3]

Viewing 25 replies - 1 through 25 (of 25 total)
  • Avatar of Andy Peatling
    Andy Peatling
    Keymaster

    @apeatling

    If you’re using a child theme you’ll need to copy over the header.php again as it has changed. I’ve just searched, this function is not called anywhere in RC3, so make sure all the files were updated.

    Avatar of James Kirk
    James Kirk
    Participant

    @boldlygoing

    Hey,

    I just received similar:

    Fatal error: Call to undefined function bp_get_user_nav() in /home/public_html/3rdTribe.net/public/wp-content/themes/bp-default/members/single/home.php on line 15

    However, I’m just running the default theme, no children going on. Also, on WP 3.0a (running in network mode) if that makes any difference? TIA!

    Avatar of Brajesh Singh
    Brajesh Singh
    Participant

    @sbrajesh

    this has been changed

    replace

    bp_get_user_nav()

    with

    bp_get_displayed_user_nav()

    and everything will be working.

    Avatar of Brajesh Singh
    Brajesh Singh
    Participant

    @sbrajesh

    btw, anyone finding this problem may not have overridden their theme.

    Just overwrite older bp-default with the packaged bp-default theme and this issue will not be there.

    Avatar of James Kirk
    James Kirk
    Participant

    @boldlygoing

    Nice, Brajesh. Right you are. Just curious, how would I know or learn that sort of solution to something similar in the future? TIA

    Avatar of Brajesh Singh
    Brajesh Singh
    Participant

    @sbrajesh

    haha, keeping up with the trunk teaches you everything :)

    btw, the forum is always there, so I hope you will not have to worry about this in future :)

    Avatar of Andy Peatling
    Andy Peatling
    Keymaster

    @apeatling

    You should not be copying or moving bp-default from the BuddyPress folder, so technically this sort of thing should never happen.

    Avatar of intimez
    intimez
    Participant

    @intimez

    I was confused so I started over and configure up to my previous set up.

    Install wordpress2.9.1 (configure permalink)

    install buddypress12rc2 (select default theme – no other install or changes)

    then …

    install buddypress1.2.rc3 over buddypress12rc2.

    Produced the same error.

    Avatar of Andy Peatling
    Andy Peatling
    Keymaster

    @apeatling

    Don’t install rc2, just install rc3 and that’s it.

    Avatar of intimez
    intimez
    Participant

    @intimez

    So are you saying that for those that are upgrading from RC2 and getting the same error, we can simply delete the entire buddypress plugin folder and replace it?

    Avatar of geoffm33
    geoffm33
    Participant

    @geoffm33

    That’s what I have been doing. I have ssh access to my server so I just delete the directory, and do an svn export and reactivate the plugin.

    Avatar of intimez
    intimez
    Participant

    @intimez

    deleting the folder and using RC3 didn’t go too well. main page is all messed up. looked inside themes page and thumbnail is not showing.

    with all respect, I’m simply following the directions from Andy’s developer post which states, “If you are upgrading from an earlier pre-release version then you can just overwrite the BuddyPress plugin directory.”

    Avatar of m@rk
    m@rk
    Participant

    @mrk-1

    @intimez: the fatal error described in your very post here only occurs in case you haven’t set a specific start page like “Activity Stream” under -> Settings -> Reading !

    Setting Activity Stream as start page inhibits the fatal error. Strange?

    [WPMU 2.9.1.1 & BP 1.2 RC3]

    Avatar of danka
    danka
    Participant

    @danka

    Hi,

    I dont know why, but I am getting error 500, internal server error… what it means?

    I configured all as said on requirements…

    I am using WP 2.9.1 + PHP 5.2.3 + BP 1.2 RC3

    Avatar of danbpfr
    danbpfr
    Participant

    @chouf1

    How with your php memory limit ?

    Avatar of danka
    danka
    Participant

    @danka

    I dont have the lesser idea about the memory limit…but I think it is small, something like 8 or 16 Mb… How I can solve it?

    I tried buddypress also on this other configuration:

    WPmu 2.9.1.1 + PHP 5.2.3 + BP 1.2 RC3 b2715

    It gave me this error:

    Plugin could not be activated because it triggered a fatal error.

    Warning: require_once(/home/www/khron.com/wordpress-mu/wp-content/plugins/buddypress/bp-core.php) [function.require-once]: failed to open stream: No such file or directory in /home/www/khron.com/wordpress-mu/wp-content/plugins/budypress/bp-loader.php on line 19

    Avatar of danka
    danka
    Participant

    @danka

    Well,

    Forget about the last post, I just noticed that I forgot to put one extra “d” on the name of the folder…

    But, I done 2 tests with the last buddypress I got on SVN [BP 1.2 RC3 b2715], the first was in WP 2.9.1, the second in WPmu 2.9.1.1, both tests on the same server… both tests gave the same error [500, internal server error].

    About the memory limit, I still dont have idea about it, why the memory limit would be the problem? How much memory buddypress need to run?

    Avatar of danbpfr
    danbpfr
    Participant

    @chouf1

    No exact idea about how many memory is needed for BP, but for wp-mu it is in the wp-settings.php :

    line13: define(‘WP_MEMORY_LIMIT’, ’64M’);

    For WP single it is 32M…

    http://trac.mu.wordpress.org/browser/trunk/wp-settings.php

    To know the php memory_limit on your server, use:

    phpinfo();

    or

    http://wordpress.org/extend/plugins/wp-memory-usage/

    Avatar of danka
    danka
    Participant

    @danka

    Maybe is not the memory limit….

    I used the plugin and I got it:

    PHP Version : 5.2.6 / 32Bit OS

    Memory limit : 128 MByte

    Memory usage : 12.61 MByte

    I also noticed that I was wrong about the PHP version :-/

    There are any other possibility of thing to have problem with buddypress?

    Avatar of danbpfr
    danbpfr
    Participant

    @chouf1

    Did you retrieve the old theme folders ?

    bp-sn-parent and bp-default are no more in the theme folder, but in their own in buddypress

    Avatar of danka
    danka
    Participant

    @danka

    I done a clean install twice times with WPmu and more one with WP, with all the recommendations… and got the very same problem…

    the theme used is just the one available on the pack, not the old one… and I dont changed any thing on the pack…

    Avatar of Iva
    Iva
    Participant

    @supersonicsquirrel

    I am having the same problem as intimez and nothing helped. I am not using a child theme either, I did try some out in the past, didn’t like them because they were fluid.

    Would removing options related to those themes from the database solve anything and, if so, what should I remove.

    Avatar of danka
    danka
    Participant

    @danka

    Hi,

    I tried buddypress in another server, and it gave me a blank page… so, I think it is not problem on the server side, right?

    Avatar of danka
    danka
    Participant

    @danka

    Well,

    Thanks for ones that replied me!

    I just got the whole thing to work, but I am having another problem.

    So, I am starting a new post.

    Thanks.

    Avatar of designodyssey
    designodyssey
    Participant

    @designodyssey

    For those of us who made our WP theme compatible with BP before Andy’s plugin, this change in functions should be highlighted in the sticky thread http://buddypress.org/forums/topic/php-fatal-error-rc2-rc3#post-36596

    Probably need a global search and replace as another instance is in plugins.php line 15.

    Thanks Brajesh.

Viewing 25 replies - 1 through 25 (of 25 total)

You must be logged in to reply to this topic.