[Bug]: Two different ' this name is already in use ' message implementations in file creation on web.
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
When creating a new file in the web interface and trying to name the file exactly like another file two 'this name is already in use' messages are shown through two different implementations.
One shows a red border around the input field and the message beneath it as long as the name is already in use.
The other is a tooltip style message that requires key or mouse button input to dissappear (although the name is still already in use, as indicated by the first mentioned implementation.
Steps to reproduce
- Create a file with a chosen name.
- Try to create another file of the same file type with the same name in the same folder.
- See two different implementations of the 'This name is already in use' message.
Expected behavior
To see only one message, preferably the red text type message with the red border around the input field.
Nextcloud Server version
33 (33.0.6)
Operating system
No response
PHP engine version
No response
Web server
No response
Database engine version
No response
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
No response
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing duplicate-name file creation in the web interface and trace the two validation messages shown during the flow. Done means the duplicate-name case presents only one message, preferably the red text with the red input border, while preserving the existing validation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100