Adrian Kentleton

Not so much a solution, more a workaround!

I got what I wanted, my uploads in year folders under wp-content, by editing two files:

a. wp-config.php, adding (before ABSPATH lines)
define('UPLOADS', 'wp-content');

b. wp-includes\functions.php (line 2001)
$subdir = "/$y"; ie removing /$m from that line

It’s always a bit of a pain if you have to acheive what you want through editing files, rather than through the GUI, since there’s always a risk of losing customisations through updates/upgrades.

However, I always make a note of the files edited, comment the edits with my name (makes them easy to find later), and save a copy of the files with an .ak extension (so they’ll still be there if the originals are overwritten).

• This reply was modified 8 years, 8 months ago by Adrian Kentleton.

Ha! Still have the inability to login via my VPN, but have discovered why this morning, any access to my blog (and any other sites hosted on my server!) became impossible via my VPN.

I run a script every morning that analyses my mail and web server logs for inappropriate access attempts, which automatically adds the offending IP addresses to a server-wide firewall blocklist. The IP addresses of the exit nodes of the VPN servers I normally use appeared in this blocklist; one of the downsides of using a free, open-to-anyone, VPN service, which some folk will use for nefarious purposes!

Need to modify my script to allow those IP addresses as exceptions, then get back to investigating the original issue!

Thanks @tobifjellner for your ideas.

I’ve checked my server firewall logs, and whether I (try to) connect to the site home page or login page directly or through the VPN, the logs report allowing access on port 80 in every case; so I appear to be ‘getting inside’ whichever is used and wherever I try to go ie probably not an https issue.

However, will investigate the .htaccess issue. I don’t normally use these files since I have access to the main (Apache) server configuration, so control access and rewrite rules via <Directory> or <VirtualHost> directives. However, because I don’t normally use .htaccess, it’s quite possible something’s been lost in transalation as I’ve tried to adapt the rules to fit the different context.

Will post back when I’ve more info, either eliminated it as a cause without result, or resolved the problem.

Thanks again for your help.