Troubleshooting uploaded code that does not reach the storefront
Key Takeaway
The storefront runs code only from the active code version. If an upload succeeds but the storefront shows the error "System template default used directly or indirectly in custom site", set your upload tool's code-version to the active version shown in Code Deployment, then upload again.
Uploading a cartridge over WebDAV only puts files on the server. The storefront runs code only from the active code version, using the cartridges on the site's cartridge path. Page caching can also hide fresh changes. So when uploaded code doesn't show up, check each link in turn: which version got the code, whether that version is active, whether the site uses the cartridge, and whether caching or URL rules are hiding the result.
Code versions and the active version
An instance can hold several code versions at once, but it uses only the active code version. All templates, pipelines, scripts, and images come from that active version, so files in any other version don't reach the storefront.
You choose the active version in "Administration > Site Development > Code Deployment". When you activate a version, the server adds its folder to the list of folders where it looks up resources and removes the previous version's folder. The new code is then available immediately. Activation also clears cached items.