Skip to main content
This document explains how the Zonely template system works in daily operations. It focuses on the main areas developers use most often: Templates, Template Changes, Outdated Templates, the Template Editor, and the SFTP workflow.

​
Overview

The template system is built to let you manage theme files safely without touching the core structure directly. In daily use, most work happens in one of these areas:
  1. Templates
  2. Template Changes
  3. Outdated Templates
  4. Template Editor
  5. SFTP access
Each screen has a different purpose, but they all work together as part of the same template workflow.

​
Templates

The Templates page is the main working area. This is where you browse template files, search through them, filter by theme, and open files for editing. It also includes the main actions developers usually need, such as downloading all templates, uploading a ZIP file, opening SFTP access, or rolling back template changes. You can also switch between two scopes here: Normal Template Used for the main website theme. AdminCP Template Used for the admin interface. In short, this is the screen you use when you want to find and work on a template file.

​
Template Changes

The Template Changes page only shows files that were changed. This makes it useful for quick review and cleanup. Instead of looking through every template file, you only see the files that currently have overrides or edits. From here, you can: View the difference of a file. Roll back a single file. Reset all changed templates at once. This page is especially useful after editing several files and wanting to check what actually changed.

​
Outdated Templates

The Outdated Templates page is used after core template updates. If the system detects that an override file is based on an older version of a template, it will appear here. This helps you identify overrides that may need to be updated after system changes. You can update files one by one or update all outdated templates together. The recommended approach is simple: First review the difference, then apply the update.

​
Template Editor

The Template Editor is the main editing panel. It opens inside a drawer and gives you a file tree on the left side and the editor area on the right side. Changed files are marked in the tree, so it is easier to keep track of what has been edited. The main actions at the top are: Save Changes Saves the current file content. Revert Changes Rolls back the current file. This editor is where most panel-based template work is done.

​
Daily workflow

In normal daily use, the workflow is usually very simple.

​
Editing a template from the panel

  1. Open the Templates page.
  2. Choose the correct scope.
  3. Select the theme if needed.
  4. Find the file using search or the file list.
  5. Click Edit.
  6. Make your changes inside the editor.
  7. Save the file.
  8. If needed, open Template Changes to review the diff again.
This is the most common workflow for developers working directly from the panel.

​
Reverting a single file

If you want to undo one template file only:
  1. Open Templates or Template Changes.
  2. Find the related file.
  3. Click Revert.
  4. Confirm the action.
After that, the override content for that file is removed or reset.

​
Reverting all template changes

If you want to reset everything in the selected scope or theme:
  1. Open Templates or Template Changes.
  2. Use the action for reverting all template changes.
  3. Confirm the action.
This is useful when testing is finished or when you want to clean the environment quickly.

​
Updating outdated templates

When core templates change, you should review outdated overrides. The usual workflow is:
  1. Open Outdated Templates.
  2. Select the correct scope and theme if needed.
  3. Review the difference first.
  4. Update the file or update all outdated templates.
This helps keep your overrides in sync with the current system.

​
SFTP workflow

The SFTP action on the Templates page generates domain-based access details. Inside the modal, the system shows the connection details you need, such as: Server Port Username Password Quick connection URI The available actions are usually: Copy Connection Copies the connection details. Open SFTP Opens the connection flow directly. SFTP works together with the panel template system. This means you can edit files remotely and still manage them through the panel. After editing files through SFTP, it may take a few seconds before the changes appear in the panel. If the update does not show immediately, refresh the page and check again.

​
How the diff view works

The diff screen is designed to focus on changes instead of showing the full file as raw output. It helps you understand: Which file changed. Where the change happened. What the integration line is. Whether something was added, removed, or changed. If the system hides certain backend blocks internally, those areas may appear in the diff screen as labeled placeholders instead of raw code. This makes the comparison easier to read while still showing the structure of the change. A few habits make template work much easier and safer. Review the diff before saving important files. Prefer small edits instead of very large one-step changes. Check the Outdated Templates page after core updates. Use the AdminCP scope for admin-side work. Use the Normal Template scope for website-side work. These small practices reduce conflicts and make rollbacks easier if something goes wrong.

​
Common situations

​
Template could not be loaded

This usually means one of the following: The file path does not match the theme. The wrong scope was selected. A temporary loading issue happened while fetching the file. What to do: Check the scope first. Check the selected theme. Refresh the page and try again.

​
I reverted the file but the old content is still visible

This can happen if an old override file still exists physically or if the page is showing cached content. What to do: Run Revert again for the same file. Check Template Changes and confirm that the record is gone. Refresh the page without cache.

​
I edited a file through SFTP but I do not see it in the panel yet

This usually means the sync or mirror process has not completed yet. What to do: Refresh the Templates page. Open the diff view for the file. If needed, open the same file once in the panel editor and save it again.

​
Summary

The Zonely template workflow is built around a few core screens: Templates The main working screen. Template Changes Shows only changed files. Outdated Templates Used after core updates to keep overrides in sync. Template Editor Used for editing, saving, and reverting files. SFTP Used for remote editing while still staying connected to the panel workflow. Once you get used to these areas, daily template work becomes straightforward. Most tasks come down to finding the right file, making a safe change, checking the diff, and keeping outdated overrides under control.