You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Protect works on Stacks pages. Add the new Protect stack to a page, or call {{ protect_page() }}, to put it behind a passcode the way the protect feature does on a Site Builder page. It takes the same passcode, prompt title and scope options, and uses the extension's Default Passcode without them. A page from another website builder, or one written by hand, works the same way as long as it renders through the PHP API. Upgrade note: if Protect was already enabled, turn on its Twig Functions permission under Admin → Extensions → Protect. New permissions start off on an update, and until then a page with the stack shows a Twig error instead of its content. See Protect
A .starterignore file leaves paths out of tcms starter:export. List design notes, seed files or site backups in it, one path per line from the project root, and the starter won't carry them. See What Is Copied under starter:export in the Site Builder CLI docs
tcms setup:admin creates the first admin from the command line. It also marks setup finished, so a site made by a script or by Total CMS Studio opens ready to sign in instead of in the setup wizard. The password comes in on stdin, never as an option. See setup:admin in the CLI docs
Visitors can send files to a depot without an account. Add a publicUpload setting to a depot property and put {{ cms.form.depotDrop('inbox', {collection: 'dropbox'}) }} on a public page. You choose the file types, the size limits and the folder, and visitors can add files and nothing else. A visitor can also leave a comment and pick a tag from a list you set in the template, both saved on each file. Uploads are limited per address, and a hidden check keeps bots out without a CAPTCHA. Uploads are not virus scanned. See Public Uploads in the Forms docs
Client Help, a bundled extension for admin-only how-tos. Write posts in a private client-help collection and your client reads them in the admin: a home page with a note and featured articles, a sidebar by category, and articles in the same layout as the built-in docs. Clients need the extension's permission, not access to the collection, and drafts never show. See Client Help
A blogdown schema for blogs written in Markdown. It is the blog schema with content, summary and extra stored as Markdown, with the same RSS feed and SEO defaults. Pick it when you create a collection, and print those fields with the |markdown filter. Needs the Standard edition, like blog. See Styled Markdown
Extension menu items can use a stock admin icon. An admin nav item's icon takes raw SVG or a built-in icon by its CSS variable, such as var(--icon-help)
Changed
cms.form.builder() printed on its own is a working form.{{ cms.form.builder('contact', {addOnly: true}) }} now builds the schema's fields and a save button, and .build() does the same. Before, it rendered an empty form. A register: true form leaves out protected fields such as groups. Forms that use addField() or pass their own markup don't change
Deck items get an ID on their own. When the item schema has no autogen rule, a new item in the admin and a deck API post with no id get an ID like item_a1b2c3d. Existing autogen rules and saved IDs don't change
Lists in the docs and Client Help are indented. Bullets and numbers used to hang out past the left edge of the text. They now sit inside it, like the rest of the page
The setup wizard now defaults to Above Document Root. It tests whether it can write there, and preselects Document Root only when it can't. Above Document Root is also listed first, and Document Root is no longer labeled the default. Behavior change: sites that sit side by side, such as /home/you/one.com and /home/you/two.com, share one tcms-data folder unless each sets its own datadir, and the second site skips the wizard
The New Object shortcut is Control+N on a Mac and Alt+N elsewhere. Cmd+N opened a new browser window instead, and browsers keep Ctrl+N on Windows and Linux for themselves
Git-managed templates can be edited from the dashboard on a dev install. With env set to dev, a save writes to the same working tree your editor uses, and the editor shows where it landed. Every other environment stays read-only, so a deploy's git pull never conflicts, and the Template Designer API still refuses git-managed templates. See Git-First Templates
The impersonation badge shows the user's name. It showed their ID, and falls back to it when there is no name. The return button is now a close icon, with its label kept as a tooltip and for screen readers
Copy buttons show a check mark when they copy. They used to say "Copied!"
Removed
The Cursor rules file. Cursor now reads the agent skill that tcms skill:install adds to your project, so resources/cursor/totalcms.mdc is gone
Fixed
A starter's .gitignore leaves out node_modules/. It still named the old frontend/ folder, so a site made from a starter with a frontend showed every installed package as a new file in git
Starter exports keep the data folder's .htaccess.tcms starter:export left it out, so a starter's tcms-data/ lost the rule that keeps it private on Apache
The passcode form keeps the query string. After a correct passcode, Protect used to send the visitor back to the page without it.
Protect's settings no longer show a passcode that isn't in effect. The Default Passcode field started at 1234, but nothing was stored until the settings were saved, so a page relying on it accepted no code at all. The field now starts empty: save a passcode to use one. Sites that already saved their settings are unchanged.
Renaming a depot folder works again. The admin's folder rename answered 404 "Not found." and the folder only looked renamed until the page reloaded. A broader route registered earlier was catching the request first; the REST API's deck item update (PUT …/deck/{itemId}) was caught by the same route. Both reach their own handlers now, and a rename that fails shows the reason and puts the old name back. An empty folder renames too: it has no directory on disk until a file goes into it, and the rename used to fail trying to move one
A passcode with letters can be entered. The settings and Page Data took any text, but the passcode form only accepted digits, so a code like preview could never be typed. The form now shows a number pad only when the passcode is all digits.
Every depot list in the admin shows the original or custom download name. The list used to show the name on disk. Files sent through a public upload carry a random prefix there, and it no longer shows
Same-name uploads no longer mix. Two uploads of a file with the same name at the same time could get each other's chunks
Parallel uploads to a depot keep every file. A file could drop off the depot's list while it stayed on disk
A comment sent with an upload lands on the right file. When a file was renamed on save, the comment could go to another file or nowhere
Long values stay inside their cards on the API Keys and Access Groups pages. A long endpoint path or collection name used to run past the right edge of the card. It now ends in an ellipsis, and the full value shows when you hover over it
File download names are encoded properly. Names with quotes, accents or other unusual characters now download under the right name
The disabled-extension warning no longer breaks admin pages. It took a column of the page layout, which pushed the sidebar and content sideways. Warnings now sit in their own row across the top of the page
A saved template reaches the next request with Development Mode off. Saved pages, layouts and partials used to stay stale until the cache was cleared. Behavior change: files changed on disk, including by a git deploy, now show up without clearing the cache. A {% cache %} block still keeps its output until its ttl runs out
New Collection links show only to users who can create collections. Quick Nav and the dashboard's Quick Actions checked the wrong permission, so an editor saw a link the page then refused. The collections sidebar button was admin-only, hiding it from other users allowed to create collections, and the welcome panel's card had no check at all
The dashboard's "Email is not set up" alert checks the SMTP username. It checked the From address, which isn't what makes email work
Extension menu items stay inside the admin. An item whose URL started with a slash ignored the admin's base address and linked outside it