ZOVANTA SOFTWARE / KNOWLEDGEBASE

Forovanta starter handbook • current release and edition notes: 161i

Upload images, paste pictures and attach files

This handbook defaults to the flat PHP starter. See current release and edition coverage for current changes and the separate PHP port. Earlier build references identify when a feature was documented; they are not a claim that both editions expose identical controls.

Use the shared editor's Image or Attach control to select a local file. Pasting an image also uses the upload path where supported by the initialized editor. These controls upload; they should not require a remote image URL. Wait for success before submitting the containing post.

An upload first belongs to your signed-in account as a draft. Saving the authorized post claims referenced uploads to that content. Do not copy another member's unclaimed attachment ID to reuse their private file. Invalid types, oversized bytes, missing CSRF or lost permission should be refused before a successful association is claimed.

For topic/reply attachments, downloads follow the containing post/topic/category access. A public topic can allow guests to download; a restricted topic must refuse readers who cannot view it. Imported IPS attachments and native uploaded attachments use distinct selectors, so equal numeric IDs cannot select the wrong table.

In Interactive demo mode, ordinary permitted members can upload through the same file validation/ownership rules. View-only refuses visitor writes. A normally signed-in real administrator retains owner access; a designated demo administrator is still a demo identity. Core 156w removed the old blanket demo-board upload refusal that also blocked the owner.

File limits come from the actual domain web runtime and application policy. A CLI php.ini or a large server limit alone does not prove the form/app permits that file. Keep the exact message and context for staff; do not set whole directories to777 or move private uploads into public storage to fix a refusal.