Title: Parse error, Warning, Fatal Error&#8230;
Last modified: August 18, 2016

---

# Parse error, Warning, Fatal Error…

 *  [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * (@thatguyjeff)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/)
 * I’m a total rookie at this. First time attempting to install and I don’t know
   code at all either. aka dangerous layperson here…
    I have checked and rechecked
   ad nauseum my db username and password stuff.
 * On running the install file (v 1.5) I get this:
 * Parse error: parse error in /web/script/thatguyjeff/familiverse.com/wordpress/
   wp-config.php on line 4
 * Warning: main(ABSPATH/wp-admin/admin-functions.php): failed to open stream: No
   such file or directory in /web/script/thatguyjeff/familiverse.com/wordpress/wp-
   admin/upgrade-functions.php on line 3
 * Fatal error: main(): Failed opening required ‘ABSPATH/wp-admin/admin-functions.
   php’ (include_path=’.:/usr/share/pear’) in /web/script/thatguyjeff/familiverse.
   com/wordpress/wp-admin/upgrade-functions.php on line 3
 * Thoughts?

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

 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164562)
 * Did everything upload as one huge number of files, or as 4 folders and a couple
   of dozen files ?
 *  Thread Starter [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * (@thatguyjeff)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164564)
 * One huge file. Perhaps I should try uploading as 4 folders and change.
 *  [Mark (podz)](https://wordpress.org/support/users/podz/)
 * (@podz)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164565)
 * When you unzip, there should be an option to preserve file/folder structure –
   this needs doing else you will get these error.
 *  Thread Starter [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * (@thatguyjeff)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164569)
 * I don’t think that’s it. The file structure is good, I just had the four folders
   and change inside another folder. Same error still…
 * What else you got for me?
 *  [ColdForged](https://wordpress.org/support/users/coldforged/)
 * (@coldforged)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164571)
 * The parse error is a little disconcerting, too, and seems indicative of an error
   in syntax for when you were trying to put in your database parameters in wp-config.
   php. That’s the file that contains the definition of ABSPATH, so if you’ve borked
   that file you’ll get errors when you try to use ABSPATH.
 *  Thread Starter [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * (@thatguyjeff)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164591)
 * I’m pretty sure I haven’t borked it. And I’ve tried editing it a few times, from
   scratch using the original sample file each time. Tried clearing the spaces between
   the ; and my username… The spaces don’t matter anyway, do they? I haven’t touched
   anything else in the file ‘cept the password and db name. I’m using a text editor,
   not Word or other word processor.
 * Here’s the config file as I have it, ‘cept I put **** where my password goes.
   See anything fishy?
 * <?php
    // ** MySQL settings ** // define(‘DB_NAME’, ‘wordpress’); thatguyjeff_db
   define(‘DB_USER’, ‘username’); thatguyjeff define(‘DB_PASSWORD’, ‘password’);******
   define(‘DB_HOST’, ‘localhost’); // 99% chance you won’t need to change this value
 * // Change the prefix if you want to have multiple blogs in a single database.
   
   $table_prefix = ‘wp_’; // example: ‘wp_’ or ‘b2’ or ‘mylogin_’
 * // Change this to localize WordPress. A corresponding MO file for the
    // chosen
   language must be installed to wp-includes/languages. // For example, install 
   de.mo to wp-includes/languages and set WPLANG to ‘de’ // to enable German language
   support. define (‘WPLANG’, ”);
 * /* Stop editing */
 * define(‘ABSPATH’, dirname(__FILE__).’/’);
    require_once(ABSPATH.’wp-settings.
   php’); ?>
 *  [ColdForged](https://wordpress.org/support/users/coldforged/)
 * (@coldforged)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164593)
 * Yes. You need to replace the text in singlequotes with what your database setup
   is. Like so:
 * <?php
    // ** MySQL settings ** // define(‘DB_NAME’, ‘thatguyjeff_db’); define(‘
   DB_USER’, ‘thatguyjeff’); define(‘DB_PASSWORD’, ‘******’);
 *  Thread Starter [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * (@thatguyjeff)
 * [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164594)
 * OMG!
 * me = biggest dork ever
 * Thanks for the assist!

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

The topic ‘Parse error, Warning, Fatal Error…’ is closed to new replies.

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 8 replies
 * 3 participants
 * Last reply from: [thatguyjeff](https://wordpress.org/support/users/thatguyjeff/)
 * Last activity: [21 years, 2 months ago](https://wordpress.org/support/topic/parse-error-warning-fatal-error/#post-164594)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
