You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cloud Library ignores the "Show images only from these sites" filter #1153
With Unified Image Access enabled and a single site added to Show images only from these sites, the Cloud Library still shows images from every site connected to the Optimole account. The filter appears to have no effect on the library query.
Steps to reproduce
Go to Optimole → Settings → Cloud Library
Enable Unified Image Access
Under Show images only from these sites, add one site (e.g. roundsky.s3-tastewp.com) and click Save changes
Open the Cloud Library tab
Expected
Only images from the listed site(s) appear.
Actual
Images from all sites connected to the Optimole account appear.
Notes
The setting appears to persist in the UI (the site chip remains after save), so this looks like the saved value isn't being applied when fetching the library.
With Unified Image Access on and one or more sites listed under "Show images only from these sites", the Cloud Library still lists images from every site connected to the Optimole account, and the sidebar still shows a folder for each of them. The setting saves and the site chip stays put, but nothing is actually filtered.
Requires: an Optimole account with at least two connected sites that have images, tested against staging — the change is on the Optimole service, so no plugin update carries it.
Under Show images only from these sites, add one of the connected sites and click Save changes.
Open the Cloud Library tab.
Bug: images from every connected site are listed, and the sidebar shows a site folder for each connected site.
Fixed: only images from the listed site appear, and the sidebar shows only that site's folder.
Edge cases
Leave the list empty — all sites' images should show; that's the intended "all sites" behavior, not a regression.
Add a second site to the list — both sites' images appear, the rest stay hidden.
Images uploaded straight into the Cloud Library (not coming from a site) stay visible whatever the list contains.
Move an image from a non-listed site into a custom folder, then open that folder — the image is now hidden too, while the custom folder itself is never hidden.
Remove the site from the list and save — the library should go back to showing everything.
The site's own Media Library and the editor's image picker should be unaffected.
Fix: Codeinwp/optimole-service#1795 (merged Sep 16, 2026 — service-side, ships with the dashboard)
The candidate API passed the new whitelist, direct-upload, empty-list, domain-intersection, and folder-filter tests; the same filter assertions failed on the base revision as expected. Restricted-key behavior matched the base revision, and the local Media Library and editor picker remained unaffected. The plugin settings UI saved a one-site whitelist and the product accessor confirmed it persisted, but the reloaded chip was not visually rechecked. A disposable Optimole account with multiple connected sites and the candidate service deployed was unavailable, so the actual Cloud Library grid, sidebar, and several UI edge cases remain blocked. No product defect was observed in the coverage that ran.
Please still try
Try the complete Cloud Library journey on candidate staging with a disposable Optimole account containing images and default folders from at least three connected sites plus a direct upload.
Verify the allowed.example.com chip is visibly present after reloading Settings following Save changes.
Open a custom folder containing an image moved from a non-listed site and confirm the asset is hidden while the folder remains visible.
Add a second allowed site in the plugin UI, then inspect both the grid and sidebar before removing all allowed sites and inspecting them again.
Lab notes (2 passed · 8 blocked)
✅ The site's own WordPress Media Library and the editor image picker continue to show their existing site images when the Cloud Library whitelist excludes another
✅ A restricted sub-account API key retains its prior folder and site access behavior after the change.
⏸️ After Unified Image Access is enabled and one connected site is added under Show images only from these sites, Save changes persists the site and the site chip
⏸️ With one site whitelisted, the Cloud Library root grid shows only that site's images plus direct Cloud Library uploads and excludes images from every non-listed
⏸️ With one site whitelisted, the Cloud Library sidebar shows only that site's default folder plus custom folders and hides every non-listed site's default folder.
⏸️ Turning All sites on makes images and default site folders from every connected site visible again.
⏸️ Adding a second site to the whitelist shows images and default folders from both listed sites while all remaining sites stay hidden.
⏸️ Images uploaded directly into Cloud Library remain visible when a site whitelist is active.
⏸️ In a custom folder, an image originating from a non-listed site is hidden while the custom folder itself remains visible.
⏸️ Removing the last whitelisted site and saving restores all connected sites' images and default folders.
Candidate optimole-service 33f40d7c75d44477695456342b8ea00593ca8528; qa-base 5ae3ae909e4f0f7056cd13ba276ccf2bd1043e00. Local WordPress 7.1 sandbox on PHP 8.4.25 with Optimole 4.2.13 (optimole-wp tag v4.2.13, b12b2b6). Browser fixtures: QA-only seeded Optimole connected state, domains allowed.example.com/blocked.example.com/third.example.com, single local PNG attachment, and draft post; no real API/license key was used, and WP-Cron was disabled to prevent the fake key from triggering external synchronization. Candidate and baseline API integration tests used the product HTTP test path and wp_tests schema. The private Composer endpoint returned HTTP 503 twice, so isolated QA-only package placeholders were used for ACF Pro and Object Cache Pro to install the unrelated test dependencies. The candidate service was not deployed as a runnable local/staging service and no disposable multi-site Optimole account was available.
Activity
selul commentedon Sep 16, 2026
This can be tested on staging.
rodica-andronache commentedon Sep 16, 2026
🤖 Automated QA Repro Steps
With Unified Image Access on and one or more sites listed under "Show images only from these sites", the Cloud Library still lists images from every site connected to the Optimole account, and the sidebar still shows a folder for each of them. The setting saves and the site chip stays put, but nothing is actually filtered.
Requires: an Optimole account with at least two connected sites that have images, tested against staging — the change is on the Optimole service, so no plugin update carries it.
Reproduce on Optimole 4.2.13:
Edge cases
Fix: Codeinwp/optimole-service#1795 (merged Sep 16, 2026 — service-side, ships with the dashboard)
pirate-bot commentedon Sep 17, 2026
QA agent — API-level whitelist filtering passes, but Cloud Library end-to-end coverage remains blocked.
The candidate API passed the new whitelist, direct-upload, empty-list, domain-intersection, and folder-filter tests; the same filter assertions failed on the base revision as expected. Restricted-key behavior matched the base revision, and the local Media Library and editor picker remained unaffected. The plugin settings UI saved a one-site whitelist and the product accessor confirmed it persisted, but the reloaded chip was not visually rechecked. A disposable Optimole account with multiple connected sites and the candidate service deployed was unavailable, so the actual Cloud Library grid, sidebar, and several UI edge cases remain blocked. No product defect was observed in the coverage that ran.
Please still try
Lab notes (2 passed · 8 blocked)
Candidate optimole-service 33f40d7c75d44477695456342b8ea00593ca8528; qa-base 5ae3ae909e4f0f7056cd13ba276ccf2bd1043e00. Local WordPress 7.1 sandbox on PHP 8.4.25 with Optimole 4.2.13 (optimole-wp tag v4.2.13, b12b2b6). Browser fixtures: QA-only seeded Optimole connected state, domains allowed.example.com/blocked.example.com/third.example.com, single local PNG attachment, and draft post; no real API/license key was used, and WP-Cron was disabled to prevent the fake key from triggering external synchronization. Candidate and baseline API integration tests used the product HTTP test path and wp_tests schema. The private Composer endpoint returned HTTP 503 twice, so isolated QA-only package placeholders were used for ACF Pro and Object Cache Pro to install the unrelated test dependencies. The candidate service was not deployed as a runnable local/staging service and no disposable multi-site Optimole account was available.
Run
qa-agent_6aabedb85a9644.58141628.Full report, evidence and session trail