-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Issues with newly created files (set name and open automatically) #42097
Closed
4 of 8 tasks
Tracked by
#3888
Labels
Milestone
Comments
juliushaertl
added
bug
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
files2vue
labels
Dec 7, 2023
related: #41772 |
8 tasks
55 tasks
cc @nextcloud/files |
skjnldsv
added
1. to develop
Accepted and waiting to be taken care of
and removed
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
labels
Jan 11, 2024
8 tasks
susnux
added
3. to review
Waiting for reviews
and removed
1. to develop
Accepted and waiting to be taken care of
labels
Jan 21, 2024
4 tasks
8 tasks
Not fixed in 28.0.3 While I can create a file name, the document does not open. Correct behavior is creating a file name and then the document should open automatically. NC27 works fine/appropriately. |
Reopen partly: For template files the file is currently not opened (this includes plain text files). |
4 tasks
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This still doesn’t work properly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
In previous versions when creating a new file you could set a name and the new file was opened directly with the default file action.
With 28 it seems that this behaviour changed in multiple ways due to the files to vue migration:
Steps to reproduce
Expected behavior
Installation method
None
Nextcloud Server version
master
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: