I get an error when any action takes places after certain level of the nested folder.["Cannot read properties of null (reading 'querySelector')"]

[Hariprasath Senathiraja]

I get an error ["Cannot read properties of null (reading 'querySelector')"] when a certain action takes place ( delete, rename, create, refresh) after a certain level of nested folders. In mine, after the 2nd level, even though I do trigger these actions, I get the above error. But the action is taking place, for example, when a rename is taking place, the changes take place in the database perfectly. But the changes can't be seen. Instead of that, I get the above error. But if I go back to the before level and come back to this same level again, I can see the changes. In my case, everything works perfectly at the root level and 1st level inside the root level, after that, if I go inside the nested folder inside those levels. I get the above error..I have attached the relevant pic too.

Attachment: image_4_85b15375.png

[Sivakumar ShunmugaSundaram]

Hi Hariprasath Senathiraja,

We understand you're encountering a "Cannot read properties of null (reading 'querySelector')" error when performing actions like rename, delete, create folder, or refresh beyond the second level of nested folders. The actions appear to succeed on the backend (e.g., database updates), but the UI doesn't reflect the changes and displays the error instead. Navigating back and forth is required to see updates, and this doesn't occur at root or first-level folders.

I've reviewed the screenshot you shared, which clearly shows the error dialog in the context of a rename operation (or similar) within a deeply nested folder structure.

To assist further, tested rename, delete, folder creation, and refresh operations at multiple nested levels using a standard setup with AJAX provider for file operations. Unfortunately, unable to reproduce the error. This suggests the problem might be related to a specific configuration in your implementation.

Sample: https://stackblitz.com/edit/angular-wkrl1pyv?file=src%2Fmain.ts

Please review the shared sample and ensure your File Manager configuration and share are the same.

• If they are the same: confirm whether the issue reproduces in the shared sample as well. If it does, share the exact steps or a short screen recording demonstrating the issue.
• If your configuration differs: share your configuration details and the steps to reproduce the issue.

These details will help isolate the cause and assist further.

Regards,

Sivakumar S