After doing everything all over again, I still have problem with database connection with my site frameda. fi. Can not log into wp-admin either. Site is showing something but not correct content. What I have done is:
1. exported my local wordpress database in localhost/phpmyadmin as a sql.gzip file.
2. uploaded wordpress files to live site using FTP client. htdocs -> public_html directory.
3. created a MySQL database on live site cPanel and created a user, added it to the database and given all privileges
4. imported wordpress database on live site using cPanel/phpMyAdmin – imported the gzipped file that was created earlier.
5. changed the site url in phpMyAdmin wp_options: options_name and home to be the live site url address (http://www…)
6. changed the database name, user and password in wp_config.php file and uploaded it back to server (not changing db host, as it is localhost. should it be changed to url and if yes, in what format?)
Any idea what to do?
Nothing there, so I guess you will need to upload your site again first 🙂
Any suggestions what I might be doing wrong, as I have uploaded wordpress files and imported database as explained above…all that can be seen on the site is the logo and menu.
Not sure. I see you have a WordPress installation at http://frameda.fi/htdocs/ but it’s not working correctly, cause it should be installed at http://frameda.fi/wordpress/. That’s why I am asking you to upload again to show exactly the error.
I have uploaded wordpress files again, directly on public_html, you can see there now is an Internal server error message. And the error log writes as follows:
[23-Sep-2014 19:04:50 UTC] PHP Warning: require(/home/frameda/public_html/wp-includes/load.php) [function.require]: failed to open stream: No such file or directory in /home/frameda/public_html/wp-settings.php on line 21
[23-Sep-2014 19:04:50 UTC] PHP Fatal error: require() [function.require]: Failed opening required ‘/home/frameda/public_html/wp-includes/load.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/frameda/public_html/wp-settings.php on line 21
Thanks!!
Have you reviewd if that file exists in your server?
It is part of the WP core files…
Remember that you need to check file wp-includes/load.php, not wp-settings.php. Is that load.php file existing?
Yes, I have load.php in wp-includes file.
@jonkukoo: the error is for the file settings.php. You need to make sure that file exists. Have you check that?
Yes, I have wp-settings.php file as well.
How about the permission and owner of load.php file? Any setting in .htaccess?
Changed the permissions and uploaded the file load.php again.
In -htaccess I have as follows:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>
# END WordPress
All folder permissions are 755 and file permissions are 644.
I have checked that the reason is not broken plugins by changing the name of the folder. It did not help.
Any other ideas?
Okay, it may be a corrupted .htaccess file:
The first thing you should do when troubleshooting the internal server error in WordPress is check for the corrupted .htaccess file. You can do so by renaming your main .htaccess file to something like .htaccess_old. To rename the .htaccess file, you will need to login to your site using the FTP. Once you are in, the .htaccess file will be located in the same directory where you will see folders like wp-content, wp-admin, and wp-includes.
Once you have renamed the .htaccess file, try loading your site to see if this solved the problem. If it did, then give yourself a pat on the back because you fixed the internal server error. Before you move on with other things, make sure that you go to Settings » Permalinks and click the save button. This will generate a new .htaccess file for you with proper rewrite rules to ensure that your post pages do not return a 404.
If checking for the corrupt .htaccess file solution did not work for you, let me know.
Actually tried this one too. Changed the name of .htaccess using FTP client and it did not help…returned it back to it´s original name.
