Skip to:
Content
Pages
Categories
Search
Top
Bottom

Strange behaviour with registration after updating BP

  • Avatar of dharmen99
    dharmen99
    Participant

    @dharmen99

    After updating to BuddyPress 1.6.1 (BP is on a secondary site on a sub directory 2 site network), the WordPress ‘Register’ link redirects to the BuddyPress blog creation screen and not the registration page. I updated BP from 1.5.6. WordPress is 3.4.2.

    To try to find out what was happening, I installed two test sites on the server, both with virgin installs of WP and BP. I did not install any additional plugins so the sites are running standard basic installs. Both sites are running WP 3.4.2. On one site I installed BP 1.6.1 and the other BP 1.5.6. (Permalinks are set to Numeric).
    The following is in the wp-config.php file:
    define(‘WP_DEBUG’, true);
    define( ‘MULTISITE’, true );
    define( ‘SUBDOMAIN_INSTALL’, false );
    $base = ‘/test/’;
    define( ‘DOMAIN_CURRENT_SITE’, ‘sannyasnews.org’ );
    define( ‘PATH_CURRENT_SITE’, ‘/test/’ );
    define( ‘BP_ROOT_BLOG’, 2);
    define( ‘SITE_ID_CURRENT_SITE’, 1 );
    define( ‘BLOG_ID_CURRENT_SITE’, 1 );

    The result you can see from these links:
    http://sannyasnews.org/test/
    http://sannyasnews.org/test2/
    The first site (test) has BP 1.6.1, the second (test2) has BP 1.5.6 The sub directory were BP is active is called ‘now’ in both cases. If you follow the links above and then click ‘Register’ (under Meta) you will find that with the first site (test), the ‘Register’ link will redirect to http://sannyasnews.org/test/now/blogs/create/ whereas the second site (test2) will redirect to http://sannyasnews.org/test2/wp-signup.php.
    It is possible that there is a bug with WordPress but this only manifested when I installed BP 1.6.1. I believe the same thing happens with BP 1.5.7
    Any help greatly appreciated.

Viewing 1 replies (of 1 total)
  • Avatar of dharmen99
    dharmen99
    Participant

    @dharmen99

    I am wondering if there is anyone else running BP1.6.1 as a secondary site that is getting this problem. I need to know if this something I am doing or if its server related or if its a bug.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.