- When changing themes does the content get removed? For instance, should I do all my theme customizing before handing the site over to a client to make content changes?
- No, the theme has nothing to do with the content. However, block placements are specific to a theme. So if someone arranges a page and then switches to a new theme those arrangements will be lost. That said, if the theme is a sub-theme and it is the first time enabling the theme, it will inherit all the blocks from the parent theme on the initial installation.
- While going through the local development tutorial videos it was clear why there was a need to add a key and a new repo for the theme, but what is the reason for the first "git init " command?
- The “git init” step assumes that a sub-theme repo has not yet been created. If you have already created a repo for the sub-theme then you can ignore this step.
- Once I’m happy with a new theme and its pushed to git, can I use that same theme across multiple sites?
- Yes, you can use it as much as you like, you will just have to sync it to each site through Site Factory.
- When copying the starter theme, the video goes through using a basic starter set. If I want to use the advanced theme do I need to do anything special to get the SASS to compile?
- When using the Advanced Starter kit, Sass will compile with Gulp. Both the Basic and Advanced Starter kits have a README.md file which will explain how to use it. https://bitbucket.org/ietwebdev/sitefarm-theme-one-subtheme-starterkits/src/advanced/README.md states that once you have installed node, gulp, etc… you can compile with "$ gulp”. This will create a watcher to recompile your sass on each save and reload your local browser. If all you want to do is a one time compile then you can do “$ gulp compile”. Do “$ gulp help” for more commands.
- Do I need to clear the cache to view every CSS change I make?
- In local development, you should not need to clear the cache for CSS changes. The only time in local development that you should need to clear cache is when adding PHP files, functions, classes, methods, etc. With your site on Site Factory, everything is always cached so you will need to clear the cache if you make any changes.
- I've enabled a module on my site but when I try to configure it (or any content types, for that matter), I get an error saying I'm not authorized to access the page.
- Having the Site Builder role does include the ability to access the Extend (modules) section, but it doesn't ensure you'll have the necessary permissions to configure anything you attempt to install yourself. This is a security measure to help users avoid irreparably damaging their site and/or making it incompatible with the SiteFarm service's development plan and future upgrades. If the module provides services or functionality your site(s) need, first check to see if a feature request has already been submitted or not. If it has, we invite you to contact us to ask that your interest in this feature be added to the work ticket. If no feature request has been made, let us know using the Feature Request Form.
