bplank

Nah, you can’t delete the admin name… I tried that initially. I moved all the posts to a new user name with admin priv, but WP didn’t allow the delete. I resolved it though… the tutorials need to be updated for new PHPAdmin versions.

Sounds like your host’s admin page or your host account was hacked… because you can’t create an SQL database from WP… only from your host account. I’d recommend you alert your host and then change your admin password.

THere were 2 WP hacking types: the SQL post injection/redirect and the password hackers. NEITHER created new databases, they only uploaded files and php redirectors, which is why I believe what I posted above.

BTW, who is your host?

You are victim to SQL injection. You need to export your posts as an XML file, then delete the SQL database and to a completely new install. Then you need to install WP 2.6.1. The SQL injection issue was 2.5 specific, but not in 2.6+

– take the index.php file that’s in the folder where you installed WordPress and save it to your desktop.
– Open the file with notepad and change the following:

From this:

require(‘./wp-blog-header.php’);

To this:

require(‘./site/wp-blog-header.php’);

‘site’ will be the name of the folder that you installed WordPress in.

– Upload that file (after you saved it) to the root directory of your site, in this case it’s ‘robpannell.com’

Voila! The php file will pull the site from the installation folder.

wait… does ‘db.stanthonysf.org’ house a SQL database? That’s supposed to be where the SQL db is. So I guess the question is, who is your hosting through, Speakeasy? Most hosts only need to you set that to localhost OR, like I had to with my previous host, it was msql.HOSTNAME.com.

Yea, you should upload the zip/rar files directly into that folder and THEN uncompress them if you’re not sure. most plug ins that have addl content need the folder as a ‘source’ to work from… so if you dump everything into the ‘plugins’ folder, WP won’t recognize them.

I fixed it. I did a clean install and found that ‘ezstatic’ was still in my exported xml file. EzStatic plug doesn’t work with 2.6, so I removed it (wasn’t using it anymore anyway) a while ago. I removed all of the meta data in the xml file with ‘ezstatic’ and then I was able to delete (finally!) the custom fields in new pages and new posts.

… yea, that didn’t do anything.

FWIW, I have Angsuman’s Permanent Redirect https://blog.taragana.com/ installed, as I did with all my previous WP installations. It’s updated to the newest version and when I deactivate the plug in, the issue remains… it actually remains if I deactivate ALL plug ins, so I simply don’t know what’s causing this issue. It’s ONLY on this one of 5 WP installations that I have this problem.

Those are old redirects that I had in my old installation, so I know they’re valid.

The only thing I can think of is something with the XML importing… maybe if I export it, scour out all the redirects and reference to a redirect, that might do it..?

……?

It’s a file that controls actions for the WordPress installation. It updates the data in your SQL database every day or every hour, depending on how it’s set up.

Try the WP-Crontrol plug-in. https://www.ditii.com/2008/01/08/wp-crontrol-wordpress-plugin/

Or WP-Cron plug-in: https://skippy.net/plugin-wp-cron

Either one can allow you to slow the amount of updates/queries to your SQL server and should aleviate the problem. Tell your host that you’re attempting to resolve the matter, so they know you’re trying to fix it.

2.5 was reponsible for the plague of SQL injection hackers. 2.6 does not have that vulnerability and 2.6.1 has the fix for the permalink issue in 2.6.

anyone?

It appears as if your ‘post’ title was altered.

The coding is presently this:

<h2 id="post-5"><a href="https://incommunion.org/articles/-2/quotations" rel="bookmark">-image-Quotations</a></h2>

Check the ‘Permalinks’ section in the Admin page, under ‘Settings’. I noticed there are permalinks issues with my 2.6 install too… so I had to revert to the ‘Default’ setting, which is https://DOMAIN NAME.com/?p=123

Give that a try.

Yea, the links will be lost, but for me, that’s not a big deal. I’m more concerned with the content, than with the links.

As I’m reading, though, 2.5 has some vulnerabilities with post injection, which is the culprit for the TONS and TONS of redirect spam lately. If your host isn’t running ModSecurity and you’re running 2.5, you could be a target of a hacker/spammer.