Skip to:
Content
Pages
Categories
Search
Top
Bottom

"Page not found" due to empty current_component after 1.2.1 upgrade


  • Boone Gorges
    Keymaster

    @boonebgorges

    14 years, 9 months ago

    WPMU 2.9.1.1. Was running BP 1.2RC-1, and updated to BP 1.2.1 this morning. Haven’t set up my server properly to allow automatic upgrade from Dashboard, so I deleted all the files in plugins/buddypress and replaced them with the updated plugin files. Running no other BP related plugins.

    Now when I try to load any directory page (/activity, /groups/, /blogs etc) but the main page, I get “Page not found”, within the bp-default template. That is, it’s not a white 404 page, but is styled as a BP page. Trying to visit a action page (/members/admin for instance) redirects me to the home page of the entire install.

    I did a var dump of $bp and saw that $bp->current_component and $bp->current_action are empty. So something is happening incorrectly in the initialization of BP. I’m about to troubleshoot, but I thought I’d ask here first in case anyone can see from this description what dumb thing I’ve done wrong.

    Thanks!

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

  • Boone Gorges
    Keymaster

    @boonebgorges

    14 years, 9 months ago

    OK, found the problem. I’m running BP on a blog other than blog_id=1. Apparently I had made the change to BP_ROOT_BLOG in a core file (not sure why). So when the new files were loaded, and bp-core-catchuri.php tried to parse the URL, it was getting hung up on the fact that the current blog was not (so it thought) the BP blog.

    I set the constant in a plugin, where it belongs, and everything is hunky dory now.


    Windhamdavid
    Participant

    @windhamdavid

    14 years, 9 months ago

    try ../wp-admin/admin.php?page=bp-component-setup and save the settings again? it’s right on ‘takeoff’ ~ bp-core-catchuri.php #20 ~ bp_core_set_uri_globals() $current_component ~ all the urls depend on it and it looks like it fails if the root_blog is not the current_blog ID? sitewide activation? Not running BP on the root? I don’t know.. do you have a any other unique configuration going on?


    Windhamdavid
    Participant

    @windhamdavid

    14 years, 9 months ago

    nvrmnd… i see you got it, didn’t refresh my browser… but I have you know.. I was investigating :)


    Boone Gorges
    Keymaster

    @boonebgorges

    14 years, 9 months ago

    Duly noted, David :) thanks for your help – and it looks like you found the problem in exactly the same way that I did!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘"Page not found" due to empty current_component after 1.2.1 upgrade’ is closed to new replies.

Topic Info

Skip to toolbar