Skip to content

KAZCODE Universal Storage 1.0.1

Latest

Choose a tag to compare

@kazmij kazmij released this 30 Aug 22:36

KAZCODE Universal Storage 1.0.1 is a reliability, data-integrity, compatibility, and WordPress.org review update for the 1.0.x production line.

This update focuses on making existing media safer to offload, verify, restore, migrate, and serve. It also updates the distributed package and readme disclosure for the current WordPress.org review. It does not introduce new provider counts, importers, or large feature workflows.

Data integrity and recovery

  • Strengthened remote verification before local media cleanup.
  • Local files are retained when the remote object cannot be verified with sufficient confidence.
  • Temporary provider failures, throttling, authentication failures, and network errors are now treated as unknown provider states rather than confirmed missing media.
  • Size verification is required before destructive local cleanup when an expected size is known.
  • Changed local bytes are uploaded even when the object key and byte length match an existing remote object.
  • Partial restore results preserve recovery information instead of clearing offload state too early.
  • Batch delete results now respect per-object provider errors so failed deletes remain visible and retryable.

Multi-profile and shared-media safety

  • Existing remote objects are addressed through their persisted Storage Profile binding instead of the current/default upload target.
  • Private/signed URLs, restore, verification, and local materialization use the profile that actually owns the object.
  • Amazon S3 profile/preset handling now ignores stale custom endpoint/path-style values, so a previous MinIO/custom endpoint cannot break AWS S3 verification.
  • Remote deletion is fail-closed when object ownership is ambiguous or a possibly shared object is detected.

WordPress media compatibility

  • Improved remote-only media compatibility with WordPress REST/editor flows, including context=edit.
  • Preserved big-image/original-image metadata behavior without forcing permanent local downloads.
  • Hardened metadata-generation sequencing for newer WordPress media callbacks.
  • Added an admin control to disable onboarding tutorials across plugin screens while keeping manual replay available.
  • Storage Profile deletion controls now remain visible and explain why deletion is blocked when a profile is still protected.

Concurrent operation safety

  • Hardened attachment operations with fenced leases so stale workers cannot commit authoritative state after another worker takes ownership.
  • Old lease owners can no longer release a newer worker's lock.
  • Destructive local/remote operations remain guarded by both verification and current operation ownership.

Compatibility and packaging

  • Improved Composer, AWS SDK, Guzzle, and PSR dependency isolation in the scoped release build.
  • Removed the unnecessary vendor/aws/aws-crt-php/format-check.py development helper from the distributed ZIP.
  • Added a package audit guard so Python files do not re-enter the release ZIP.
  • Clarified the External Services disclosure in readme.txt: generated s3.amazonaws.com URLs are administrator-configured Media Library object URLs, not external KAZCODE UI assets.
  • Verified coexistence paths for Composer-based WordPress installs and plugin dependency collisions.
  • The Free package remains Free-only; Pro functionality remains in the separate Pro add-on.

Upgrade notes

  • Version: 1.0.1
  • No database schema change.
  • Existing settings, storage profiles, object inventory, and media metadata are preserved.
  • This is the recommended 1.0.x hotfix for all 1.0.0 installations.