Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Filter top-level domain folders in WP Cloud Library based on site display settings

Aperta
  • Qualcosa non va?
#1,151 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php, wordpress
Ambito
frontend, web-dev

Direzione di ricerca

Inizia dal rendering della griglia di cartelle di Cloud Library nell’area di amministrazione di WordPress e dall’impostazione esistente “Show images only from these sites”, quindi confrontalo con il comportamento del filtraggio dell’elenco degli asset. Il lavoro è completo quando le cartelle dei domini di primo livello escluse sono nascoste, mentre le cartelle condivise e i casi senza filtro o con tutti i siti rimangono visibili; chiarisci se anche lo spostamento in blocco degli asset non assegnati rientra nell’ambito.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

customer report feature-request-triage

Impact: 75 · Confidence: 90 · Complexity: 40

Description

Problem: When a user configures 'Show images only from these sites' under Settings > Cloud Library in the Optimole WordPress plugin, the Cloud Library view still displays folder icons for all domains associated with the global Optimole account. In multi-client environments, this exposes non-relevant project folder names to site admins.

Desired Behavior: The Cloud Library folder list in the WordPress admin panel should respects the 'Show images only from these sites' configuration, hiding or collapsing domain folders that are not included in the allowed list.

Acceptance Criteria:

  • When 'Show images only from these sites' contains specific domains, only folder items corresponding to those domains (and shared folders) are listed in the Cloud Library folder grid inside WordPress.
  • Folders belonging to excluded domains are filtered out of the top-level ORDNER view.
  • If no domain filter is specified or 'Unified Image Access' displays all sites, all domain folders remain visible.

Customer Context

A pro customer managing multiple client websites under a single Optimole account configured the plugin settings on partner.easycredit.de to show images only from partner.easycredit.de. However, all domain folders from other projects (e.g. tertianum.de, ras-services.de) still appear in the Cloud Library view in WordPress, causing privacy/client concerns and clutter.

Root Cause Analysis

The customer is managing multiple distinct client websites under a single Optimole account. Their underlying goal is twofold: (1) prevent client site administrators from seeing folder names and assets belonging to other client websites in the WordPress Cloud Library, and (2) quickly organize unassigned images into the correct domain folders.

Currently, the plugin's 'Show images only from these sites' filter restricts which image assets appear under the media listing, but it does not filter out top-level domain folder icons in the Cloud Library UI inside WordPress. Furthermore, assigning unassigned images to domain folders requires moving each asset individually through the item options menu. Both issues stem from existing features (domain filtering and folder organization) not extending their filter or batch-management logic to all UI elements.

Alternative Suggestions

Update the Cloud Library UI rendering in the WordPress plugin to apply the domain whitelist filter configured in Settings > Cloud Library directly to the top-level domain folder array returned by the API.

Reasoning

The customer is experiencing two distinct issues when managing multi-site/multi-domain assets in the Optimole Cloud Library:

  1. Filtering domain folders in the Cloud Library view within WordPress: Even though the user set 'Show images only from these sites' to a single domain (partner.easycredit.de) in the plugin settings (as shown in image 1), the Cloud Library interface within WordPress still displays domain folders for all other sites connected to the Optimole account (as shown in image 2). The customer finds these extra folders distracting and embarrassing when managing multiple client projects. Instead of requiring a new feature, this is a gap between user expectation and current filter behavior — the setting 'Show images only from these sites' should also filter or collapse the top-level domain folders displayed in the WordPress Cloud Library view so that site-restricted views only show relevant domain folders.

  2. Unassigned assets management: The customer asks how to assign unassigned assets (images without folder attribution) to their correct domain folders. Currently, users must manually select and move individual assets one by one using the three-dot menu ('Move'). Enhancing the existing asset selection and batch action workflows in Optimole to support bulk moving unassigned assets to target domain folders resolves the second pain point.

Source: HelpScout #3451395720
Generated by feature-request-triage workflow (ID: feature-request-triage_6aa9099df2da94.95784861)

Lingua principale
PHP
Stelle
73
Fork
14
Merge medio
2g 13h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Codeinwp/optimole-wp

Tutte le issue di Codeinwp/optimole-wp

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.