Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Allow deletion of default domain folders in Optimole Library

未关闭
#1,073 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
php
领域
backend, frontend

调研方向

首先跟踪现有的文件夹删除 endpoint 和 UI 的删除文件夹流程,然后定位阻止默认文件夹的 backend 验证逻辑。将确认对话框选项和非活动域选项与当前行为进行比较。完成标准是:默认文件夹可以通过明确且安全的路径删除,同时清楚地确认活动站点的风险,并且现有的删除流程仍能对普通文件夹正常工作。

由索引模型根据 Issue 内容生成。

描述

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)

主要语言
PHP
星标
73
派生
14
平均合并
2 天 13 小时
30 天内合并 PR
16

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Codeinwp/optimole-wp 的其他 Issue

查看 Codeinwp/optimole-wp 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。