• Resolved luzat

    (@luzat)


    We are encountering the same problem as mentioned in these issues:

    https://wordpress.org/support/topic/removechild-error-when-renaming/
    https://wordpress.org/support/topic/error-1922/

    After hitting edit, changing the Alt text and saving, the error message

    Sorry, an error occured! Don't worry, I will fix this, so simply let me know about it.Here is some information about it:
    Node.removeChild: The node to be removed is not a child of this node

    is displayed. For us, it has been happening for a couple of weeks. It does not happen for every user, though. I was not yet able to reproduce it on Chrome 138 and Firefox 141/142 on Linux or in Chrome 133 and 138 on Windows within a virtual machine, while an employee does reliably get the error on Chrome and Edge on Windows.

    Looking at the code, I noticed that most removeChild calls in the JS are within react-modal. Maybe an update of that library will help? There have been a number of issues within react-modal regarding removeChild: https://github.com/reactjs/react-modal/issues?q=is%3Aissue%20state%3Aclosed%20removeChild It seems that workarounds may still be required: https://github.com/reactjs/react-modal/issues/769#issuecomment-2955444149

    Another idea may be that the network request is being filtered and this leads to some error. I will try to reproduce the issue and check where exactly it happens and whether there are any other errors on that user’s machine.

    We are running Media File Renamer 6.1.0 (currently not Pro), WordPress 6.8.2 and, possibly relevant, the Avada theme and FileBird Pro 6.4.8 on PHP 8.4. All software is current.

Viewing 1 replies (of 1 total)
  • Plugin Support Val Meow

    (@valwa)

    Hey @luzat! 👋

    This error is likely happening due to your environment. It can depend on both your browser version and the version of React running on your server, so please ensure that you’re using an up-to-date browser and the latest version of WordPress. Also, be mindful of any browser extensions, as they can sometimes interfere. This issue generally doesn’t occur with a fully updated setup.

Viewing 1 replies (of 1 total)

The topic ‘Node.removeChild error’ is closed to new replies.