Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Allow deletion of default domain folders in Optimole Library

オープン
  • 何か問題がありますか？
#1,073 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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時間
マージ済み PR（30日）
16

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Codeinwp/optimole-wp のほかの issue

Codeinwp/optimole-wp の issue をすべて見る

似ている issue

PHP の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。