Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Allow deletion of default domain folders in Optimole Library

Abierto
  • ¿Algo no está bien?
#1,073 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
php
Área
backend, frontend

Línea de trabajo

Empieza rastreando el endpoint existente de eliminación de carpetas y el flujo de eliminación de carpetas de la UI; después, localiza la validación del backend que bloquea las carpetas predeterminadas. Compara las opciones del diálogo de confirmación y del dominio inactivo con el comportamiento actual. Se considera terminado cuando las carpetas predeterminadas pueden eliminarse mediante una ruta segura explícita, los riesgos para los sitios activos se reconocen claramente y el flujo de eliminación existente sigue funcionando para las carpetas normales.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

customer report feature-request-triage

Impact: 75 · Confidence: 95 · Complexity: 45

Description

Problem: Users are prevented from deleting auto-generated 'default' folders (such as those created for domains) from the Optimole Cloud Library. When a domain is abandoned or migrated, users have no way to clean up the orphaned folder, leading to clutter and frustration.

Desired Behavior: Users should be able to delete default folders using the existing delete functionality. Rather than hard-blocking the action, the system should allow it subject to a strict confirmation or upon verifying the domain is inactive.

Acceptance Criteria:

  • Remove the hard restriction that prevents default folder deletion on the backend.
  • Introduce a strict confirmation dialog in the UI when attempting to delete a default folder (e.g., requiring the user to type the folder name to acknowledge it will break images if the site is live).
  • Alternatively, allow seamless deletion if the domain is verified as no longer linked/active on the account.

Customer Context

A premium user is trying to urgently organize their Property Portal Marketing account by deleting old domain folders ('newsite.simplyspanishhomes.com' and 'simplyspanishhomes.com'). They discovered the manual folder deletion feature but were blocked by an error stating they cannot remove default folders.

Root Cause Analysis

The existing 'delete folder' tool incorporates a protective restriction that hard-blocks the deletion of default (system-generated) folders. This was likely implemented to prevent users from accidentally breaking images on active websites. However, this protective default fails to account for valid cleanup use cases when a domain is decommissioned. The customer's inability to delete obsolete folders is caused by a gap in the validation logic, which lacks a pathway for intentional, confirmed deletion.

Alternative Suggestions

Improve the existing folder deletion endpoint by downgrading the restriction from a 'hard block' to a 'soft block'. Implement a warning confirmation prompt in the UI for default folders, or conditionally unlock the deletion if the API detects the domain is no longer actively connected to the Optimole account.

Reasoning

The customer is trying to delete folders associated with domain names but is blocked by a system restriction preventing the removal of 'default folders'. This issue doesn't require an entirely new feature, but rather an improvement to the existing folder deletion logic to accommodate the lifecycle of offboarded or inactive domains. We can improve the current product behavior by allowing these folders to be deleted after an adequate confirmation step.

Source: HelpScout #3341739214
Generated by feature-request-triage workflow (ID: feature-request-triage_6a1eb7ca56e5c1.18798109)

Lenguaje dominante
PHP
Estrellas
73
Forks
14
Merge medio
2 d 13 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Codeinwp/optimole-wp

Todos los issues de Codeinwp/optimole-wp

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.