Comments on: Move Your wp-content Area

By: Alex Denning

Alex Denning — Tue, 24 Nov 2009 21:27:32 +0000

It won’t move anything, only stuff you upload from change onwards.

By: Liew Cheon Fong

Liew Cheon Fong — Tue, 24 Nov 2009 17:14:10 +0000

good for new blogs but for existing blogs, you will need to do redirect with mod_rewrite .-= Liew Cheon Fong´s last blog ..Top 5 Antivirus Programs for Windows 7 =-.

By: Alex Denning

Alex Denning — Sun, 22 Nov 2009 09:29:02 +0000

It's debatable whether this actually has any effect, but theoretically it's a good idea. Even better would be to employ Amazon S3, something I'm looking at at the mo.

By: Alex Denning

Alex Denning — Sun, 22 Nov 2009 09:19:31 +0000

No. We're only moving uploads, not the whole wp-content folder. If you wanted to move the whole folder, you'd have to edit the wp-config.php file.

By: Kel

Kel — Sun, 22 Nov 2009 06:17:56 +0000

Useful tip, thanks – but be aware there are still a number of rogue plugins that expect a path similar to “mysite.com/wp-content/plugins/”, so altering your wp-content path might break some plugins. Check your site to make sure.

By: Indrek

Indrek — Sat, 21 Nov 2009 16:22:07 +0000

Thanks Alex for this tip. Hadn’t even thought about changing it. The source would definitely look much nicer with “media” or something like that.

@Thomas: that’s a good point. And although some might not agree with this method because is reduces the number of DNS lookups, this method really works.
.-= Indrek´s last blog ..How To Run Multiple Instances Of Conky =-.

By: Thomas Scholz

Thomas Scholz — Sat, 21 Nov 2009 13:33:27 +0000

It is even better to move all those files to a subdomain to allow your visitor’s browser more parallel HTTP requests.

If the local directory of your subdomain is /www/htdocs/username/_subdomain_files/ write this path into the first field and the public address (eg. http://files.example.com/) into the second.
.-= Thomas Scholz´s last blog ..Designlinks 9 =-.