Peter

Thanks for pointing that out. It was a bug that is now fixed in version 1.0.8 of the plugin.

If you’re using an SMTP plugin, note that WordPress versions up to and including 2.8 have a problem with multiple recipients. I’ve explained a fix here:

https://www.theblog.ca/wordpress-smtp

Works for me using:

Host: smtp.gmail.com
Port: 465

SSL encryption

Username: full e-mail address

Note that Gmail or Google Apps E-mail, when using SMTP, only allows you to use “From” addresses that you have registered under that particular account.

Regarding the original question, the thing about WordPress is that all displays are templates. Typically, the front page just calls your “Main page” or index.php template (which loads the latest blog posts) in your theme. If you are using a static page as your front page then the “Main page” template is not loaded. If you look in the Settings > Reading menu, you’ll see that if you select to show a static page as the front page, you can designate a different page to show your posts (you can just create a blank page for that purpose); in other words, when that page is loaded, the “Main page” template is loaded. Then you just redirect to that page.

Hi jca,

I would have to agree with you here. My blocked was hacked over the spring by a known WordPress vulnerability (and this was before the patch was released). Had I renamed my wp-admin directory or added some sort of extra layer of protection, I’d bet my chances of getting hacked for that vulnerability would have been drastically reduced. Someone probably wasn’t doing any manual hacking — they’re likely to have been running a script that scanned for WordPress installs and attacked known files within the wp-admin directory. Not all hacks are run by scanning scripts, but many are.

As for your problem, I don’t think it’s possible to exclude specific files. However, you can copy that install.css file to somewhere other than the wp-admin directory, then insert a redirect rule at the top of the same .htaccess file that references .htpasswd:

RewriteEngine On
RewriteRule ^css/install\.css https://www.yoursite.com/install.css [L]

I think that the fact that the public error page references the admin folder should be filed as a bug and hopefully fixed in the future.

I definitely recommend Simple:Press Forum as well:

https://simplepressforum.com/

Have you looked into editing your .htaccess file on atheist.nu?

RewriteCond %{HTTP_HOST} ^atheist\.nu$ [NC]
RewriteRule ^(.*)$ https://www.end-of-silence.org/$1 [R=301,L]

Hi shadam, that functionality has now been added to version 1.0.0.

Hi shmooth, let me know what features you’d like to see and I’ll look into whether I can add them.

Yeah, I too have the same problem. Some of the users of my plugin mysteriously cannot use get_option (and they have WordPress 2.0 installations!) and when I tell them to use the deprecated get_settings instead, it seems to work!

Thanks, this was great. I was struggling for the longest time using code similar to what you just posted, but as it turns out I mistakenly had the called up the variable $incoming_comment with my globals. Silly, silly me.