ifingers

@james Huff, I signed up about a week ago but have no reply yet.
Thanks!

You could have a look at the php and mysql versions, are they the same?

Also, compare the .htaccess file from a working domain to the broken one.

Have a look here for more solutions: https://codex.www.ads-software.com/Common_WordPress_Errors#The_White_Screen_of_Death

I would try uploading a copy of WordPress, everything except your wp-content folder and wp-config file from a working domain to the broken one. If that doesn’t fix it compare file permissions from a good domain to the broken one.

Hope this helps!

Will a static html file load ok?
Can you login to WordPress? Or are you seeing the WSOD everywhere?
You could try uploading a php info file to this problem subdomain and another working one, and compare them to see if you can spot a difference:
https://codex.www.ads-software.com/Finding_Server_Info

Do you have access to any error logs to help you point to the issue?

Are any of the other WordPress installs on subdomains also?

To be honest, in the long run you’re probably better moving to a new, more supportive host. ??

Is it just this sub-domain where you are getting the dreaded WSOD?

You could try contacting your host and see if they have any ideas.

pcvip, Sure, it’s your site. You can do what you like with it. You could even roll back to the previous version if that suited you better. WordPress is built by a community of hundreds of very smart people, who freely contribute their time and skills. I think 4.2 is the best release ever, but obviously your mileage will vary. Best of luck.

pcvip, the title attribute causes a real accessibility problem. In other words, it causes major issues for some people. If you want your website to be as inclusive as possible, I would embrace the changes. Seriously, in the long run this is a no-brainer. A win-win. A step forward in the right direction. Obviously you may disagree, I can understand your frustration but it’s the right thing to do.

SEO is all about people at the end of the day. The more people that like and can use your website, the better. I’m sure someone will write a plugin to reintroduce the title attribute, but that would be a big step back for accessibility and SEO imho.

That’s great Bernardneo, and well done to Andrew for spotting the typo!
Have fun with your site. ??

I see. I haven’t used that plugin before, but I get the gist of it and it’s made by some good WordPress folks.
Did you run this locally, then upload the files and database? If so, you can look at your local copy of wp-config, and see if this looks correct. If it looks garbled, I would start with a fresh clean copy of wp-config, and enter the correct remote values manually, then upload this.

I would check the other values too against your remote host. i.e. Database name, username, password. These all need setting properly.

Re-reading your original post, you said you used a plugin to update the wp-config file. Was this a WordPress plugin?

Yes, you will typically need to change these values in wp-config.php to match your host’s database:

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define( 'DB_NAME', 'database_name_here' );

/** MySQL database username */
define( 'DB_USER', 'username_here' );

/** MySQL database password */
define( 'DB_PASSWORD', 'password_here' );

/** MySQL hostname */
define( 'DB_HOST', 'localhost' );

These will be different from your local PC environment. It’s a good idea to make a backup of your local wp-config.php first. Obviously if you change this, it will break your working local setup.

Looks like the error might be pointing to an issue in your wp-config.php file. Have you updated this as per your remote hosts’ configuration?

This might help: https://codex.www.ads-software.com/Editing_wp-config.php

The code works for me.

However I am trying to add a Font Awesome icon to my submit button. I am entering code as below, but it is not working. To put it another way Is there another way of adding a class to the button?

[contact-form submit_button_text='<i class="icon-envelope"></i> Submit Now']

Well just in case this helps someone else…

I added conditional code in my header.php file like this:

<?php } else if ( 'my-custom-post-type' == get_post_type() && is_archive()) { ?>
<meta name="description" content="My wonderful SEO friendly description goes here..." />
<?php }

Not particularly elegant, but it works!

I am getting exactly the same error also.

PHP 5.4.4 MAMP setup.