Total CMS: content editing and deployment choices
Assess the proposed Total CMS version through its content model, editing and deployment responsibilities before assigning the store’s ongoing work.
- Published
- Last updated
Total CMS manages structured website content on a PHP server, with files holding the content and templates controlling its presentation. It suits a retailer whose developer maintains the site and gives staff defined fields for changing guidance. Assess the proposed version and publication controls before deciding who handles ongoing edits.
Identify the Total CMS version
Use the Total CMS 3 documentation for a Total CMS 3 proposal. The official migration guide describes version 3 as a rewrite of version 1. Content migration and template conversion are separate jobs, so an older site’s editing setup doesn’t establish how the new site works.
The current model groups records into collections. Each record has fields defined by a schema. Templates use Twig, a template language that places content into the page. The built-in Site Builder can publish pages directly without a static-site build. A separate frontend can instead read content through the application programming interface (API).
Have the proposal name the installed version, its documentation and the rendering arrangement. A directly rendered PHP site and a separate frontend have different release steps. Record which arrangement the quote covers, including any existing templates being replaced. The version 1 migration guide helps identify work hidden inside a general promise to upgrade.
Maintain the content the customer reads
Model guidance as reusable records with fields that staff can maintain without changing the page template. Keep the commerce system responsible for live prices, stock and orders.
Consider a fictional homewares retailer with a timber-table care guide and a delivery policy. Its proposed care collection could hold a title, care instructions, an image and a reference to the relevant product range. A delivery-policy record could hold dispatch guidance and delivery-area rules. These are suggested content fields, not a preconfigured retail package.
Store the care guide once and reference it from relevant product pages. If the advice changes, staff update that record instead of editing several copies. The developer must make each template read the shared record. A collection alone doesn’t make every page reuse its content.
Use the commerce system’s stable product or variant identifier to connect editorial guidance to a sellable item. A display name can change. The identifier lets the site distinguish similar tables while the commerce system supplies current availability. Keep price figures out of reusable care instructions unless a defined process updates them from the commerce record.
For the delivery correction, identify every destination that uses the policy. That can include the public policy page, product-page excerpts and connected customer assistance. Give each destination the approved text through a defined feed or import. Saving the CMS record doesn’t establish that a separate service has received it.
Publish, undo and recover safely
Confirm the configured publication rules and recovery path for the installed version. File storage describes where content lives. It doesn’t establish who approves an edit or which records a public page displays.
Total CMS documents access groups that restrict operations on collections. Its collection settings also document protected draft fields for a member-review pattern. Those controls need deliberate configuration for the store’s editorial workflow. Use the access-group reference to distinguish permission to edit content from permission to change templates.
Ask the developer to demonstrate the following checks on a non-public copy of the proposed site.
- Save an unapproved delivery-policy change. Confirm that signed-out visitors and public content feeds still receive the approved policy. Repeat with the reviewer’s account to establish who can release it.
- Approve a correction and follow its actual publication path. Open the public URL signed out, then check any product-page excerpt. Confirm that connected customer assistance receives the corrected source.
- Restore the prior approved record. Confirm that its public text returns and that a retained image still opens.
- Recover a deleted record and its media from the site backup. Test the restored page on the recovery copy before using that procedure on the store.
The distinction between the last two checks affects backup ownership. The backup documentation describes automatic record history from version 3.6.0. It keeps replaced or deleted record data, but excludes uploaded files and images. Record history therefore needs a separate site-data backup with a tested restore procedure.
If a corrected page still shows old text, inspect the content version and caches separately. The deployment guide identifies application caching, PHP caching and content delivery network caching as possible causes of stale output. Re-saving the same text won’t establish which copy the customer receives.
Assign the deployment work
Give a named maintainer responsibility for the PHP host, updates and restoration. Total CMS’s server requirements specify PHP 8.2 or later, required extensions and writable content storage. The hosting quote must cover those requirements and room for uploaded media.
Separate routine editorial work from technical maintenance in the agreement.
- Store staff maintain approved guidance and product references within their assigned collections.
- The developer maintains schemas, templates and any connection to the commerce system.
- The hosting maintainer handles server compatibility, access and backup storage, with a named person responsible for proving restores work.
- The support agreement assigns application updates and extension compatibility checks, including a recovery route after a failed update.
Total CMS documents application updates and rollback separately from content history. Keep both procedures in the handover. A restored application version doesn’t by itself restore the delivery policy a staff member changed.
Keep licence terms and any product limits attached to the version and written quote being assessed. Separate that charge from hosting, extension costs and ongoing developer support. Accept the proposal when the editing demonstration works and someone owns every technical step between an approved correction and the page customers receive.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.