reneekelly

Okay, I uninstalled MAMP & then reinstalled it & viola – it connected & I was on the setup page on wordpress.

It was wanting to have the database info to create wp-config.php. Since I had already done wp-config.php manually I was confused.

I went back & realized this time I did not change the file name from wp-config-sample. When I went back & renamed the file to wp-config.php, I again received the error message. When I named it back to wp-config-sample I again was connected.

Resolution:
The file need to be named wp-config-sample for it to connect to localhost:8888/wordpress for installation. (Perhaps the new versions of the software – not sure which one since they are both new have simplified something in the set up.) Most instructions on the internet are recommending the manual setup before conencting to localhost:8888/wordpress. It appears that in the new versions this is what was causing the error.

I just wanting to say thank you CureWP for you detailed assistance. Also thanks to officialsabbir.

It is soooo very cool that you were willing to take time out to assist me! Happy New Year to you both!! ??

Everything else checks out, even the $table_prefix.

Server connection collation: utf8mb4_unicode_ci

so changed my configs to:
DB_CHARSET reads:
/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8mb4_unicode_ci’);

still blank page – (& if I reset back to the original ‘utf8’[just want to see] I am still seeing a blank screen – no longer seeing the error message)
Have left settings to read – define(‘DB_CHARSET’, ‘utf8mb4_unicode_ci’); as that is exactly what is stated on Sever connection collation on phpmyAdmin.

Should I now attempt to reinstall MAMP?

Okay,

I did have a discrepancy on one of the lines:
I changed:
/** Database Charset to use in creating database tables. */
define(‘DB_CHARSET’, ‘utf8’);

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

I am no longer getting the error message – but just a blank screen.

Okay, I’m following your instructions (officialsabbir)

In my configs: (cutting & pasting here)
define(‘DB_NAME’, ‘wordpress44’);

/** 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’, ”);

I am still getting the error message whether I use:
localhost:8888/wordpress
or change the port setting & use:
localhost/wordpress/

Regarding lastest post (Artur Bobinski):
I have closed down MAMP completely and ran it again, I have rebooted my computer, but will do that again now & report back. (Should I consider trashing both MAMP & wordpress 4.4 & starting over with the downloads?)
How do I restart both apache and mysql?

Hi there, I appreciate your time.
I’m sorry I didn’t include that in the previous post.

Database: wordpress44
User – root
Host – localhost
Type – global
Privileges – all privileges
Grant – yes

The correct database, user & host are in my configs.
However, where do I go to double-check the password (in phpMyAdmin)?

I forgot to add that I am working on a Mac – Os X Yosemite v. 10.10

Re: localhost:
I attempted that before & tried again with your suggestion & still the same message.

When I go open MAMP, go to phpMyAdmin (under tools) & click on the created database (wordpress44) under Privileges it shows
user – root
host – localhost

When I click on status it reports:
Network traffic since startup: 279.4 KiB

This MySQL server has been running for 4 days, 13 hours, 59 minutes and 27 seconds. It started up on Dec 25, 2015 at 03:24 AM.
Traffic ? per hour
Received 75.9 KiB 706 B
Sent 203.5 KiB 1.9 KiB
Total 279.4 KiB 2.5 KiB
Connections ? per hour %
max. concurrent connections 1 — —
Failed attempts 43 0.39 45.26%
Aborted 0 0 0%
Total 95 863.71 m 100.00%

I also cut & pasted define(‘DB_PASSWORD’, ‘’); adding root as password that was also suggested & still the same message.