No edit summary |
m (Bot: Automated text replacement (-doesn't +does not)) |
||
| Line 1: | Line 1: | ||
The "Default" theme is not, actually, the "default" theme. While SMF starts out with it as the base theme, the "Default" theme is only a collection of the default templates. These templates are "fallbacks". If a custom theme | The "Default" theme is not, actually, the "default" theme. While SMF starts out with it as the base theme, the "Default" theme is only a collection of the default templates. These templates are "fallbacks". If a custom theme does not contain some required files, the software will use the corresponding files from the default theme's directory. | ||
So, the reason that you should not ever delete the default theme, is that all of your other themes will rely on files that are contained within the default theme's directory. If you delete those, none of your other themes will work. | So, the reason that you should not ever delete the default theme, is that all of your other themes will rely on files that are contained within the default theme's directory. If you delete those, none of your other themes will work. | ||
Revision as of 11:16, 13 June 2013
The "Default" theme is not, actually, the "default" theme. While SMF starts out with it as the base theme, the "Default" theme is only a collection of the default templates. These templates are "fallbacks". If a custom theme does not contain some required files, the software will use the corresponding files from the default theme's directory.
So, the reason that you should not ever delete the default theme, is that all of your other themes will rely on files that are contained within the default theme's directory. If you delete those, none of your other themes will work.
It is similar to URLs - if the base domain name isn't specified, (in example, just /style.css) it uses the default (making the URL, www.simplemachines.org/style.css). In this case, it works a bit different, but the concept is similar.
