Skip to content

Manage Website Files

Open Website -> Platform -> File Management and select the Website Environment you intend to inspect.

File Manager is available for hosted WordPress, PHP, Static HTML, and Node.js Websites. It is not available for externally hosted Websites or while the selected Environment’s node capability is unavailable.

Choose a named File Root instead of a server path:

  • WordPress and Static HTML expose /web.
  • PHP and Node.js expose /app and /data.

Expand folder-tree branches as needed. Each branch loads only its direct child folders. The listing is paged, and directory sizes appear after background calculation so opening a folder does not wait for a recursive scan.

If your access includes Manage files, use Upload or drag files into the current folder. You can select multiple files; File Manager transfers up to three at once and reports each result separately. The default limit is 25 MiB per file.

Uploads never replace an existing file. When a name is already present, File Manager creates the lowest available underscore suffix before the extension, such as logo_1.svg, and shows the final path it used.

Use New folder to create a directory in the current File Root. Existing names receive the same underscore suffix treatment. Platform-managed paths and protected WordPress files cannot be changed through File Manager.

For a hosted WordPress Environment, use the compact LockDown control in the Website header to unlock WordPress core for 15 minutes, 1 hour, 4 hours, or 24 hours. File Manager permits core changes only after the header reports Unlocked; it blocks new core mutations again as soon as LockDown is observed as armed. The control never disables LockDown permanently, and wp-content remains manageable while core is armed.

The folder tree and file table mark entries currently protected by LockDown or platform policy.

Select a file to use Download or Edit from either the toolbar or its context menu. Browser downloads support resuming and ranges up to the configured limit, which defaults to 1 GiB. Use SFTP for larger transfers.

The text editor supports approved text formats up to the configured limit, which defaults to 2 MiB. Every save checks the version opened by the editor. If another process changed the file, choose Reload to discard the draft or Save as new file to preserve it without overwriting the newer version.

For a TMXIO-managed wp-config.php, the editor shows the complete file but only the Customer Configuration Section is editable. Saves validate PHP before replacing the file. If a valid edit causes a runtime problem, choose Restore last-known-good, review the warning, and confirm the recovery. Recovery replaces only the customer-owned section, keeps the current TMXIO-managed settings, and refuses to overwrite a version that changed after you opened it. The action requires Manage files, recent passkey verification, and an unlocked wp-config.php.

Sensitive filenames remain visible to users who can view files, but their contents require Manage files and passkey verification from the last 15 minutes. Platform secrets and host-managed configuration are never available as file content. Changes under /app are live and untracked, and the next Deploy replaces them.