Skip to:
Content
Pages
Categories
Search
Top
Bottom

Upgrade to 1.03 – forced to install WPmu 2.8.4a?

  • @catinw12

    Participant

    Currently using Buddypress 1.0.2 and WPmu 2.7.1

    I started the to process to upgrade to Buddypress 1.0.3, following Andy’s exact process. After disabling all of the plugins, I began to look for WPmu 2.8.3 to install manually (since the auto upgrade indicated it would charge me up with 2.8.4a straightaway), and could not find the older version. I found one link in the WPmu site that said ‘previous versions’ but when I clicked on it, all it presented was 2.8.4a.

    So I stopped the conversion process. All indications on the forum are that the 2.8.4a is not fully compatible with Buddypress 1.0.3

    I realize there is already a similar topic on here about compatibility but the main thrust of this topic is finding the 2.8.3 install.

    Thanks and I hope everyone is having a great August (or a mild one for those down under).

    Brian

Viewing 5 replies - 1 through 5 (of 5 total)
  • @djpaul

    Keymaster

    Bp 1.0.3 needs wpmu 2.8 onwards. I have no issues with 2.8.4a on my site.

    @jeffsayre

    Participant

    The auto upgrader is not working in WPMU 2.8.2. Here is a fix: http://ocaoimh.ie/wordpress-mu-2-8-3/

    @djpaul

    Keymaster

    Ah, *that*. :p

    @catinw12

    Participant

    decided to make the plunge and do the automated update to 2.8.4a

    encountered several fatal errors along the way but deactivating the plugins and then activating by “activate” instead of “activate site wide” seemed to do the trick. That and logging out as the admin and logging back in resolved most stuff.

    Having to redo my .htaccess file that was coded to provided direct external SSO from aMember. Way beyond my ability so I await help from aMember.

    Had to dive back into the bp-core to remodify all the changes. From a user perspective as opposed to a developer, following the instructions of the moderators on here is very difficult and since most of you are doing this for free, I am loathe to complain for any help you provide. I mention this because there is a certain level of knowledge in coding that is necessary before many of us can follow the instructions of Burt and other brillianto’s. Unfortunately, we don’t have that knowledge so the quick and dirty for us users who are trying to make buddypress operational is to simply cut and paste code in the core, write down in a researcher’s notepad akin to a research scientist titrating drops of transylvanian serum into Frankenstein’s bloodstream.

    @jeffsayre

    Participant

    @catinw12

    From which version of WPMU were you upgrading? If from 2.8.2 or older, did you see my post above?

    Had to dive back into the bp-core to remodify all the changes…I mention this because there is a certain level of knowledge in coding that is necessary before many of us can follow the instructions of Burt and other brillianto’s. Unfortunately, we don’t have that knowledge so the quick and dirty for us users who are trying to make buddypress operational is to simply cut and paste code in the core, write down in a researcher’s notepad akin to a research scientist titrating drops of transylvanian serum into Frankenstein’s bloodstream.

    AHHHH! Stop!

    Of course you’ve had all the issues you mentioned above!. You are traipsing around in the codebase, modifying core files like there’s no tomorrow. Even if you are a “brillianto” programmer, you do not touch core files unless you are helping patch bugs or providing new functionality to the overall project.

    Why? Because whenever you upgrade, ever single core hack you’ve made will be erased. What are your options? Either install other’s plugins that provide the functionality you’re after, write your own plugins, or place your code changes in the bp-custom.php file. But, never, never, never change the core code. If you do, you will have the issue you’ve mentioned above.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Upgrade to 1.03 – forced to install WPmu 2.8.4a?’ is closed to new replies.
Skip to toolbar