tintypes

.htaccess contents:

# Block these IP addresses from reaching my site
order allow,deny
deny from 158.64.42.135
deny from 195.7.10.56
deny from 46.4.50.141
deny from 188.127.240.61
deny from 200.122.146.28
deny from 80.254.66.5
deny from 194.44.169.156
deny from 71.237.2.169
deny from 208.165.55.157
deny from 46.115.24.27
deny from 201.191.198.66
deny from 71.176.101.77
allow from all

# Block hotlinking of images
RewriteEngine on
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?bestrppc.com [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?roberteckhardtphotographs.com [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?innocentsabroad.com [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?://(www\.)?perfectlikeness.com [NC]
RewriteRule \.(jpg|jpeg|png|gif)$ - [NC,F,L]

# Protect the wp-login.php file from access
<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_URI} wp-login.php
RewriteCond %{REMOTE_ADDR} !^24\.6\.
RewriteRule .* http://bestrppc.com/ [R,L]
</IfModule>

# Protect the wp-register.php file from access
<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_URI} wp-register.php
RewriteCond %{REMOTE_ADDR} !^24\.6\.
RewriteRule .* http://bestrppc.com/ [R,L]
</IfModule>

# BEGIN WPSuperCache
# END WPSuperCache

# BEGIN WordPress
<IfModule mod_rewrite.c>

RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule  ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

</IfModule>
# END WordPress

I’d prefer, in this thread anyway, that we avoid discussing the pros and cons of security through obscurity. I’ve seen lots of discussion on this — so let’s assume I want to do it anyway.

Unfortunately, as I mentioned, option 2 does not work — not flawlessly, anyway. I my experience, option 2 has resulted in partially broken sites. There are, apparently, some instances of “wp_” in the database that should not be changed. Probably names of some plugins, for example. Possibly other instances. Problem is, I don’t know which instances should not be changed — when I look in the tables, there are quite a few that look debatable to me. I’m looking for some help in determining exactly where “wp_” should be changed, and where it shouldn’t. Or at least, I think that is the problem.

Thanks Andrea! I had done a refresh in Transmit with no luck. So, after your comment, I tried a simple quit and restart of Transmit — and voila, my plugins are all there. Lesson learned.