Table of Contents
How do I upload files to the media library?
CBSplit does not call this screen a media library. The module is Content > Assets. Assets are the images, style sheets, fonts, JavaScript, and other files you upload in the built-in file manager. There is no FTP access. The wiki does not publish file-type allow lists, size limits, folder names, or the public URL of an uploaded file. Those limits have to be read from the file manager itself.
Before You Begin
Log in with an account that can open Content > Assets. Verification required: the permissions screen's label for this module is not written next to the screenshot on Admins.
The Assets article points to a file-manager screencast and recommends fullscreen playback: Assets file manager screencast. Use that video for buttons the written page never names.
Do not plan an FTP upload. The article states that CBSplit does not offer FTP, and that the file manager is how files are uploaded and managed.
Page folders are not asset folders. Move selected to in Pages groups pages in the left panel. It does not upload a file.
The Getting Started guide lists Assets as one of the pieces you use, with layouts, snippets, and menus, when you build a layout.
Step-by-Step Instructions
- Open Content > Assets.
- Upload the file with the file manager shown in the screencast. Verification required: the written page does not name the upload button, a drag-and-drop area, or an overwrite prompt.
- Store images, style sheets, fonts, and JavaScript here. The article lists those categories and says “etc.”, so other document types may be accepted. Do not assume a type is allowed until the manager accepts it.
- Verification required: note any size or dimension error the manager returns. No numeric limit is published, so this article will not invent one.
- Reuse the file by inserting it into a page or layout. The Pages module has a WYSIWYG editor and a source view. Verification required: the wiki does not say whether the editor has an “insert asset” button, or whether you paste a URL the file manager displays.
- To place a stylesheet or a script on many pages, a snippet plus Snippet Insertion can inject HTML at the head, the top of the page, or the bottom of the page. That is a documented injection path. It is not, by itself, a documented asset URL scheme.
- Keep marketing pixels that should load only for one traffic source in a snippet with logic, not as a site-wide asset include. The Snippets article warns that a site-wide advertiser script reports all of your traffic to that advertiser.
Verification required: alt text for an image is not a documented asset field. The page editor's Meta Image is a social and search image for the page, not the alt attribute of an inline picture. See How do I configure SEO settings for individual pages?.
Example
A sales page needs one product photo and a small stylesheet.
Upload both files in Content > Assets. The photo is then placed in the page content. Verification required: copy the image address from the file manager using whatever copy or insert action that screen shows. Do not guess a path such as /assets/.
The stylesheet is a separate asset. How it is linked is covered in How do I customize CSS or styling in CBSplit?. Upload it once, then reference that same asset from the layout or from a head snippet so the offer page and the FAQ page share it.
If the same photo is needed on a second page, select the existing asset again. The Assets article describes the module as the place to upload files “to be used later on pages”, which is the documented reuse path. It does not describe a duplicate-file warning.
How to Verify
- After upload, the file is visible in the file manager. The written docs do not describe a success toast.
- Open the public page that embeds the image. The image request should return the file, not a broken-image icon.
- Open a second page that is supposed to reuse the same file. It should request the same address.
- Confirm you did not need FTP. If a contractor asks for FTP credentials, the published answer is that the file manager replaces FTP.
- If the file is a stylesheet, verify it with the CSS article's checks, not by looking only at the file list.
Troubleshooting
The upload control is missing
The account may lack access, or you are in Pages or in page folders rather than Content > Assets. Page folders do not accept file uploads.
FTP login fails
That matches the documented product behavior. Use the file manager. Do not treat a failed FTP login as a broken asset.
The image is in Assets and broken on the page
The page source points at the wrong address, or the address was guessed. Verification required: copy the address from the file manager again. Also check the layout's mobile tab. A mobile layout with its own HTML will not inherit an image that exists only in the default layout.
A large video never finishes
No size limit is published. Verification required: record the manager's error. The hotlinking page discusses loading images from outside CBSplit to save bandwidth, but that page mixes “enable hotlinking” with “Hotlinking Protection” and a separate /apps setup screen. Do not follow it as the upload procedure.
Someone replaced a shared image and every page changed
Reuse means pages point at one asset. Replacing that file changes every page that uses it. The wiki does not describe file versioning. Upload a new file if the old artwork must remain on older pages.
Frequently Asked Questions
Where is the media library?
Use Content > Assets. “Media library” is not the admin label in the Assets article.
Which file types can I upload?
Documented examples are images, style sheets, fonts, and JavaScript. An allow-list and a size cap are verification required inside the file manager.
Can I organize assets in folders?
Not in the written Assets article. Page folders are for pages. Verification required: if the file manager shows directories, use those labels rather than this article's guesses.
How do I set alt text?
No asset alt-text field is documented. If the WYSIWYG inserts an image tag, set alt in the source view of that page. Verification required: confirm the inserted markup on a test page.
