framework/sage
Template
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #1890 from rfair404/rfair/update-docs-for-resources

Browse Source 
Update inline documentation to reflect correct theme file locations
This commit is contained in:
Ben Word
2017-06-11 17:40:59 -06:00
committed by GitHub
parent c304c3041d da353de6ee
commit 384d95871d
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
resources/functions.php
View File

@@ -59,12 +59,12 @@ array_map(function ($file) use ($sage_error) {
/** /**
* Here's what's happening with these hooks: * Here's what's happening with these hooks:
* 1. WordPress initially detects theme in themes/sage * 1. WordPress initially detects theme in themes/sage/resources
* 2. Upon activation, we tell WordPress that the theme is actually in themes/sage/resources/views * 2. Upon activation, we tell WordPress that the theme is actually in themes/sage/resources/views
* 3. When we call get_template_directory() or get_template_directory_uri(), we point it back to themes/sage * 3. When we call get_template_directory() or get_template_directory_uri(), we point it back to themes/sage/resources
* *
* We do this so that the Template Hierarchy will look in themes/sage/resources/views for core WordPress themes * We do this so that the Template Hierarchy will look in themes/sage/resources/views for core WordPress themes
* But functions.php, style.css, and index.php are all still located in themes/sage * But functions.php, style.css, and index.php are all still located in themes/sage/resources
* *
* This is not compatible with the WordPress Customizer theme preview prior to theme activation * This is not compatible with the WordPress Customizer theme preview prior to theme activation
* *