wp – q292u

Byq292u

Clogs, Database Web, Delete, Gig, Plesk, Reason, Spamming, Sql Delete, Two Solutions, wp

WordPress Database – Delete Orphaned Posts

Delete Orphaned Posts

After manually using SQL to delete users, you can be left with (potentially a lot) of posts which now belong to users who simply don’t exist. You don’t want this, it wastes space and clogs things up.
There are two solutions to this:

Delete the Orphaned Posts
Assign them to another user.

I’m going to use option1, as I deleted those users for a reason – Spamming!

From PLESK or CPANEL database web admin:

Delete Orphaned Posts

DELETE
FROM `wp_posts`
WHERE post_author NOT
IN (
SELECT id
FROM wp_users
);

NONE of my tables have a wp_ prefix!

Now DELETE ORPHANED POSTMETA..

** BACKUP YOUR DATABASE FIRST!

Please note: You should NEVER leave your tables with the default “wp_” prefix. Or have a user called “admin”, or a user with id=1. That’s just for start!
Let us secure your WordPress site for you:
http://www.q292u.com/services/secure-your-wordpress-site-our-new-fiverr-gig

Byq292u

Better WordPress Security

As it stands, WordPress Security is OK.
It’s certainly a LOT better than the security I had on my home-brew php/mysql website before I got into WordPress. (that site was hacked, which is WHY I got into wp).
BUT. And it’s a big BUT, it could easily be better.
A standard WP install has certain vulnerabilities a hacker can exploit:

No user/hostname lockout or blacklisting
Admin user called “Admin”, with ID of “1”.
All database tables prefixed “wp_”
Version Info displayed to everyone

All of these security holes can be used by a hacker to gain access and/or modify your content.

One of my sites was recently taken offline by my hosting company because their security software detected a password hacking attempt. Mega-Kudos for that! – WordPress would have let them get on with it!

So I’ve been installing a plugin called “Better WP Security” on my higher-risk sites.
It’s already detected (and banned) a Russian hacker (in St Petersburg) attempting a password hack. I’ve also rolled his hostname out to my other sites as a precaution.

None of my sites now have an “admin” account, an account with an ID of “1”, or a database table with a “wp_” prefix. I’ve implemented blacklisting (using a known list of bad hosts and user agents), so known bad people don’t even get a look-in.. and a host of other security measures including automatic timeouts between failed attempts, and permanent (automatic) hostname banning.

The more obstacles you can put in their way, the more chance the hackers will move on to easier targets elsewhere..

I recommend “Better WP Security” – and it’s free!

Byq292u

Blogs, Educational Establishment, Gomez Gomez, htaccess file, Maturity, Occurrences, Proxy, Server Name, Sql Queries, Urls, Wordpress Multisite, wp

WordPress Multisite Problems

We’re currently working on a Multisite WordPress Installation for an educational establishment. The problem is that the server is accessed via a proxy on their main domain.
Their technical people advised us to set up the wp install using the server name. We’ll call it “Gomez”. Gomez isn’t accessible from the internet, so it’s accessed via www.domain.ac.uk/proxyname. That’s fine, except that it only works internally. 🙁
Also, it switches all the URLs back to Gomez once you are through the proxy. 🙁
Using a “requestheader host” statement in the htaccess file throws a WP error – it thinks there’s a port number in the URL!
You wouldn’t believe how difficult it is to change the URLs within a WP Multisite install!
We have to use sql queries to replace all occurrences of the original URL with the new one, for ALL the sub blogs as well as the master one. After editing the wp-config file.
It looks like WP multisite has some way to go before maturity..

Byq292u

Cach, Dashboard, Database Login, Disaster, Heading Home, Jackpot, Neat Trick, Red Letters, Speed Issues, Supercache, Train, wordpress, wordpress plugin, wp

WP-SUPERCACHE ATE MY WEBSITE! – It’s EVIL!

Whatever you do, BE CAREFUL if you are using the WP-SUPERCACHE WordPress plugin..

I’ll explain the problem: My site was having speed issues, so I investigated alternative cach plugins. I settled on Quick-Cache.
So, I disabled Supercache, which then argued, in BIG RED LETTERS at the top of the dashboard, and advised me to visit it’s settings page, as caching was off. I didn’t want to do that, so I hit “deactivate” again.

BANG!. The site was dead. Not only that, but it was displaying the contents of the WP-CONFIG file in plain text on the frontpage!!! Including database login details, password, etc.. DISASTER!

