Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Fail to create a second file in the Files web interface, unless I reload #45486

Closed
4 of 8 tasks
blizzz opened this issue May 23, 2024 · 2 comments · Fixed by nextcloud/viewer#2322 or nextcloud/viewer#2368
Closed
4 of 8 tasks

[Bug]: Fail to create a second file in the Files web interface, unless I reload #45486

blizzz opened this issue May 23, 2024 · 2 comments · Fixed by nextcloud/viewer#2322 or nextcloud/viewer#2368
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback 29-feedback bug feature: files

Comments

@blizzz
Copy link
Member

blizzz commented May 23, 2024

⚠️ This issue respects the following points: ⚠️

Bug description

When creating a file in the web interface via "+ New", it will be created and opened immediately. When this document is closed and a second document is created, it will appear, but it will not be opened – it needs a page refresh. For some 3rd party applications it is bad, because the created files are just plain empty 0 bytes files, but e.g. MS's Office Online expects a setup office document.

It's probably a sharp corner from the F2V effort.

Steps to reproduce

  1. After a refresh of Nextcloud Files, it is possible to create a new speadsheet document. It opens automatically.
  2. Then you close the document and create a new spreadsheet document. It does not open automatically and stays at 0 bytes.
  3. When you reload the browser, creating a new document will open open Office Online again.
  4. If you try steps 1-3 for a simple "New text file" instead of a spreadsheet, the results are the same (only that it opens with the Text editor the first time after a refresh).

Expected behavior

It works just as the first time.

Installation method

None

Nextcloud Server version

28

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?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response
@blizzz blizzz added bug 0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback 29-feedback feature: files labels May 23, 2024
This was referenced May 29, 2024
Closed
Merged
@blizzz
Copy link
Member Author

blizzz commented Jul 11, 2024

@artonge I have to reopen it, due to issues on NC 28. Actually this situation is unchanged there.

Sometimes it actually is worse and does not open on the first time even, then I see this error in the browser console:

TypeError: e.fileInfo is null
    fn https://nc.zara/stable28/dist/files-sidebar.js:2
    r https://nc.zara/stable28/dist/core-common.js:2
    Q https://nc.zara/stable28/dist/core-common.js:2
    _render https://nc.zara/stable28/dist/core-common.js:2
    a https://nc.zara/stable28/dist/core-common.js:2
    get https://nc.zara/stable28/dist/core-common.js:2
    e https://nc.zara/stable28/dist/core-common.js:2
    mount https://nc.zara/stable28/dist/core-common.js:2
    $mount https://nc.zara/stable28/dist/core-common.js:2
    init https://nc.zara/stable28/dist/core-common.js:2
    h https://nc.zara/stable28/dist/core-common.js:2
    h https://nc.zara/stable28/dist/core-common.js:2
    Ci https://nc.zara/stable28/dist/core-common.js:2
    _update https://nc.zara/stable28/dist/core-common.js:2
    a https://nc.zara/stable28/dist/core-common.js:2
    get https://nc.zara/stable28/dist/core-common.js:2
    run https://nc.zara/stable28/dist/core-common.js:2
    ta https://nc.zara/stable28/dist/core-common.js:2
    yn https://nc.zara/stable28/dist/core-common.js:2
    gn https://nc.zara/stable28/dist/core-common.js:2
    promise callback*hn https://nc.zara/stable28/dist/core-common.js:2
    yn https://nc.zara/stable28/dist/core-common.js:2
    na https://nc.zara/stable28/dist/core-common.js:2
    update https://nc.zara/stable28/dist/core-common.js:2
    notify https://nc.zara/stable28/dist/core-common.js:2
    set https://nc.zara/stable28/dist/core-common.js:2
    open https://nc.zara/stable28/dist/files-sidebar.js:2
    exec https://nc.zara/stable28/dist/files-main.js:2
    openSidebarForFile https://nc.zara/stable28/dist/files-main.js:2
    mounted https://nc.zara/stable28/dist/files-main.js:2
    un https://nc.zara/stable28/dist/core-common.js:2
    Gn https://nc.zara/stable28/dist/core-common.js:2
    insert https://nc.zara/stable28/dist/core-common.js:2
    E https://nc.zara/stable28/dist/core-common.js:2
    Ci https://nc.zara/stable28/dist/core-common.js:2
    _update https://nc.zara/stable28/dist/core-common.js:2
    a https://nc.zara/stable28/dist/core-common.js:2
    get https://nc.zara/stable28/dist/core-common.js:2
    run https://nc.zara/stable28/dist/core-common.js:2
    ta https://nc.zara/stable28/dist/core-common.js:2
    yn https://nc.zara/stable28/dist/core-common.js:2
    gn https://nc.zara/stable28/dist/core-common.js:2
    promise callback*hn https://nc.zara/stable28/dist/core-common.js:2
    yn https://nc.zara/stable28/dist/core-common.js:2
    na https://nc.zara/stable28/dist/core-common.js:2
    update https://nc.zara/stable28/dist/core-common.js:2
    notify https://nc.zara/stable28/dist/core-common.js:2
    set https://nc.zara/stable28/dist/core-common.js:2
    set https://nc.zara/stable28/dist/core-common.js:2
    updateStorageStats https://nc.zara/stable28/dist/files-main.js:2
    throttleUpdateStorageStats https://nc.zara/stable28/dist/files-main.js:2
    f https://nc.zara/stable28/dist/files-main.js:2
    f https://nc.zara/stable28/dist/files-main.js:2
    emit https://nc.zara/stable28/dist/core-common.js:2
    emit https://nc.zara/stable28/dist/core-common.js:2
    emit https://nc.zara/stable28/dist/core-common.js:2
    h https://nc.zara/stable28/dist/core-common.js:2
    onSubmit https://nc.zara/stable28/dist/9647-9647.js?v=93895b40459d7fceb1fb:2
    open https://nc.zara/stable28/dist/9647-9647.js?v=93895b40459d7fceb1fb:2
    open https://nc.zara/stable28/dist/files-init.js:2
    handler https://nc.zara/stable28/dist/files-init.js:2
    click https://nc.zara/stable28/dist/files-main.js:2
    un https://nc.zara/stable28/dist/core-common.js:2
    n https://nc.zara/stable28/dist/core-common.js:2
    un https://nc.zara/stable28/dist/core-common.js:2
core-common.js:2:1917906

But in the "normal" case, when the first files is opened, but the second file not, there are no erros logged in the browser.

@blizzz blizzz reopened this Jul 11, 2024
@blizzz
Copy link
Member Author

blizzz commented Jul 11, 2024

For completeness, also spotted nextcloud/circles#1434 during testing, but i does not seem to have any effect. Same fickle behavior with circles enabled and disabled.

@artonge artonge mentioned this issue Jul 15, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap 28-feedback 29-feedback bug feature: files
Projects
None yet
Milestone
No milestone
1 participant
@blizzz