Skip to:
Content
Pages
Categories
Search
Top
Bottom

Cant Get Buddy Press to Run Locally


  • ryan_dolan
    Participant

    @ryan_dolan

    Hi everyone, looking for some advice and guidance
    I am new to buddypress and before I design the ui for a site I have in mind that will use buddypress i wanted to just install it and see what its like. Good thing i did because I cant get it to work.
    I am running Mamp Pro and the latest version of both WP and BP. I have tried manual installs as well as through the plugins installer. The only time I got it to work was with the default BP theme, but then I couldnt edit anything via wp-admin. Does this make sense? When I would try to go to my dashboard i would get server errors. I saw some posts about changing the memory size in wp config etc but nothing is working. Any help or advice would be great. Thank you!

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

  • 9087877
    Inactive

    Try xampp instead and make sure the info in the wp-config.php is correct:
    http://www.apachefriends.org/en/xampp.html


    ryan_dolan
    Participant

    @ryan_dolan

    What difference do you think that will make?


    9087877
    Inactive

    Well I use xampp and I can assist you better if we are using the same software. I can tell you for certain that something is wrong in your wp-config.php thats causing these errors between buddypress and mysql database.
    Edit:
    Regardless of what software your using I would take a look at your wp-config.php and try to work it out from there.


    ryan_dolan
    Participant

    @ryan_dolan

    Heres my WP-Config file

    <?php
    /**
    * The base configurations of the WordPress.
    *
    * This file has the following configurations: MySQL settings, Table Prefix,
    * Secret Keys, WordPress Language, and ABSPATH. You can find more information
    * by visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
    * wp-config.php} Codex page. You can get the MySQL settings from your web host.
    *
    * This file is used by the wp-config.php creation script during the
    * installation. You don’t have to use the web site, you can just copy this file
    * to “wp-config.php” and fill in the values.
    *
    * @package WordPress
    */

    // ** MySQL settings – You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define(‘DB_NAME’, ‘ryanpaddlesite’);

    /** MySQL database username */
    define(‘DB_USER’, ‘root’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘password’);

    /** MySQL hostname */
    define(‘DB_HOST’, ‘localhost’);

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);

    define(‘WP_ALLOW_MULTISITE’, true);

    define(‘WP_MEMORY_LIMIT’, ’512M’);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the { @link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    *
    * @since 2.6.0
    */
    define(‘AUTH_KEY’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
    define(‘NONCE_KEY’, ‘put your unique phrase here’);
    define(‘AUTH_SALT’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_SALT’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_SALT’, ‘put your unique phrase here’);
    define(‘NONCE_SALT’, ‘put your unique phrase here’);

    /**#@-*/

    /**
    * WordPress Database Table prefix.
    *
    * You can have multiple installations in one database if you give each a unique
    * prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘wp_’;

    /**
    * WordPress Localized Language, defaults to English.
    *
    * Change this to localize WordPress. A corresponding MO file for the chosen
    * language must be installed to wp-content/languages. For example, install
    * de_DE.mo to wp-content/languages and set WPLANG to ‘de_DE’ to enable German
    * language support.
    */
    define(‘WPLANG’, ”);

    /**
    * For developers: WordPress debugging mode.
    *
    * Change this to true to enable the display of notices during development.
    * It is strongly recommended that plugin and theme developers use WP_DEBUG
    * in their development environments.
    */
    define(‘WP_DEBUG’, false);

    /* That’s all, stop editing! Happy blogging. */

    /** Absolute path to the WordPress directory. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);


    9087877
    Inactive

    In your wp-config.php change:
    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘password’);
    to:
    /** MySQL database password */
    define(‘DB_PASSWORD’, ‘’);


    ryan_dolan
    Participant

    @ryan_dolan

    so there will be no password? i did that and now I have an error establishing a database connection


    9087877
    Inactive

    Then check the other fields. Here is a copy of one of my local sites wp-config.php:
    <?php
    /**
    * The base configurations of the WordPress.
    *
    * This file has the following configurations: MySQL settings, Table Prefix,
    * Secret Keys, WordPress Language, and ABSPATH. You can find more information
    * by visiting { @link https://codex.wordpress.org/Editing_wp-config.php Editing
    * wp-config.php} Codex page. You can get the MySQL settings from your web host.
    *
    * This file is used by the wp-config.php creation script during the
    * installation. You don’t have to use the web site, you can just copy this file
    * to “wp-config.php” and fill in the values.
    *
    * @package WordPress
    */

    // ** MySQL settings – You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define(‘DB_NAME’, ‘bpdev’);

    /** MySQL database username */
    define(‘DB_USER’, ‘root’);

    /** MySQL database password */
    define(‘DB_PASSWORD’, ”);

    /** MySQL hostname */
    define(‘DB_HOST’, ‘localhost’);

    /** Database Charset to use in creating database tables. */
    define(‘DB_CHARSET’, ‘utf8’);

    /** The Database Collate type. Don’t change this if in doubt. */
    define(‘DB_COLLATE’, ”);

    /**#@+
    * Authentication Unique Keys and Salts.
    *
    * Change these to different unique phrases!
    * You can generate these using the { @link https://api.wordpress.org/secret-key/1.1/salt/ WordPress.org secret-key service}
    * You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.
    *
    * @since 2.6.0
    */
    define(‘AUTH_KEY’, ‘gKR[~e-<4 |Jj1DVfT-RM.m(|=M7(OB;tp/bfQt9+9[+FcIK<Gdp[(*u~2@-_H*J');
    define(‘SECURE_AUTH_KEY’, ‘_$y7AKT$.Zz`XHS3 DxndhyLGd/3ITTfE3oJqphSGS:x1*TH@45D 6NIjU7y64om’);
    define(‘LOGGED_IN_KEY’, ‘i6[pr$z#c,0E&EI]j]:K}cG9N`J[:JsL]wgy%[coeV>h(<c#W%Ye');
    define(‘NONCE_KEY’, ‘@GH9@ITlC&Py&cG3O5sKaVrm;vqP/4mKYz#=n>K?`%:C.q56yFO4WEaY:g^Rs+>+’);
    define(‘AUTH_SALT’, ‘QulXiJdP`zXXz*D*]RbfXfH[$C6 Z;:n>pLwcrSZvkY!7|*mHxyS>#n^qqiD2noO’);
    define(‘SECURE_AUTH_SALT’, ‘3/{(F|iduMA;QfF%OPY:jHTH:D8jcmWB&h`gfs$K4L&uTVhg1.05nz~h.COtvf+7’);
    define(‘LOGGED_IN_SALT’, ‘YG?P2/ <+A,W8L:r<0^9~n1c<aO-w|OTl~.o^T39ZPp)tz7&V~[x57X&n,(*(iA0');
    define(‘NONCE_SALT’, ‘|G0,AO(>,Ak @y a/A;Kf3it9W~Lv[/q*?,Pe!Dqf~WDzKzD?JJQ+V%.:]icGtzq/’);

    /**#@-*/

    /**
    * WordPress Database Table prefix.
    *
    * You can have multiple installations in one database if you give each a unique
    * prefix. Only numbers, letters, and underscores please!
    */
    $table_prefix = ‘wp_’;

    /**
    * WordPress Localized Language, defaults to English.
    *
    * Change this to localize WordPress. A corresponding MO file for the chosen
    * language must be installed to wp-content/languages. For example, install
    * de_DE.mo to wp-content/languages and set WPLANG to ‘de_DE’ to enable German
    * language support.
    */
    define(‘WPLANG’, ”);

    /**
    * For developers: WordPress debugging mode.
    *
    * Change this to true to enable the display of notices during development.
    * It is strongly recommended that plugin and theme developers use WP_DEBUG
    * in their development environments.
    */
    define(‘WP_DEBUG’, false);

    /* That’s all, stop editing! Happy blogging. */

    /** Absolute path to the WordPress directory. */
    if ( !defined(‘ABSPATH’) )
    define(‘ABSPATH’, dirname(__FILE__) . ‘/’);

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);


    ryan_dolan
    Participant

    @ryan_dolan

    hmm all looks the same. I am gonna try xammp and tell you what happens

    Works fine in local environments. I personally use MAMP. You didn’t say what the error that you’re getting was?


    ryan_dolan
    Participant

    @ryan_dolan

    So as soon as I install the default them for BP, I cant do anything to edit. If i click on the dashboard I get a server error


    ryan_dolan
    Participant

    @ryan_dolan

    The website encountered an error while retrieving http://mysite/wp-admin/. It may be down for maintenance or configured incorrectly.
    Here are some suggestions:
    Reload this webpage later.
    HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.


    modemlooper
    Moderator

    @modemlooper

    Use regular mamp not the pro. Can’t remember exactly but I had similar issues


    ryan_dolan
    Participant

    @ryan_dolan

    Very weird, it works with Mamp like you said but not Mamp Pro

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Cant Get Buddy Press to Run Locally’ is closed to new replies.
Skip to toolbar