update version folder structure for custom vhosts

Author: chadwickmeyer

Diff for: Internals/Overview.rst

@@ -9,6 +9,8 @@ Entity & Event Listener Timing
 
 We regularly use Entity and Event listeners to execute specific actions. It is critical that we create those actions in the right type of listener, so that they are able to modify the entity at the right sequence. Failure to execute your code could result in your changes not being persisted, or other dirty states that will create errors.
 
+NOTE: we have customized Doctrine's UnitOfWork file to add custom listeners that were lacking, and this has not been accepted by Doctrine's team (yet).
+
 Below is a summary of the timing and order of operations for the UnitOfWork.php (not real PHP code) to help you understand what order methods are executed for the Listeners:
 
 

Diff for: Overview/Versioning.rst renamed to Overview/Content-Versioning.rst

@@ -1,6 +1,6 @@
-##########
-Versioning
-##########
+##################
+Content Versioning
+##################
 
 Versioning allows an entity's revision history to be tracked. The best example of this in action is seen when editing content (i.e. pages or modules on a site). Whenever content is edited by a new user or if it's been more than a set period of time (e.g. 30 minutes) since the last time it was saved, then a new unpublished version of the content is created. The new version can be previewed on the site in "Preview" mode, but will not appear on the live site until the version is "Published".
 

Diff for: Overview/Features.rst

@@ -117,6 +117,6 @@ You can do advanced searches on one or more specific fields by using a special f
 Customization
 *************
 
-The framework allows you to customize the generic PHP controller or Twig template for any content type by adding an identical file to the client's site ``/var/wwww/vhosts/{ID}/src/`` directory. Design Templates can also be customized in the same way by adding files to the ``Sitetheory/Template{TEMPLATE-NAME}Bundle/src/`` directory. Individual pages can have a unique controller only for that view ID by adding a similar file with the additional view ID appended to the name.
+The framework allows you to customize the generic PHP controller or Twig template for any content type by adding an identical file to the client's site in the relevant version ``/var/wwww/vhosts/{ID}/v/1/0/src/`` directory. Design Templates can also be customized in the same way by adding files to the ``Sitetheory/Template{TEMPLATE-NAME}Bundle/src/`` directory. Individual pages can have a unique controller only for that view ID by adding a similar file with the additional view ID appended to the name.
 
 Learn more about :doc:`File Customizations </1.0/Tutorials/How-To-Customize-Files>`.

Diff for: Tutorials/How-To-Customize-Files.rst

@@ -28,11 +28,11 @@ This has a cascading priority that lets you customize files in a very targeted m
 Namespace                       Path
 ---------                       -----
 
-user                            /var/www/vhosts/100/user/1/
-siteTemplate                    /var/www/vhosts/100/src/Foo/TemplateBarBundle/src/
-site                            /var/www/vhosts/100/src/
-siteMasterTemplate              /var/www/vhosts/9/src/Foo/TemplateBarBundle/src/
-siteMaster                      /var/www/vhosts/9/src/
+user                            /var/www/vhosts/100/user/1/v/1/0/
+siteTemplate                    /var/www/vhosts/100/v/1/0/src/Foo/TemplateBarBundle/src/
+site                            /var/www/vhosts/100/v/1/0/src/
+siteMasterTemplate              /var/www/vhosts/9/v/1/0/src/Foo/TemplateBarBundle/src/
+siteMaster                      /var/www/vhosts/9/v/1/0/src/
 siteVendorTemplate              /var/www/core/v/1/0/src/Foo/TemplateBarBundle/src/
 siteVendor                      /var/www/core/v/1/0/src/Foo/
 siteVendorMasterTemplate        /var/www/core/v/1/0/src/Sitetheory/TemplateBarBundle/src/
@@ -178,8 +178,8 @@ For nested emulated bundles (where bundles customize another bundle) we make spe
 For vhosts with customized files, we must also make symlinks:
 
 .. code-block:: shell
-    /var/www/vhosts/100/assets/1/0/bundles/sitetheoryfoo -> /var/www/vhosts/100/src/Sitetheory/FooBundle/Resources/public/
-    /var/www/vhosts/100/assets/1/0/bundles/sitetheorybar -> /var/www/vhosts/100/src/Sitetheory/BarBundle/Resources/public/
+    /var/www/vhosts/100/assets/1/0/bundles/sitetheoryfoo -> /var/www/vhosts/100/v/1/0/src/Sitetheory/FooBundle/Resources/public/
+    /var/www/vhosts/100/assets/1/0/bundles/sitetheorybar -> /var/www/vhosts/100/v/1/0/src/Sitetheory/BarBundle/Resources/public/
 
 
 Customization of Assets
@@ -239,7 +239,7 @@ So to overwrite the FooBundle file from:
 
 You would put a file here:
 .. code-block:: shell
-    /var/www/vhosts/100/src/Sitetheory/BarBundle/Resources/public/css/baz.css
+    /var/www/vhosts/100/v/1/0/src/Sitetheory/BarBundle/Resources/public/css/baz.css
 
 
 
@@ -348,13 +348,13 @@ If you are customizing a site and need to customize the vendor's custom Content
 Client Site Files
 *****************
 
-Client Site files are located in the ``/var/www/vhosts/{ID}/src`` directory which mimics the exact structure of the core Sitetheory framework directory. To customize controllers or templates, just add the exact same file to the client’s site directory, e.g.
+Client Site files are located in the relevant version directory ``/var/www/vhosts/{ID}/v/1/0/src`` which mimics the exact structure of the core Sitetheory framework directory. To customize controllers or templates, just add the exact same file to the client’s site directory, e.g.
 
 .. code-block:: shell
 
-    /var/www/vhosts/1/src/Sitetheory/MenuBundle/Controller/MenuPrimary.php
-    /var/www/vhosts/1/src/Sitetheory/MenuBundle/Resources/views/MenuPrimary.html.twig
-    /var/www/vhosts/1/src/Sitetheory/MenuBundle/Resources/public/css/menu.css
+    /var/www/vhosts/1/v/1/0/src/Sitetheory/MenuBundle/Controller/MenuPrimary.php
+    /var/www/vhosts/1/v/1/0/src/Sitetheory/MenuBundle/Resources/views/MenuPrimary.html.twig
+    /var/www/vhosts/1/v/1/0/src/Sitetheory/MenuBundle/Resources/public/css/menu.css
 
 Controllers must include the same namespace and object name as the original file as well. They literally are identical.
 
@@ -377,14 +377,14 @@ If you need to customize a controller or template for a unique instance of a pag
 .. code-block:: shell
     :linenos:
 
-    /var/www/vhosts/1/src/Sitetheory/MenuBundle/Resources/views/MenuPrimary12345.html.twig
+    /var/www/vhosts/1/v/1/0/src/Sitetheory/MenuBundle/Resources/views/MenuPrimary12345.html.twig
 
 For Controllers, since you append the viewID to the filename you will also need to append it to the classname, e.g.
 
 .. code-block:: php
     :linenos:
 
-    /var/www/vhosts/1/src/Sitetheory/MenuBundle/Controller/MenuPrimary12345.php
+    /var/www/vhosts/1/v/1/0/src/Sitetheory/MenuBundle/Controller/MenuPrimary12345.php
     <?php
     class MenuPrimary12345 extends ContentController Base
     {