PhotoSales StudioDocumentationVersion 6.8.0.1 · Platform
PhotoSales Studio 6.8.0.1

Platform Documentation

Installation, configuration and operational guide for administrators, managers, photographers and Unlimited Subscribers.

01

Overview

PhotoSales Studio is a self-hosted professional photography sales platform that combines gallery management, media processing, commerce, delivery, photographer revenue, CMS, Cloud storage and subscriber access.

FrontendPublic galleries, search, favorites, cart, checkout and customer delivery.
AdministrationGalleries, orders, customers, photographers, settings, QA and maintenance.
Photographer workspaceOwned galleries, upload, purchased-photo preparation, sales and earnings.
Subscriber portalSubscription-based access to active sale galleries and protected original downloads.
02

System requirements

Recommended runtime: PHP 8.2/8.3, MySQL, HTTPS and writable application data/upload directories. GD or equivalent image support is recommended for local image processing. For Full Cloud deployments, Cloudflare R2 or another compatible S3 endpoint is configured from Storage settings.

Production deployments should use HTTPS, private database credentials and regular backups.
03

Installation

Upload the PhotoSales Studio distribution to the target web directory.
Create an empty MySQL database and database user.
Open /install/ in the browser and complete the installer.
Create the initial administrator credentials and choose whether to install demo content.
After installation, open Administration and run the available readiness/QA checks.
04

Initial configuration

General settings

Set studio/site name, contact details, timezone, date format, currency, default frontend language and enabled languages.

Appearance

Configure Light/Dark theme assets, logo, favicon and frontend visual preferences.

Email & public forms

Configure SMTP, contact addresses and reCAPTCHA before enabling public form workflows.

05

Roles & permissions

AdministratorComplete platform access, settings, users, all galleries, all orders, settlements and QA.
ManagerOperational access to assigned photographers, relevant galleries, orders and revenue workflows.
PhotographerOwn galleries, uploads, purchased-photo preparation, own sales and earnings.
Unlimited SubscriberPrivate customer portal with access controlled by subscription status and dates.
06

Galleries

Gallery Editor controls title, event metadata, category, photographer ownership, sale formats, pricing mode, Featured status, slider visibility, search behavior, watermark policy and publication state.

Use Featured to manually control which galleries appear in the Featured Galleries widget independently from the homepage slider.

07

Smart Media Workspace

The workspace provides album navigation, photo grid and per-photo inspector. It supports EXIF, WebP/derivative status, watermark state, AI tags, sales/views/history and multi-edit actions.

In Full Cloud mode, the workspace uses existing Cloud frontend derivatives instead of generating permanent local display copies.

08

Pricing & formats

Each gallery can independently sell Digital, Print and/or Original formats. Digital size can be limited by pixels, Print can use configured dimensions/prices, and Original represents the protected master output.

Package discounts and coupons can be enabled per gallery.

09

Orders & checkout

Customers select photos and formats, build a cart and complete an order using enabled channels/payment capabilities. Orders progress through New, Confirmed, Paid, Processing/Preparation, Delivered, Completed or Cancelled states.

10

Delivery & Production Center

Preparation is performed per photographer and order item, while final delivery is performed per order. Photographers see their own purchased photos; Administrator and Manager can see the complete order.

Final delivery records channel, recipient/reference, notes and delivered-photo count. Retention/archive tools clean expired delivery packages safely.

11

Photographer sales & revenue

The platform tracks photographer ownership, sales attribution, commissions, settlements and payout status. Photographer views are restricted to their own revenue, while Administrator/Manager have broader reporting according to permissions.

12

Unlimited Subscribers

Administrators create subscriber accounts and control Active, Paused or Disabled state plus subscription start/end dates. Expired subscriptions lose access automatically.

Subscriber Login opens My Photo Access, where active subscribers can browse sale galleries and—on production installations—download authorized originals through protected Local delivery or short-lived signed R2 URLs.

13

CMS & TinyMCE

CMS Pages and reusable Content Blocks support rich text, SEO metadata, multilingual content and theme-aware rendering. TinyMCE includes formatting, alignment, code/source view and Accordion using safe native <details>/<summary> markup.

14

Cloud storage

LocalMaster and derivatives live on the application server.
HybridLocal-first behavior with verified Cloud fallback.
Full CloudVerified master plus frontend and sale derivatives live in R2; missing permanent local copies are not treated as errors.

Full Cloud cleanup

Use the built-in Cloud Local Cleanup tool only after remote readiness is verified. Do not manually delete the complete uploads directory.

15

QA Center

PhotoSales Studio includes Core, Platform, Payment and Release QA plus Cloud Storage QA, Content Integrity, Processing Verification, Storage Analyzer and Gallery Performance tools. Use these checks after installation, storage changes and before a production release.

16

Backup & maintenance

Use the platform Backup/Restore tools before major configuration changes or upgrades. Maintenance Center provides a controlled maintenance state, while lifecycle/archive modules manage delivery retention and historical records.

17

Security

Security controls include role/ownership authorization, CSRF protection, session hardening, sanitized rich text, private Cloud masters, short-lived signed download URLs and restricted public forms. Production sites should keep software and PHP dependencies current.

18

Upgrade procedure

Create a configuration/data backup and note the current application version.
Use the matching cumulative UPDATE package for an existing installation.
Do not overwrite user data unless the release instructions explicitly require it.
After deployment, clear browser/server caches if applicable and run QA Center checks.
Test login roles, galleries, checkout, Delivery Center and storage mode before declaring the upgrade complete.
19

Demo access

The public read-only demo installation is available at:

Admindemo_admin Demo2026!
Managerdemo_manager Demo2026!
Photographerdemo_photographer Demo2026!
Subscribersubscriber@demo.local Demo2026!

The demo installation is read-only: navigation is available, but changes, purchases, payments and protected downloads are disabled.