ScratchMonkey

One additional glitch (which is just a documentation clarification): I ran into the ‘Sorry, you are not allowed to customize this site.’ message and, after much research and figuring out how to enable debugging, revealed that I’d put the extra settings for WP_HOME and WP_CONTENT_DIR at the end of wp-config.php, not before the “stop editing!” line. Turning on WP_DEBUG revealed that right away with a message that those variables were being defined twice. So I’d recommend adding to the guide that those settings must go before the stop-editing line.

Thanks. I could swear I looked at the core URL in the source browser and saw a src directory, but now it’s not there. I just have fat-fingered the URL when I tried to inspect it a couple days ago. But looking at it now I see the old layout. Which is good because I need to update an existing site and it would have been slightly painful with that reorg of the directory structure.

I just realized the protected link is supposed to go to my site. That’s not what I need help with. It’s how to organize the files on the web server so I can keep the svn working directory clean. As originally explained here:

https://codex.www.ads-software.com/Installing_WordPress_With_Clean_Subversion_Repositories

Let’s say I’m installing to /home/mysite. That page suggests I check out to /home/mysite/trunk and then create /home/mysite/wp-config.php in the directory above trunk to avoid polluting the working copy.

But the new layout puts the docroot in /home/mysite/trunk/src, so I’d have to put my wp-config.php in /home/mysite/trunk, which pollutes the WC. How are normal developers organizing their setups to avoid this? It looks like you just depend on the svn:ignore property on trunk.