frikafrax

Can you try accessing the blog one more time to see if you’re still getting a blank page?

That’s odd that you’re getting a blank page. The blog displays correctly for me under Chrome, IE and Firefox, even after flushing their caches and reloading the blog.

I’ve re-uploaded and overwrote all the core WordPress files a number of times from a newly downloaded WordPress installation archive so I’m fairly certain that I have no missing or corrupt files.

I’m re-uploading the core WordPress files again right now, just to be certain.

EDIT: In addition, I’m getting the WordPress log-in page when I access wp-login.php directly.

I’ve switched two three different themes via manual editing of wp_options and the blog shows up fine on the public end each time, but the Dashboard always fails to load. It’s always blank and 0-bytes.

Here’s the blog.

Manually editing wp_options to change themes unfortunately didn’t fix the missing dashboard problem.

@andrea

I tested it out on my blog with Chrome and using the zBench v1.2.5 theme and the update works! ??

Wow, that’s great! Much appreciated! Thanks!

Thanks Andrea, appreciate it.

Of course, if it turns out that it’s not too difficult to integrate Login Dongle with Theme my Login, then by all means! But you have a point about doing things the standard WordPress way.

Although I’m PHP-challenged, maybe I’d be better off in the long term if I learned how to manually add a theme to my log-in page.

The reason Digg is blocked by default is due to Digg’s use of a doctored and suspicious user agent for its bot rather than a user agent which clearly identifies the bot as being from Digg.

This was explained in the user comments of the article you linked to.

Additionally, Bad Behavior has a whitelist feature. Just enter the IP or IP range used by Digg and problem solved.

Hi, Camu

I don’t seem to be getting the “Unknown column” error any more but the Slimstats dashboard widget is producing the following error message:

WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 9 for query SELECT t1.resource, t1.ip, t1.user, t1.dt, ts1.count
				FROM (
					SELECT t1.resource, MAX(t1.id) id, COUNT(*) count
					FROM wp_slim_stats t1
					WHERE t1.resource NOT LIKE '[%'   AND t1.dt BETWEEN '1330560000' AND '1333238399'
					GROUP BY t1.resource
				) AS ts1 INNER JOIN wp_slim_stats t1 ON ts1.id = t1.id
				ORDER BY ts1.count DESC, t1.resource ASC
				LIMIT 0,  made by wp_dashboard, do_meta_boxes, call_user_func, wp_slimstat_dashboard->show_top_pages, wp_slimstat_view->get_top

I tried toggling the Slimstats dashboard widget plugin with no effect.

I’ve just toggled Slimstat’s activation and reset the PHP error log.

My blog is very low traffic so I’ll get back to you in a little bit with the results. ??

Thanks!

@mickeyroush

We were speaking about the frequency of appearance of usernames and email addresses within the context of external blacklists. WordPress’ built-in tools don’t poll external blacklists.

Matching on just usernames would be a bad idea so I thought using criteria that is a combination of usernames with email addresses and their frequencies would help bans from being too broad.

I was thinking about stopping those spammers who use “spammy” usernames like “buy viagra cheap” or “streaming music” (etc) many, many times.

But you’re right. Adding an option to take frequency of email address into account over usernames looks like the way to go.

The frequency of use of identical email addresses appears to yield far more results, at least on SFS’s database.

@BostomCab

I’m currently trying the WP Mobile Detector plugin.

From what I’ve seen so far, WP Mobile Detector doesn’t alter blog URLs with query strings when serving pages to mobile devices so it won’t mess up your site where search engines are concerned.

(Apologies for necro-posting but I didn’t receive any email notifications for new follow-up posts on this thread.)

Spammer create fake user accounts for a number of reasons. Spammers like to build large reserves of”sleeper”accounts to utilize at some point, or to scrape content from email subscriptions for instance.

Probably the primary reason to create fake users is to exploit public user profiles. Google Webmaster Central Blog has an article on fake users and spam profiles.

You’re welcome! Glad I could be of some help!