Need Testers: Activation Issue with BP v 1.2.5
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.
You must be logged in to reply to this topic.