Skip to:
Content
Pages
Categories
Search
Top
Bottom

Shoebombing BuddyPress hijacks root WordPress urls

  • Avatar of copywryter
    copywryter
    Member

    @copywryter

    Check out http://www.venture4change.com. All of the links (navigation, for example) are being hijacked by a BuddyPress installation in a /community directory. I can access the admin area of the root blog, and write posts, but clearly I need code that tells buddypress to stop being a naughty database terrorist.

    WP and BP technical details below. I’ve looked on the forums for an answer to this but it doesn’t seem to be a common issue.

    WP

    WP 2.9.1 in the root of http://www.venture4change.com, was functioning perfectly. Will update to 2.9.2 in next day or two.

    BP

    Version 1.2.3, fresh install, standard theme, no plugins, unmodified core files, no custom functions, bb-press built-in and running fine. No other issues. Tried moving away from standard theme — no difference.

    Hosted by myhosting.com, running on Linux.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Avatar of Andrea Rennick
    Andrea Rennick
    Participant

    @andrea_r

    BuddyPress works in a WordPress install – so in the /community/folder there has to be a WP install you’re posting from. It is not a stand-alone script.

    Look at the HTML source of the page, it says:

    <meta name="generator" content="WordPress 2.9.2" />

    When I go to your main install at the actual root, those menu items on the front of your site are off the root blog.

    You have another blog at /community/ as well as BuddyPress. Did you, perchance, install this using SimpleScripts?

    Avatar of copywryter
    copywryter
    Member

    @copywryter

    BuddyPress is running fine in http://www.venture4change.com/community, but I see what you mean….perhaps there are two installations? It’s possible…I used the host’s lousy wordpress installer, which was likely simplescripts.

    What’s your recommendation?

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

You must be logged in to reply to this topic.