• Resolved tezalsec

    (@tezalsec)


    Hi, the backup is not working. Using latest version, 5.2.3. Disabling all other plugins does not solve it.
    Getting these errors:

    [DOM] Found 5 elements with non-unique id #_wpnonce: (More info: https://goo.gl/9p2vKq) ​ ​ ​ ​ ​
    admin.php:1 [DOM] Found 5 elements with non-unique id #backwpupajaxnonce: (More info: https://goo.gl/9p2vKq) ​ ​ ​ ​ ​
    admin.php:1 [DOM] Found 2 elements with non-unique id #js-backwpup-add-new-backup: (More info: https://goo.gl/9p2vKq) ​…​​flex ​…​​flex
    admin.php:1 [DOM] Found 2 elements with non-unique id #js-backwpup-add-new-backup-form: (More info: https://goo.gl/9p2vKq) ​…​​flex ​…​​flex
    admin.php:1 [DOM] Found 2 elements with non-unique id #new_db: (More info: https://goo.gl/9p2vKq) ​ ​
    admin.php:1 [DOM] Found 2 elements with non-unique id #new_files: (More info: https://goo.gl/9p2vKq)


    Suspecting php/js routines​ ​are not working due to multiple id’s generated in html.
    Did some rollbacks all the way back to 5.1, the errors are definetely related to the new interface.

    Moving to another plugin for now.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Saransh

    (@saranshwpm)

    Hi,

    Thank you for your detailed message and for taking the time to share this with us.

    We’re currently investigating the matter and will get back to you with an update as soon as we have more information.

    Best Regards

    Thread Starter tezalsec

    (@tezalsec)

    I forgot to add, these errors already appear when loading the settings page, probably causing the “backup now” button to not function.

    Plugin Support Saransh

    (@saranshwpm)

    Hi @tezalsec,

    Thanks again for your earlier feedback.

    We wanted to follow up as our developers weren’t able to reproduce the issue on the standard browsers we test with. The console warnings alone shouldn’t block the “Backup Now” function, so we’d love to investigate further.

    If possible, could you reach out to us directly via support so we can take a closer look? With temporary access, we’ll be able to inspect what’s happening in your setup and identify the root cause.

    We’d really appreciate the chance to dig into this — looking forward to hearing from you!

    Thread Starter tezalsec

    (@tezalsec)

    Hi, I do not believe you will find the cause testing browsers (I am using Brave) or inspecting the console beyond this point. I agree the console warnings do not “block”. They are just informing you it has found multiple html elements containing the same id.

    I suspect your js or php function executing the backup function expects a single element with a certain id, and is therefore choaking on it and leaving the execution. Then the only question is, what in your codebase is creating and repeating these html elements, having id’s like “_wpnonce”?

    I am sorry, I won’t be involved beyond this point and won’t give out access to my site for this.

    @tezalsec The invalid HTML with non-unique id attributes has been reported already almost 4 months ago, nothing happened.

    Plugin Support Saransh

    (@saranshwpm)

    Hi @tezalsec,

    Just following up on this. Since we’re not able to replicate the issue on our end, it’s been difficult to troubleshoot without more details.

    To help us investigate further, could you please share the following:

    • Do scheduled backups work on your setup?
    • When you click “Backup Now,” does any entry appear in the plugin’s log?
    • Can you check if the JavaScript call that triggers the backup is being sent to the REST API? You can do this via your browser’s Network tab (Dev Tools). The call happens quickly right before the page reloads — if you catch it, what’s the response?

    We’d really appreciate your input on this so we can better understand what’s happening. Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Backup not working’ is closed to new replies.