Photolab streamlines selling digital photos at scale through WooCommerce. Upload thousands of photos in batches, apply watermarks inline during upload, and publish each as a downloadable product \u2014 all from a single admin panel. Built for event photographers, photo studios, and anyone selling large galleries online.<\/p>\n\n
Key features:<\/strong><\/p>\n\n Requirements:<\/strong><\/p>\n\n Original photo protection:<\/strong><\/p>\n\n The If using Nginx<\/strong>, Consult your hosting provider documentation to apply this configuration.<\/p>\n\n\n The plugin handles high volumes, up to 2000+ photos per album. Uploads use chunks of 5 files (filterable via Yes. If Imagick is unavailable, Photolab automatically uses GD for watermarking. Performance on large volumes will be reduced compared to Imagick.<\/p><\/dd>\n No. The watermark is applied to a copy (saved in Watermarking is inline: it runs during the same HTTP request as the upload chunk. Photos are watermarked immediately as they arrive, not via a background queue. The The client sends a heartbeat every 30 seconds. If the server receives no heartbeat for 5 minutes (or 10 minutes if none was ever received), a recovery job transitions the album to Yes, up to 3 concurrent album uploads per user. Attempts beyond this limit return HTTP 429. Albums with the same name already in flight for the same user return HTTP 409.<\/p><\/dd>\n The client can retry the same If an expiration date is set for the album, the plugin automatically deletes the WooCommerce product, watermarked image, and database record via a daily job managed by Action Scheduler (bundled with WooCommerce).<\/p><\/dd>\n An Action Scheduler job Yes. An optional distributed lock is available: if WordPress uses an external object cache (e.g. Redis), the lock uses Yes. The WordPress REST API requires a permalink structure other than \"Plain\". The plugin shows an admin notice if Pretty Permalinks are not active.<\/p><\/dd>\n Yes. Photolab does not access In WooCommerce \u2192 Status \u2192 Logs<\/strong>, filter by source \n
\n
\n
photolab<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\nwp-content\/uploads\/Photolab\/photos\/<\/code> directory is protected via an .htaccess<\/code> file denying direct access. This works on Apache<\/strong> servers with mod_rewrite<\/code> enabled.<\/p>\n\n.htaccess<\/code> files are not read. Add a rule to your server block to protect the directory:<\/p>\n\nlocation ~* \/wp-content\/uploads\/Photolab\/photos\/ {\n deny all;\n return 403;\n}\n<\/code><\/pre>\n\n\n
How many photos can I upload per album?<\/h3><\/dt>\n
photolab_chunk_size<\/code>) for compatibility with shared hosting.<\/p><\/dd>\nCan I use the plugin without Imagick?<\/h3><\/dt>\n
Does the watermark affect original photos?<\/h3><\/dt>\n
wp-content\/uploads\/Photolab\/watermarked\/<\/code>). Originals are stored separately and protected from public access.<\/p><\/dd>\nWhen is the watermark applied?<\/h3><\/dt>\n
\/upload\/chunk<\/code> endpoint returns after processing completes. Download is blocked until the photo reaches the watermarked<\/code> state (HTTP 425).<\/p><\/dd>\nWhat happens if I close the browser during upload?<\/h3><\/dt>\n
aborted<\/code>. From the admin panel you can reset the album (POST \/albums\/{id}\/reset<\/code>) to resume, or delete it. Already-uploaded photos remain as valid WooCommerce products.<\/p><\/dd>\nCan I upload multiple albums at once?<\/h3><\/dt>\n
What happens if a chunk upload times out?<\/h3><\/dt>\n
\/upload\/chunk<\/code> with an Idempotency-Key<\/code> header. The original response is replayed from a transient (TTL 24h) without reprocessing files. Without the header, behavior is unchanged.<\/p><\/dd>\nWhat happens when a photo expires?<\/h3><\/dt>\n
How does the daily cleanup work?<\/h3><\/dt>\n
photolab_daily_cleanup<\/code> runs every 24 hours (default 03:00 UTC) performing a failsafe sweep: detects stuck watermark jobs >1h, re-enqueues stalled photos, retries failed photos within a 5-retry budget per photo, purges expired idempotency transients, scans for disk\/DB orphans (log only), and deletes Photolab logs older than 30 days (filter photolab_log_retention_days<\/code>). Action Scheduler logs are auto-deleted after 7 days.<\/p><\/dd>\nDoes the plugin work in multi-server environments?<\/h3><\/dt>\n
wp_cache_add<\/code> (atomic SET NX). Without external object cache, the fallback is a transient. Concurrent chunk attempts for the same album from different nodes return HTTP 423. CAS on the database is the final safeguard. Disable via filter photolab_use_distributed_lock<\/code>.<\/p><\/dd>\nAre Pretty Permalinks required?<\/h3><\/dt>\n
Does Photolab work with WooCommerce HPOS?<\/h3><\/dt>\n
wp_posts<\/code> directly for WooCommerce products and is fully compatible with High-Performance Order Storage (HPOS).<\/p><\/dd>\nWhere do I find the logs?<\/h3><\/dt>\n
photolab*<\/code>. Available sources: photolab<\/code>, photolab-fsm<\/code>, photolab-upload<\/code>, photolab-heartbeat<\/code>, photolab-recovery<\/code>, photolab-watermark-job<\/code>, photolab-rate-limit<\/code>, photolab-ownership<\/code>, photolab-download-guard<\/code>, photolab-idempotency<\/code>, photolab-cleanup<\/code>, photolab-lock<\/code>, photolab-logger<\/code>. Each entry automatically includes user_id<\/code>, album_id<\/code>, and other contextual keys. Sensitive data (passwords, tokens, emails) is automatically redacted.<\/p><\/dd>\n\n<\/dl>\n\n\n0.0.5 \u2014 Initial public release<\/h4>\n\n
\n