• 1.5.3 600aac43b6

    v1.5.3 Stable

    javier released this 2026-11-03 16:46:37 +00:00 | 0 commits to main since this release

    1.5.3

    Release date: 2026-11-03

    Highlights

    • Support window realigned: WordPress 7.0-7.2 (7.2 beta tested) and PHP 8.3-8.6 (8.6 RC tested) — Requires at least raised 5.3 → 7.0 and Requires PHP raised 8.1 → 8.3 per the support policy
    • Includes the never-released 1.5.2 changeset (vendor PHP-floor integrity fix, WP 7.2 / PHP 8.6 verification)

    Changed

    • WordPress minimum raised 5.3 → 7.0 and PHP minimum raised 8.1 → 8.3 (support policy: WordPress 7.0-7.2, PHP 8.3-8.6). The code's real floors remain lower — WordPress 5.3 (wp-compat: the single pre-7.0 binding symbol is the big_image_size_threshold filter, WP 5.3; 7.0 and 7.2 scan clean) and PHP 8.1 (aws/aws-sdk-php) — so the raise is a support-window decision, not a technical necessity
    • composer.json platform pin raised 8.1 → 8.3 together with the declared floor; dependency resolution stays locked to the supported minimum
    • Composer dependencies updated (net, from the last released 1.5.1): aws/aws-sdk-php 3.395.5 → 3.402.5 (3.402+ requires PHP >= 8.2, now allowed under the 8.3 floor — resolves KI-009), symfony/filesystem v8.1.6 → v7.4.21, guzzlehttp/guzzle 8.2.0 → 8.3.1, guzzlehttp/psr7 3.1.0 → 3.2.0, guzzlehttp/promises 3.0.2 → 3.1.0 (removes the Using "is" as a class name is deprecated since 8.6 deprecation raised on PHP 8.6), symfony polyfills updated (ctype stays at v1.37) (no known CVEs — composer audit clean for production and dev)
    • Dev tooling updated: PHPStan 2.2.14 → 2.3.5, johnbillion/wp-compat 2.0.1 → 3.0.1, php-stubs/wordpress-stubs 7.1.0 → 7.1.2, PHPUnit 9.6.36 → 9.6.38

    Fixed

    • Declared PHP floor integrity: since 1.4.4 the locked symfony/filesystem v8.1.x required PHP >= 8.4.1, so the installed vendor tree silently demanded PHP 8.4+ despite the declared minimum. The platform.php pin introduced with the 1.5.2 changeset guarantees dependency resolution can never exceed the declared floor (now 8.3)

    Compatibility

    • WordPress: 7.0 - 7.2 — floor verified with wp-compat 3.0.1 (requiresAtLeast 4.7 / 5.2 / 5.3 / 7.0 / 7.2): 7.0 and 7.2 are clean; runtime-verified on the WordPress 7.2-beta staging site — the only debug.log entries are core admin-bar icon notices introduced by WordPress 7.2 itself (core replacing its own dashicons with SVG via wp_get_icon(), wordpress-develop PR #12270)
    • PHP: 8.3 - 8.6 — declared-range PHPCompatibility scan 8.3-8.6 clean; runtime matrix green: full PHPUnit suite passes on PHP 8.3, 8.4, 8.5 and 8.6.0RC3, with no deprecations on 8.6; the full-range scan 5.6-8.6 documents the code's own (lower) syntax floor — the declared 8.3 is the supported policy window
    • Icon assessment (wordpress-develop PR #12270): no action needed — the plugin registers no icons of its own (the Settings submenu inherits core's menu icon; no admin-bar nodes; no dashicon references in code or assets), so core's switch to SVG admin icons requires no adaptation

    Security

    • composer audit (production and dev dependencies): no known CVEs
    • Full AGENTS-security.md checklist re-verified against the codebase — no new findings; no runtime code changes in this release

    Tests

    • PHP Coding Standards: 3.13.6 (0 errors)
    • WordPress Coding Standards: 3.4.1 (0 violations)
    • PHPStan: 2.3.5, level 9, 0 errors
    • PHPUnit: 96 tests, 211 assertions (green on PHP 8.3, 8.4, 8.5, 8.6.0RC3)
    • composer audit: no known CVEs
    Downloads
  • 1.5.1 a498b5af15

    v1.5.1 Stable

    javier released this 2026-11-03 16:45:04 +00:00 | 1 commits to main since this release

    1.5.1

    Release date: 2026-10-02

    Fixed

    • Remote name collisions no longer overwrite existing S3 objects: on the first upload of an attachment, the plugin probes the remote bucket (headObject) and, when the key is taken, renames the local files WordPress-style (file.jpg → file-1.jpg, file-2.jpg, …) before uploading, keeping metadata, _wp_attached_file, and GUID in sync. Previously a re-uploaded name silently overwrote the existing remote object (and every attachment pointing at it), because local files are deleted after upload and WordPress core deduplicates names against the local disk only. Re-uploads of an already-offloaded attachment keep their name (intentional overwrite). Non-404 headObject errors fall back to the previous upload-without-check behavior so uploads are never blocked

    Compatibility

    • WordPress: 5.3 - 7.1 (no new symbols)
    • PHP: 8.1 - 8.5

    Tests

    • PHPUnit: 95 tests, 207 assertions (7 new Media_Uploader tests covering rename-on-collision, local-candidate blocking, missing-original, and the headObject 404/NotFound/NoSuchKey/non-404 outcomes)
    Downloads
  • 1.5.0 7d59203323

    v1.5.0 Stable

    javier released this 2026-09-18 15:20:45 +00:00 | 2 commits to main since this release

    1.5.0

    Release date: 2026-09-18

    Highlights

    • Multisite uninstall now cleans up every site, not just the current one

    Fixed

    • Multisite uninstall scope (KI-005): uninstall.php iterates all network sites via get_sites() + switch_to_blog(), so post meta, options, and cron events are removed from subsites too. Each site's own opt-in setting decides; single-site flow unchanged

    Compatibility

    • WordPress: 5.3 - 7.1 (new symbols used — get_sites(), switch_to_blog() — predate the 5.3 floor)
    • PHP: 8.1 - 8.5

    Tests

    • PHP Coding Standards: 3.13.6 (0 errors)
    • WordPress Coding Standards: 3.4.1 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 88 tests, 164 assertions (6 new uninstall tests: single-site opt-in/opt-out/corrupt, multisite per-site cleanup, empty site-list fallback)
    Downloads
  • 1.4.4 29a034f975

    v1.4.4 Pre-release

    javier released this 2026-09-18 14:36:58 +00:00 | 3 commits to main since this release

    1.4.4

    Release date: 2026-09-18

    Highlights

    • Maintenance release: Composer dependency updates plus full code, security, and compatibility reviews — no behavior changes

    Changed

    • Composer dependencies updated: aws/aws-sdk-php 3.393.4 → 3.395.5, guzzlehttp/guzzle 8.0.2 → 8.2.0, guzzlehttp/psr7 3.0.1 → 3.1.0, symfony/filesystem v8.1.5 → v8.1.6 (no known CVEs)
    • Dev tooling updated: PHPStan 2.2.9 → 2.2.14, johnbillion/wp-compat 2.0.0 → 2.0.1, php-stubs/wordpress-stubs 6.9.4 → 7.1.0, szepeviktor/phpstan-wordpress 2.0.3 → 2.0.4, nikic/php-parser 5.8.0 → 5.9.0

    Security

    • composer audit (production and dev dependencies): no known CVEs
    • Full AGENTS-security.md checklist re-verified against the codebase — no new findings; all superglobal access remains validated and all S3 operations stay inside try/catch

    Compatibility

    • WordPress: 5.3 - 7.1 (floor re-verified with wp-compat 2.0.1: the single binding symbol is the big_image_size_threshold filter, WP 5.3 — a 4.7 floor fails on that symbol only; WordPress 7.2 is still in alpha with final release scheduled December 2026, so 7.1 remains the ceiling)
    • PHP: 8.1 - 8.5 (full-range PHPCompatibility scan 5.6-8.5 clean for the declared range; plugin code itself uses PHP 8.0 features — str_starts_with(), mixed type — which PHPCompatibility 9.3.5 does not flag, so the floor was confirmed by manual review; the effective floor stays 8.1 via aws/aws-sdk-php requiring >= 8.1)

    Tests

    • PHP Coding Standards: 3.13.6 (0 errors)
    • WordPress Coding Standards: 3.4.1 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 83 tests, 130 assertions
    • composer audit: no known CVEs
    Downloads
  • 1.4.3 5bb4d373fc

    v1.4.3 Stable

    javier released this 2026-08-24 10:48:11 +00:00 | 4 commits to main since this release

    1.4.3

    Release date: 2026-08-24

    Added

    • Manager detection now uses the ecosystem presence constant ROBOTSTXT_MANAGER_NOTICED (ROBOTSTXT Manager 1.6.2+); a plugin-list scan remains as fallback for older Manager versions — same method name and return type, no caller changes

    Changed

    • Composer dependencies updated: aws/aws-sdk-php 3.392.3 → 3.393.4, guzzlehttp/psr7 3.0.0 → 3.0.1, guzzlehttp/promises 3.0.1 → 3.0.2, PHPStan 2.2.8 → 2.2.9, johnbillion/wp-compat 1.5.0 → 2.0.0 (now a PHPStan extension) (no known CVEs)

    Localization

    • POT regenerated for 1.4.3 (no string changes); Spanish (es_ES) and Catalan (ca) translations verified — 69/69 strings in both locales

    Compatibility

    • WordPress: 5.3 - 7.1 (floor re-verified with wp-compat 2.0: big_image_size_threshold filter, WP 5.3; one false positive on wp_enqueue_script() positional $in_footer argument documented in docs/known-issues.md)
    • PHP: 8.1 - 8.5 (full-range PHPCompatibility scan 5.6-8.5; floor set by aws/aws-sdk-php requiring >= 8.1)

    Tests

    • PHP Coding Standards: 3.13.6 (0 errors)
    • WordPress Coding Standards: 3.4.1 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 83 tests, 130 assertions
    • composer audit: no known CVEs
    Downloads
  • 1.4.2 6a8de6e2e2

    v1.4.2 Stable

    javier released this 2026-08-17 15:51:27 +00:00 | 6 commits to main since this release

    1.4.2

    Release date: 2026-08-17

    Added

    • Dismissible admin notice on the Plugins page when the ROBOTSTXT Manager plugin is not installed or active, linking to https://www.robotstxt.software/plugins/robotstxt-manager/ — updates are delivered through ROBOTSTXT Manager
    • Persistent (non-dismissible) notice on Settings → iDrivee2 under the same condition

    Changed

    • Removed the bundled Gitea auto-updater (robotstxt-updater.php and update.json); automatic updates are now handled by the ROBOTSTXT Manager plugin
    • Plugin URI and new Update URI header point to https://www.robotstxt.software/plugins/idrivee2-media-upload/
    • Author URI updated to https://www.robotstxt.software/
    • Composer dependencies updated: aws/aws-sdk-php 3.383.2 → 3.392.3, guzzlehttp/guzzle 7.x → 8.0.2, WPCS 3.3.0 → 3.4.1, PHPStan 2.2.1 → 2.2.8 (no known CVEs)

    Localization

    • POT regenerated for 1.4.2 — includes the WP-CLI and data-cleanup strings that were missing since 1.4.0, and drops the removed updater strings
    • Spanish (es_ES) and Catalan (ca) translations updated: 69/69 strings translated in both locales

    Compatibility

    • WordPress: 5.3 - 7.1 (floor verified with wp-compat: big_image_size_threshold filter, WP 5.3)
    • PHP: 8.1 - 8.5 (full-range PHPCompatibility scan 5.6-8.5; floor set by aws/aws-sdk-php requiring >= 8.1)

    Tests

    • PHP Coding Standards: 3.13.6 (0 errors)
    • WordPress Coding Standards: 3.4.1 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 78 tests, 125 assertions
    • composer audit: no known CVEs
    Downloads
  • 1.4.1 6a8de6e2e2

    v1.4.1 Stable

    javier released this 2026-08-10 16:31:55 +00:00 | 6 commits to main since this release

    1.4.1

    Release date: 2026-08-10

    Highlights

    • Security hardening, data preservation option, and WP-CLI commands
    • 66 tests (up from 38), 100% coverage of tested classes

    Added

    • Data preservation option — checkbox under Settings → iDrivee2 to opt in to data deletion on uninstall (default: preserve)
    • WP-CLI commands: wp idrivee2 test-connection, wp idrivee2 cleanup-local-files, wp idrivee2 stats --days=N

    Security

    • Logger: validate IP with filter_var( FILTER_VALIDATE_IP ) instead of sanitize_text_field
    • Admin page: wp_unslash() at read point for $_POST['test_file']
    • Cron cleanup: wp_delete_file() replaces WP_Filesystem() (cron-safe, no credentials needed)
    • Uninstall: data preservation is opt-in per AGENTS policy (default: preserve all data)

    Changed

    • WordPress minimum corrected 4.1 → 5.3 (wp-compat verified)
    • Uninstall: delete_post_meta_by_key() replaces raw SQL
    • robotstxt-updater.php documented as EXTERNAL DEPENDENCY

    Compatibility

    • WordPress: 5.3 - 7.1
    • PHP: 8.1 - 8.5

    Tests

    • PHP Coding Standards: 3.13.5 (0 errors)
    • WordPress Coding Standards: 3.3.0 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 66 tests, 109 assertions
    Downloads
  • 1.4.0 cc1bca74fa

    v1.4.0 Stable

    javier released this 2026-08-10 16:22:41 +00:00 | 7 commits to main since this release

    1.4.0

    Release date: 2026-08-10

    Highlights

    • Security hardening, data preservation option, and WP-CLI commands
    • 66 tests (up from 38), 100% coverage of tested classes

    Added

    • Data preservation option — checkbox under Settings → iDrivee2 to opt in to data deletion on uninstall (default: preserve)
    • WP-CLI commands: wp idrivee2 test-connection, wp idrivee2 cleanup-local-files, wp idrivee2 stats --days=N

    Security

    • Logger: validate IP with filter_var( FILTER_VALIDATE_IP ) instead of sanitize_text_field
    • Admin page: wp_unslash() at read point for $_POST['test_file']
    • Cron cleanup: wp_delete_file() replaces WP_Filesystem() (cron-safe, no credentials needed)
    • Uninstall: data preservation is opt-in per AGENTS policy (default: preserve all data)

    Changed

    • WordPress minimum corrected 4.1 → 5.3 (wp-compat verified)
    • Uninstall: delete_post_meta_by_key() replaces raw SQL
    • robotstxt-updater.php documented as EXTERNAL DEPENDENCY

    Compatibility

    • WordPress: 5.3 - 7.1
    • PHP: 8.1 - 8.5

    Tests

    • PHP Coding Standards: 3.13.5 (0 errors)
    • WordPress Coding Standards: 3.3.0 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 66 tests, 109 assertions
    Downloads
  • 1.3.0 916d7845be

    v1.3.0 Stable

    javier released this 2026-07-18 13:31:17 +00:00 | 8 commits to main since this release

    1.3.0

    Release date: 2026-07-18

    Highlights

    • New image sub-sizes control: ship less data per upload, ideal for large camera files. Reduces work in both the WP 7.1 client-side path (browser) and the server-side path.

    Added

    • Settings field Image Sub-sizes under Settings → iDrivee2 with three modes: all (default), thumbnail (only the default thumbnail), none (no sub-sizes).
    • IDRIVEE2_MEDIA_SUBSIZES_MODE wp-config.php constant — same priority pattern as the S3 credentials; the field becomes read-only when set.
    • In thumbnail and none modes the big_image_size_threshold filter is also disabled, so WordPress no longer creates a -scaled derivative for images larger than 2560px.

    Security

    • composer audit CVEs resolved: guzzlehttp/guzzle 7.11 → 7.15, guzzlehttp/psr7 2.11 → 2.13, mtdowling/jmespath.php 2.8 → 2.9 (CVE-2026-55767 / 55568 / 55766 / 54133).

    Tooling

    • bin/preflight.sh added — automated pre-deploy verification per AGENTS-testing-build-deployment.md (PHPCS, PHPStan, PHPCompatibility, PHPUnit + coverage, composer audit, candidate ZIP inspection).
    • .claude/settings.json added — mechanical deny rules for deploy.sh, git push/tag/merge per AGENTS.md.

    Compatibility

    • WordPress: 4.1 - 7.1
    • PHP: 8.1 - 8.5

    Tests

    • PHP Coding Standards: 3.13.5 (0 errors)
    • WordPress Coding Standards: 3.3.0 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 38 tests, 60 assertions
    Downloads
  • 1.2.1 a97911a978

    v1.2.1 Stable

    javier released this 2026-06-05 09:47:38 +00:00 | 9 commits to main since this release

    1.2.1

    Release date: 2026-06-05

    Fixed

    • Infinite recursion on image upload — wp_update_post() (called to update the attachment GUID after S3 upload) was firing the edit_attachment WordPress action, which re-triggered the upload method, which called wp_update_post() again, creating infinite recursion. Xdebug killed the process at 512 stack frames, WordPress reported "The server cannot process the image". Fixed by: (1) removing the edit_attachment hook — wp_update_attachment_metadata covers all new-upload scenarios; (2) adding a static re-entry guard ($in_progress per attachment ID) as a safety net.

    • Fatal error: fclose() on already-closed stream — The AWS SDK (via Guzzle) closes file streams automatically after reading them for upload. The finally block was attempting to fclose() streams that were already closed, throwing TypeError: fclose(): Argument #1 ($stream) must be an open stream resource. Fixed by checking is_resource($fh) before calling fclose().

    Compatibility

    • WordPress: 4.1 - 7.1
    • PHP: 8.1 - 8.5

    Tests

    • PHP Coding Standards: 3.13.5 (0 errors)
    • WordPress Coding Standards: 3.3.0 (0 violations)
    • PHPStan: Level 9, 0 errors
    • PHPUnit: 22 tests, 54 assertions
    Downloads