bplank

Keep it simple, people…

On the admin page where you selected your “front page” select another (existing) Page as your “posts page”. Done.

.
wow… why didn’t someone tell me about that before?

Well, FWIW, you can still use the c&p of the ‘index.php’ file that I posted above. Both ways are effective.

1. Copy the ‘index.php’ file over to the main directory.
2. Edit the file to show the following:

<?php
define('WP_USE_THEMES', true);
require('./FOLDER-WHERE-YOU-WISH-TO-LOAD-THE-SITE-FROM/wp-blog-header.php');
?>

The wordpress site will load when visitors type in the base-level domain address.

Change your permalinks to:
Default https://domainname.com/wordpress/?p=123

The issue will go away.

Change your permalinks to:
Default https://domainname.com/wordpress/?p=123

The issue will go away.

Change your permalinks to:
Default https://domainname.com/wordpress/?p=123

The issue will go away.

I contacted my host and had them remove the ‘POST_PAYLOAD’ from the ModSecurity settings.

yup… this is all you need in the index.php file:

<?php
define('WP_USE_THEMES', true);
require('./FOLDER-WHERE-YOU-WISH-TO-LOAD-THE-SITE-FROM/wp-blog-header.php');
?>

k… I added the .htaccess file (with the suggested text) to the wp-admin folder and the root install folder, but the issue and same error remain.

I have the same issue.

You need to update the wp-config file with the data that was in your previous file. I tried your link and the error is because the php file can’t ‘call up’ the SQL database, because the information in the wp-config file isn’t correct (or blank).

FIRST OFF… if you’re going to upgrade, you should ALWAYS export as an xml file.

But on all of my WP sites, I had to do a clean install, so removed all files (except my wp-content folder) and dropped all tables in my database. Once I did that, I could get 2.6 to install properly.

IMO, stick with 2.5 if you have it… or even 2.4. There’s too much crap to deal with in 2.6.

Google is the source for that block. If you have resolved your vulnerabilities and removed the files the hacker added, then visit this link to request removal: https://www.google.com/webmasters/tools/

OK… so I had to do a CLEAN install and the issue subsided.

So far, 2.6 SUCKS!!

Why do I receive a 500 error when a post size is more than 10 lines of text?

I came across the same issue when I upgraded to 2.6. I had to do a clean install and dump all of my SQL tables to finally get the damn thing to work right (yes, I exported and then imported all of my content).

I had the same problem when I upgraded to 2.6

Here’s what I did (it sucks, but it worked):

1. I exported my entire blog as an xml file.
2. Go into MyPhPAdmin (or whatever you use to work on your SQL databases) and ‘DROP’ all the tables in the database you use for that particular blog.
3. INSTALL (not upgrade) the blog, but if you’ve moded any themes, DO NOT INSTALL THE WP-CONTENT FOLDER!!.
4. Once you log into the ‘admin’ page, click on ‘Manage’, then ‘Import’, then WordPress.
5. Select the xml file you exported and click ‘Upload file and import’

Your site should look like it did before ??