I was heading home on the train as all this was unfolding, so I got the support guys at Unlimited Web Hosting to shut down the site, which they did, instantly.

We then spent most of the night, on and off, trying to get the site back up.
Unlimited showed me a neat trick to disable all WordPress plugins without access to the site.. I’ll be posting about that later..

Anyway, I decided that wp-supercache had corrupted something, probably wp-functions, so I reloaded WordPress over the existing files (after configuring wp-config).

Jackpot! The site came back up. I then re-enabled the plugins, one-by-one. (they were all disabled from earlier).

DELETED WP-Supercache, and installed and enabled Quick-Cache.
I suggest you do the same.

Byq292u

Cach, Dashboard, Database Login, Disaster, Engine Optimisation, Heading Home, Jackpot, Neat Trick, Offline Marketers, Red Letters, Speed Issues, Supercache, Train, wordpress, wordpress plugin, Wordpress Themes, wp

WP-SUPERCACHE ATE MY WEBSITE! – It’s EVIL!

Whatever you do, BE CAREFUL if you are using the WP-SUPERCACHE WordPress plugin..

I’ll explain the problem: My site was having speed issues, so I investigated alternative cach plugins. I settled on Quick-Cache.
So, I disabled Supercache, which then argued, in BIG RED LETTERS at the top of the dashboard, and advised me to visit it’s settings page, as caching was off. I didn’t want to do that, so I hit “deactivate” again.

BANG!. The site was dead. Not only that, but it was displaying the contents of the WP-CONFIG file in plain text on the frontpage!!! Including database login details, password, etc.. DISASTER!

I was heading home on the train as all this was unfolding, so I got the support guys at Unlimited Web Hosting to shut down the site, which they did, instantly.

We then spent most of the night, on and off, trying to get the site back up.
Unlimited showed me a neat trick to disable all WordPress plugins without access to the site:

Disable all active plugins.

Anyway, I decided that wp-supercache had corrupted something, probably wp-functions, so I reloaded WordPress over the existing files (after configuring wp-config).

Jackpot! The site came back up. I then re-enabled the plugins, one-by-one. (they were all disabled from earlier).

DELETED WP-Supercache, and installed and enabled Quick-Cache.
I suggest you do the same.

WordPress Optimisation

I’ve just been comparing the pageload times for two of my similar (architecture, not content) wordpress sites.

Site A was coming in at about 1000-1500 milliseconds, whereas Site B was anything up to 6000 milliseconds 🙁

Turns out that caching had been disabled during a search to find a dodgy plugin, but never re-enabled on Site B..

That got me thinking though.. what if I could get the load time down.. would that improve the bounce-rate?

So, before I starting messing about with settings, I took some baseline stats with www.whichloadsfaster.com, (try it, it loads two pages in parallel, and measures load times..)

Then I re-enabled caching on site B. Suddenly, Site B loads faster than site A..
Next move: use the same caching settings on Site B on Site A.. (Site B had compression turned OFF, A was ON..)
Bingo! Both sites are now around 700-1000 milliseconds!

Next move: use the csprites plugin on both sites. (this makes dynamic css sprites from the images, loads faster).

We are now down to 500-750 Milliseconds on BOTH sites.

Can I just remind you of where we started here?

Site	Before (ms)	After (ms)
A	1000-1500	500-750
B	6000	500-750

P.S. this took less than half an hour, all-in..

Plugins used: wp-supercache, csprites
Tools used: www.whichloadsfaster.com

Byq292u

blog, multiple posts, tumblr, tumblr blogs, tumblr posts, update, update button, wp, wp posts, wp2tumblr plugin

Tumblr

Experimenting with Tumblr blogging.
I’ve set up two Tumblr blogs corresponding to WordPress sites. These sites have the wp2tumblr plugin installed, which creates tumblr posts when the WP posts are updated.

Unfortunately, it doesn’t work for RSS generated posts, but it’s easy enough to select multiple posts for edit, and just hit the update button.

We’ll see if anything gets referred from Tumblr..

Tag Archive wp

WordPress Database – Delete Orphaned Posts

Delete Orphaned Posts

Delete Orphaned Posts

Like this:

Better WordPress Security

Like this:

WordPress Multisite Problems

Like this:

WordPress Optimisation

Like this:

Tumblr

Like this:

Tag Archive wp

Delete Orphaned Posts

Delete Orphaned Posts

Like this:

Like this:

Like this:

Like this:

Related External Links

Like this:

Like this:

Like this: