Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #46385 Docman reactivity issues
    Infos
    #46385
    Marie Ange Garnier (marieange)
    2026-02-12 11:01
    2026-01-20 09:45
    48114
    Details
    Docman reactivity issues

    Following request #46377

    There are a lot of reactivity issues in document, a lot of them comes from the removal of compat mode where the way of the store wasn't handled the same way, it will raise warning in console, when app is run in watch mode

    Known issues:

    Embeded view page

    • [x]create a version does not refresh the display [Vue warn] value cannot be made readonly: null, no longer reproductible on 10/02
    • [gerrit #36825]lock/unlock an element won't update the header document-Dmr3TiWA.js:343 [Vue warn] Set operation on key "lock_info" failed: target is readonly.
    • [gerrit #36826] delete the emedded will raise an error TypeError: Cannot read properties of null (reading 'user_can_write')

    Tree view page

    • [gerrit #36773] fold/unfold a folder raise warnings Set operation on key "is_uploading_in_collapsed_folder" failed: target is readonly. && document-Dmr3TiWA.js:343 [Vue warn] Set operation on key "progress" failed: target is readonly.
    • [gerrit #36852] document-CKQEag8O.js:15117 [vuex] state field "error" was overridden by a module with the same name at "error" => wont fix, only a comment in code, will be done at vuex removal
    • [x] document-CKQEag8O.js:343 [Vue warn] value cannot be made readonly: null (for isCurrentDocumentDisplayed) => won't fix
    • [x] [Vue warn]: Failed to resolve component: tlp-relative-date => won't fix

    Quick look page

    • [gerrit #36775] upload a new file version, many warnings are raised [Vue warn] Set operation on key "file_properties" failed: target is readonly. && document-Dmr3TiWA.js:343 [Vue warn] Set operation on key "lock_info" failed: target is readonly. && [Vue warn] Set operation on key "has_approval_table" failed: target is readonly. && document-Dmr3TiWA.js:343 [Vue warn] Set operation on key "is_approval_table_enabled" failed: target is readonly. && [Vue warn] Set operation on key "approval_table" failed: target is readonly. && [Vue warn] Set operation on key "lock_info" failed: target is readonly.
    Doc/Documentation manager
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Closed
    2026-02-12
    Attachments
    Empty
    References
    Referencing request #46385

    Artifact

    request #46768 delete an emedded will raise an error
    Display settings

    Follow-ups

    User avatar
    Marie Ange Garnier (marieange)2026-02-12 11:01
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Status changed from New to Closed
    • Close date set to 2026-02-12
    User avatar
    Marie Ange Garnier (marieange)2026-02-12 10:31

    [Vue warn]: Failed to resolve component: tlp-relative-date

    we do have the proper vite configuration, issue only occurs on watch mode and do not have any rendering issue

    I'm not sure it worth to spend some time to try to fix this

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-02-12 10:27

    document-CKQEag8O.js:343 [Vue warn] value cannot be made readonly: null (for isCurrentDocumentDisplayed)

    they can be solved by changing the way we access store const currently_previewed_item = computed(() => store.state.currently_previewed_item); const current_folder = computed(() => store.state.current_folder);

    they occurs because at some point during mounting of component the stores provides a "bad" reference, there is no interest of correct them, it won't cause any reactivity issue (the example bellow is on breadcrumb for currently displayed item)

    they will be solved when we'll remove the vuex store

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-02-10 15:07
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-02-10 15:01
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-02-10 14:15
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-02-05 11:37
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marie Ange Garnier (marieange)2026-01-20 09:45
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes