• Hi guys,
    im trying to install wordpress on a subdomain (the main domain isnt wp, and has it’s own website, as it was built by some company.) i have access to the ftp server for the subdomain, a dedicated db for it, and i have configured the wp-config file.but everytime i try to run sub.domain.com/wp-admin/install.php I get reverted to the main site. If i just type in sub.domain.com I get html page that just says this is a placeholder for sub.domain.com.

    Any ideas on how to get the install to run?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Why are you configuring wp-config file in advance? Just upload WP installation to the dedicated subdomain folder (or use Softaculous or what have you in your cPanel) and then install as usual.

    Thread Starter paddydrum

    (@paddydrum)

    @sinip
    good question but the reason is that it doesn’t run this way and so as per wordpress instructions i set up the config

    Ah well… Hard to tell without seeing your wp-config file. I did few installs on subdomains on my hosting and always completed it the usual way. But then again I have no idea which host you use and how it is configured. maybe someone who faced the same issue will be able to shed more light?

    Thread Starter paddydrum

    (@paddydrum)

    Here is my wp-config file (I changed the names and password from the real for obvious reasons_

    <?php
    /**
    * The base configuration for WordPress
    *
    * The wp-config.php creation script uses this file during the
    * installation. You don’t have to use the web site, you can
    * copy this file to “wp-config.php” and fill in the values.
    *
    * This file contains the following configurations:
    *
    * * MySQL settings
    * * Secret keys
    * * Database table prefix
    * * ABSPATH
    *
    * @link https://codex.wordpress.org/Editing_wp-config.php
    *
    * @package WordPress
    */

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

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

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

    /** 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’, ‘3H`a[~,)vk>->OT.+qTrM02rFog}~/9e^h^!23WSA]T#r~_41RB#r$t,~zPu%]RF’);
    define(‘SECURE_AUTH_KEY’, ‘K)+uJVTd*2Y,k6r^-:5MBmT#w&I0phuJ&mCuy#_d%D>__=0(#ZJnZWFpsw%{|]H$’);
    define(‘LOGGED_IN_KEY’, ‘&C?cX$R<N[SOQBV+)rmuDq#CTlU:(Z{y<nP6h4;Kuk?T+l>+{u2%Li)M;oYDDRLW’);
    define(‘NONCE_KEY’, ‘.wsxOSN(! q(3rBFguGE@Z86!%CqX/syA=]5INW5|T~|?w-:D<-~[`VQDSiYPm7d’);
    define(‘AUTH_SALT’, ‘O[uoX,.)Jr-,+^||^G&m7v;<o}hM-U`(y-H|JU^!%sI!K!9r;|%N%_K!__Q|[1B@’);
    define(‘SECURE_AUTH_SALT’, ‘)c}CT^J-J|D$N_kj0<K|1:{Ans~Vf1k0+a,jliAg>nX{|zs=R~-Gk[EwJC@0n4s’);
    define(‘LOGGED_IN_SALT’, ‘L+!Q54AZXn,o}!Q[v@-TX,v0Lf-G>o@-R*[E5U. %@R3eZ!mZ0n9%b?X_Pui~[B+’);
    define(‘NONCE_SALT’, ‘+it96Na9vvp6Ig-DFFJ>i+#+0e$<v2Y6L0&/9jDZFMPm:F W&. sIXu5VV~B1l(h’);

    /**#@-*/

    /**
    * 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_’;

    /**
    * 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.
    *
    * For information on other constants that can be used for debugging,
    * visit the Codex.
    *
    * @link https://codex.wordpress.org/Debugging_in_WordPress
    */
    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’);

    Hi, I ran into the same problem – i was about to launch new install and decided to use the most recent and the instalation failed. and I didn’t edit the config file, just after that and with this debug result:

    [07-Mar-2017 18:22:26 UTC] PHP Fatal error: Class ‘Requests_Hooks’ not found in /hosting/www_delta/wp-includes/class-wp-http-requests-hooks.php on line 17

    older instalation pack run smoothly.

    Thread Starter paddydrum

    (@paddydrum)

    @chikory do you know what version you used?

    sure, it was 4.7.3, BUT – I solved my problem and it was not related to wp. The problem was wrong upload setting, one very basic error, that I didn’t look there at first, because i would never set it that way purposely. I didn’t noticed that ftp client was changing all letters to lowercase, and it’s so elementary error, that I feel very dumb now.
    the older package was already copied on the server, so it was okey.

    jacksonmartinez9449

    (@jacksonmartinez9449)

    Wordpress version 4.7.3 has pretty much bugs it’s my opinion

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Unable to run install.php’ is closed to new replies.