OpenListTeam / OpenListTeam/OpenList

[Feature]需要密码访问界面增加自定义文案

Open
#1,463 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
24.7k
Forks
2.3k
Avg merge
1d 20h
Merged PRs (30d)
36

Description

请确认以下事项
  • 我已确认阅读并同意 AGPL-3.0 第15条
    本程序不提供任何明示或暗示的担保,使用风险由您自行承担。

  • 我已确认阅读并同意 AGPL-3.0 第16条
    无论何种情况,版权持有人或其他分发者均不对使用本程序所造成的任何损失承担责任。

  • 我确认我的描述清晰,语法礼貌,能帮助开发者快速定位问题,并符合社区规则。

  • 我已确认阅读了OpenList文档

  • 我已确认没有重复的问题或讨论。

  • 我认为此问题必须由OpenList处理,而非第三方。

  • 我已确认此功能尚未被实现。

  • 我已确认此功能是合理的,且有普遍需求,并非我个人需要。

需求描述
Image

我设置了密码。 访问的时候 要求输入密码。。但是 但是 但是:我后台设置了 顶部说明。并没有在 密码访问界面显示。 所以 我觉得应该要让密码访问界面给于提示。这样 让访问者可以到指定位置获取密码!

Image
实现思路

No response

附加信息

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the password-protected access page and how the configured top notice is rendered. Compare the two screenshots and verify whether the existing notice is omitted from this flow. Done means visitors see the configured custom text on the password access screen, with suitable coverage for the affected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.