Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 1,576 through 1,600 (of 1,763 total)
  • @jeffsayre

    Participant

    @Signaltrap-

    Tried to update via SiteAdmin Upgdare> Automatically Upgrade.

    Where you running a branch of WPMU 2.7.1 before upgrading?

    As I said above, if you were, then you cannot use the auto upgrade feature since WPMU 2.7.1 is the same as WPMU 2.7.1 The upgrade function cannot distinguish between -beta1 and the recently released public version of 2.7.1

    So, you must “upgrade” the old fashioned way.

    @jeffsayre

    Participant

    Were you running WPMU 2.7.1-beta1 before upgrading to the public version of 2.7.1?

    If so, did you try using the auto update feature? If you did, it will not work since the version is already 2.7.1.

    Instead, you have to do it the old fashion way: delete what is not needed, upload new files, then log in as site admin and got to Site Admin > Upgrade and finish the upgrade. Then, install BuddyPress, activate, and do the various theme directory changes.

    Also, are you using a brand new wp-config.php file–the one that comes with WPMU 2.7.1? Or, did you use an older version?

    If so, there is an additional define line added to WMPU’s config file as of 2.7.1:

    define(\'SITE_ID_CURRENT_SITE\', 1);

    @jeffsayre

    Participant

    Jfcarter-

    I’m sorry I did not get back to you last night. I was too tired and needed to go to sleep. Has this been resolved yet?

    @jeffsayre

    Participant

    bp-activity.php – bp_activity_install() Jeff.

    Thanks, Burt. I knew it was in there and that some activity table merging occurred in RC2, I just could not remember off the top of my head and I was dog tired to go look. I went to bed about 2 minutes after posting.

    @jeffsayre

    Participant

    BeLogical-

    I’m putting the finishing touches to the revisions to v1.2 of the Skeleton Component for plugin developers today. Since I first updated it, there are additional changes to make it sync up to RC2.

    When it is finished, I’ll post in this thread.

    @jeffsayre

    Participant

    Nightstalker101-

    Is this working for you now?

    Burt, I told you I was tired. I should not be posting when my head is fuzzy. :(

    @jeffsayre

    Participant

    Justme1-

    Okay a couple more questions:

    1. You say that your site is now up and running. Did adding that additional line to WPMU’s config file make that happen?
    2. When you upgraded to WPMU 2.7.1, did you log into the backend as site admin then go to the Site Admin > Upgrade and finish the upgrade?
    3. Are you using a custom theme?
    4. Did you move the themes into their proper location following these instructions?
    5. Do you have any plugins other than BuddyPress activated?

    The last question should not be a factor, but it helps to know your overall setup.

    @jeffsayre

    Participant

    Someone needs to confirm this, but I believe that the conversion from RC1 to RC2 eliminate some activity stream tables.

    Parts of this thread my answer your question, Jfcarter.

    @jeffsayre

    Participant

    @Justme1-

    If you do not have that line in your wp-config file, it means you used an older version. I just checked a new WPMU 2.7.1 download and the wp-config-sample.php file has this additional line in it.

    Anyway, this line goes in the section that starts with this comment:

    /** The Database Collate type. Don’t change this if in doubt. */

    As far as your last question, yes. You will have lots of issues using the BuddyPress themes until BuddyPress is successfully activated.

    In reply to: Empty Profile Page

    @jeffsayre

    Participant

    Okay, a few questions:

    1. Which versions of WPMU and BuddyPress are you running?
    2. You say that you were “beginning to alter the colors”. I assume you’re using the default BuddyPress themes and you only worked with the CSS files. Is that true? Or, did you make changes to some of the php files as well?
    3. Are you running this on localhost or a remote site?

    In reply to: Still no Avatar fix?

    @jeffsayre

    Participant

    Thanks for the info–and setting this thread to green!

    @jeffsayre

    Participant

    Chris-

    Let us know how it goes.

    @jeffsayre

    Participant

    Are you using a brand new wp-config.php file–the one that comes with WPMU 2.7.1? Or, did you use an older version?

    If so, there is an additional define line added to WMPU’s config file as of 2.7.1:

    define(\'SITE_ID_CURRENT_SITE\', 1);

    Also, before installing BuddyPress, but after upgrading WPMU to 2.7.1, did you got to Site Admin > Upgrade in site admin and finish the upgrade?

    @jeffsayre

    Participant

    Did you check permissions?

    @jeffsayre

    Participant

    I totally missed the templatetag part–sorry.

    Try bp_the_site_member()

    In reply to: Still no Avatar fix?

    @jeffsayre

    Participant

    @Erichamby-

    Wait!

    I’m glad it worked, but you need to do two things:

    1. Say what was the solution

    2. Turn on the green light –the topic is solved!

    Good luck with the other 235k things!

    @jeffsayre

    Participant

    bp_core_get_username() is used to fetch the username of a user based on their user id.

    @jeffsayre

    Participant

    Okay, at this stage I’d say it’s time to clean house.

    If this is a test dev install–meaning you do not have it in production mode–then I recommend deleting absolutely everything. This means the database file as well.

    Install a clean, new copy of WPMU 2.7.1 plus BuddyPress RC2 and see what happens. After WPMU is properly installed, then install BuddyPress RC2 using the plugin browser as described here: https://codex.buddypress.org/getting-started/installing-buddypress/

    Let us know how that goes.

    @jeffsayre

    Participant

    Maythil-

    I believe this issue has been resolved in the RC2 version of BuddyPress. If you have not yet upgraded, I’d recommend doing so. Read this thread: https://buddypress.org/forums/topic.php?id=2298

    @jeffsayre

    Participant

    Jfcarter-

    The upgrade process will remove a few BuddyPress tables that are not needed anymore in RC2. Don’t worry, though. All the important data is safe. So, as long as you have a recent backup of your DB, you’ll be fine.

    As far as shutting down your site during the upgrade, I usually make a post the day before stating that I’ll be performing upgrades. Since it is should take no more than 10 minutes, usually it is not an issue.

    But part of the upgrade process has been to delete everything except your wp-config file, various files in /wp-content/ (and of course your database), if someone attempts to go to the site during the upgrade, there may be no files to serve. So, with more established sites, I’ll stick an index.html file in root so that it will be served if someone comes while I’m upgrading. In that file, I have the logo and a “be back soon” or something like that message. This is overkill for most sites though.

    Finally, you could look at the Lock Outplugin. I’ve never used it and I do not know if it works with WPMU 2.7+.

    Good luck!

    In reply to: BuddyPress 1.0 RC-2

    @jeffsayre

    Participant

    Congratulations, Andy! This is another important milestone for BuddyPress!

    Thank you for your hard work, determination, and dedication in making the BuddyPress platform a wonderful tool for creating cutting-edge, vibrant social networks. I look forward to seeing where this goes!

    @jeffsayre

    Participant

    @Chris-

    Still thinking here, but a few more questions:

    Are you using the new wp-config.php file that comes with WPMU 2.7.1? Or, did you use and older version?

    If so, there is an additional define line added to WMPU’s config file:

    define('SITE_ID_CURRENT_SITE', 1);

    Also, before installing BuddyPress, but after upgrading WPMU to 2.7.1, did you got to Site Admin > Upgrade in site admin and finish the upgrade?

    @jeffsayre

    Participant

    JJJ-

    The party was great! But, it ended last night. ;)

    In reply to: Still no Avatar fix?

    @jeffsayre

    Participant

    Okay, so you’re site is running PHP5. I’m guessing that what is happening then is a PHP is running into a memory limit. So, we’re going to help PHP by boosting its memory limit.

    You’ll need to make a file called php.ini. Inside this new file, put this:

    memory=48MB

    Once you’ve created that file, upload it to your wp-admin directory.

    On some installs, I’ve had to boost the memory to 96MB. If 48MB does not work, try increasing.

    Let me know how that goes.

    In reply to: Still no Avatar fix?

    @jeffsayre

    Participant

    When uploading creating a group error 500 shows

    Okay, so your server is throwing an Error 500–Internal Server Error.

    A few more questions:

    • Which hosting company are you using?
    • Is your site running PHP 4 or PHP5?

    There are a few additional steps that can be taken–increasing the memory limit in php.ini and forcing Apache to run PHP 5, assuming that it is not.

    I’m actually going to get some sleep now. So, please reply and if someone else reads this before I do tomorrow, perhaps they’ll continue helping you.

    Good luck! I\’ll check back.

Viewing 25 replies - 1,576 through 1,600 (of 1,763 total)
Skip to toolbar