Skip to:
Content
Pages
Categories
Search
Top
Bottom

Need Testers: Activation Issue with BP v 1.2.5

  • @jeffsayre

    Participant

    14 years, 5 months ago

    I’ve been working with the latest BP builds of the 1.2.5 branch over the past several days. I noticed a new issue with the just-released BP 1.2.5 tagged version that I had not seen with the previous 8 or 9 branch versions that I’ve tested. After deactivating all BP-dependent plugins and then BP itself, downloading and manually installing BuddyPress 1.2.5, I went to activate BP. It activated but did not show up in the “Currently Active Site Wide Plugins” listing. I thought that was odd.

    So, I deactivated and tried again. Same issue. I deactivated again, this time clicking the “Activate BuddyPress Site Wide” link which worked as expected. The issue is that BuddyPress is tagged to auto activate site wide–as should all 3rd-party BP plugins. This is accomplished by means of a simple tag in the header of bp-loader.php file. Look for the “Site Wide Only: true” tag.

    When I activated my BP-dependent plugins, they all activated site wide without issue, appearing in the “Currently Active Site Wide Plugins” listing. But, the only way to get BP to appear in that listing is to manually click the “Activate BuddyPress Site Wide” link — which should not be necessary. Just for kicks, I’ve tried several combinations of edits to the header tag in bp-loader.php, including deleting the “Site Wide Only: true” tag and leaving the “Network: true” tag and visa versa. Both these tags should be there, but I wanted to see what would happen. Results: no change in behavior.

    This is happening on my WP 2.9.2 dev site as well as WP 3.0.

    So, the questions are:

    1. Do others see this behavior? If so, what version of WP are you running?
    2. What is causing this issue?

    Please report any site wide activation issues.

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

  • @johnjamesjacoby

    Keymaster

    14 years, 5 months ago

    Can’t duplicate it myself, but let’s get some feedback.

    @johnjamesjacoby

    Keymaster

    14 years, 5 months ago

    Just upgraded two sites, one a subdirectory, the other a subdomain, two separate hosts and environments, neither of which showed this issue. Phew!

    Again, doesn’t mean it doesn’t exist, but so far I really can’t duplicate it.

    @davidtcarson

    Participant

    14 years, 5 months ago

    Works for me using WP 3.0 on a local install.

    Updated to BP 1.2.5 automatically, clicked the activate button after upgrade, and it was activated across the network.

    @jeffsayre

    Participant

    14 years, 5 months ago

    Very strange. I’m going to delete my dev sites, reinstall WP and BP, reboot and see what happens. I’ve already cleared out caches, cookies, and rebooted several times. Perhaps I shouldn’t be using my Commodore PET to run my dev sites. I’m also going to try on my other two MacBook Pros.

    @hnla

    Participant

    14 years, 5 months ago

    Don’t quite get this? I have no ‘activate’ or rather it is grayed out and it would be running in multi site mode (WP 3.0)? or should that be in either mode ?does it flip flop the links? – the only option I have is to ‘network activate’ and that works as expected, although there is no separate section for the network activated plugins.

    You may find things run better on a Sinclair ZX spectrum? In all seriousness it’s probably about time you upgraded to a BBC MIcro

    @lightcapturer

    Participant

    14 years, 5 months ago

    I just activate Buddypress 1.2.5 on Wodrdpress 3.0 Multisite without any problems. Can viewed on http://teronggosong.com.

    @jeffsayre

    Participant

    14 years, 5 months ago

    @hnla: I should have been more clear. With WP3.0, the “Activate” link for BuddyPress is replaced with “Network Only”. To activate BuddyPress, you have to click the “Network Activate” link.

    I have tracked down this issue. It is specific to WP 2.9.2 only. I thought I was seeing it in both WP 2.9.2 and WP 3.0. But, after reinstalling everything, I can only reproduce it in WP 2.9.2.

    Would someone please confirm this on a WP 2.9.2 install. I suppose it could be a quirk in my dev setup, but this issue did not exist with the four or five 1.2.5 branch versions that I tested yesterday.

    If others can replicate this issue, then the “Requires at least” tag in BP’s readme.txt file should be changed to WP 3.0. Otherwise, we will have people activating BP for a single blog, and not site wide–that is if they just click the “Activate” link in WP 2.9.2.

    Do we need to updated the information for plugin devs? Should they include the “Network: true” tag in the header of whatever file they consider their loader file?

    @jeffsayre

    Participant

    14 years, 5 months ago

    Has anyone with a WP2.9.2 tested this out yet? I would like to have confirmation that it is isolated to WP 2.9.2 — maybe just isolated to my dev site!

    NOTE: see my above post for more details.

    @jeffsayre

    Participant

    14 years, 5 months ago

    Giving this a bump.

    Would someone with a WP 2.9.2 install please test this potential BP 1.2.5 activation issue as described in this thread and report back here?

    @seagrinch

    Participant

    14 years, 5 months ago

    Hi Jeff, I have the same issue. And it now explains why all the bp template tags were not working in my sub blog themes. I didn’t notice that Buddypress was not activating site-wide, but clicking the activate site-wide link fixes this.

    @jeffsayre

    Participant

    14 years, 5 months ago

    @ seagrinch –

    Thanks for the report. This confirms my suspicions. BuddyPress v1.2.5 has an activation issue under WP 2.9.2. So, as I stated above, the “Requires at least” tag in BP’s readme.txt file should be changed to WP 3.0. Otherwise, we will have people activating BP for a single blog, and not site wide–that is if they just click the “Activate” link in WP 2.9.2.

    The other option is to give users of WP 2.9.2 clear, explicit instructions that they have to click the “Activate BuddyPress Site Wide” link instead of the “Activate” link. However, this will not guarantee that most users will actually see these instructions.

    @hnla

    Participant

    14 years, 5 months ago

    Upgraded my remaining 2.9.2 to BP 1.2.5 to run a test for you (bit late as it appears now :) )

    I confirm above ‘Activate’ is not site wide, results in sub blogs sans BP , setting ‘Site Wide’ activation results in expected behavior.

    @jeffsayre

    Participant

    14 years, 5 months ago

    @hnla –

    Thanks for the testing and confirmation. I have created a ticket for this issue.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Need Testers: Activation Issue with BP v 1.2.5’ is closed to new replies.

Topic Info

Skip to toolbar