Title: ScratchMonkey's Replies | WordPress.org

---

# ScratchMonkey

  [  ](https://wordpress.org/support/users/scratchmonkey/)

 *   [Profile](https://wordpress.org/support/users/scratchmonkey/)
 *   [Topics Started](https://wordpress.org/support/users/scratchmonkey/topics/)
 *   [Replies Created](https://wordpress.org/support/users/scratchmonkey/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/scratchmonkey/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/scratchmonkey/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/scratchmonkey/engagements/)
 *   [Favorites](https://wordpress.org/support/users/scratchmonkey/favorites/)

 Search replies:

## Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)

 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [Installing WordPress With Clean Subversion Repositories](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/)
 *  Thread Starter [ScratchMonkey](https://wordpress.org/support/users/scratchmonkey/)
 * (@scratchmonkey)
 * [6 years ago](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/#post-12870217)
 * 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.
 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [Installing WordPress With Clean Subversion Repositories](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/)
 *  Thread Starter [ScratchMonkey](https://wordpress.org/support/users/scratchmonkey/)
 * (@scratchmonkey)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/#post-12735119)
 * 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.
 *   Forum: [Installing WordPress](https://wordpress.org/support/forum/installation/)
   
   In reply to: [Installing WordPress With Clean Subversion Repositories](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/)
 *  Thread Starter [ScratchMonkey](https://wordpress.org/support/users/scratchmonkey/)
 * (@scratchmonkey)
 * [6 years, 1 month ago](https://wordpress.org/support/topic/installing-wordpress-with-clean-subversion-repositories/#post-12734829)
 * 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.wordpress.org/Installing_WordPress_With_Clean_Subversion_Repositories](https://codex.wordpress.org/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.

Viewing 3 replies - 1 through 3 (of 3 total)