Multiple issues with version 5.5

Resolved Andis
(@andydegroo)

7 months, 2 weeks ago
Here are my observations after recent updates to the new UI
1. Saved jobs data in inconsistencies with UI
  Extra entries present in the backwpup_jobs option after deleting default and legacy jobs except for one. This is causing inconsistencies – UI shows the job with database backup enabled but when running the job it doesn’t even try to backup database.
  I went to inspect and exported the jobs as JSON using wp-cli command wp option get backwpup_jobs --format=json > backwpup_jobs.json .
  There are two partial (with only some options present) extra entries at the end of JSON object. One of them has a “jobid”: 4 which matches the actual job and overrides the "type": ["FILE", "WPPLUGIN"] option from actual job entry but only in UI. A sample from the list:
  "backup_ids": { "FOLDER": 7, "DROPBOX": 8 }, "type": ["FILE", "WPPLUGIN"], "jobid": 4, "lastruntime": 13 }, "4": { "type": ["DBDUMP"], "activetype": "wpcron", "cron": "0 3 * * *" }, "5": { "jobid": 4, "type": ["FILE", "DBDUMP", "WPPLUGIN"] } }
  This might be the reason behind this previous issue report: No Database Backup
  Possible workaround: Disable and re-enable the database backup option for the job.
2. The global option and indivisual job option "mailaddresssenderlog" (the sender’s address) defaults to admin_email option.
  This is absolutely not what you want in most cases. The e-mail message would be blocked by most MTAs or dropped by receiving SMTP servers.
  Also, the option is not editable per-job and job entries aren’t updated when the global/default changes in “Advanced settings > Logs settings”.
3. The UI accessibility needs a lot of work
  Start with the basics like tab navigation, visual focus states, properly labeled form fields, and buttons. A11y should be a priority throughout development process, not an afterthought or nice to have. Please hire a a11y consultant if not sure where to start.
4. Other issues in the new “nicer” UI:
  - Job entries can’t be edited when deactivated
  - Multiple HTML elements in the page have clashing id properties which may cause issues.
  - Modal settings sidebar doesn’t receive focus when opened and isn’t set as modal but acts as modal.

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

Thread Starter Andis
(@andydegroo)

7 months, 2 weeks ago

The UI inconsistencies are even worse;
I tried adding a new job but for some reason both job entries in UI now have same jobid=5 judging by the data-job-id HTML properties and HTTP request params. Changing or toggling one job updates both entries in UI. The issue persists even after reloading whole the BackWPup admin page. It must be faulty logic in server-side PHP code which I confirmed by looking at page source.

After making changes, diffing the exported JSON file with previous shows that changes are added to an entry in backwpup_jobs option that has no jobid property and contains only the changed properties. UI doesn’t reflect job name or other changed options.
Plugin Support Saransh
(@saranshwpm)

7 months, 2 weeks ago
Hi,

Thanks a lot for sharing such detailed feedback. I just want to be sure I’m understanding the first part correctly.

Please make sure that no two jobs are scheduled at the same time. Also, check the backup log to confirm if the database is actually being backed up. You can extract the backup and look for the .sql file (it’s a hidden file inside the archive). If the log confirms it but the file isn’t there, please share the job ID so I can look deeper.

About the other points you mentioned:
- Email sender: I tested using a different “From” address (not the admin one) and the emails were sent correctly from that defined address.
- Per-job email sender: Taking this as a feature request.
- Accessibility feedback: Noted, and really appreciate you mentioning this.
- Editing deactivated jobs: That’s expected at the moment, but you can activate, make edits, and then deactivate again.
- Multiple HTML IDs & modal behavior: Feedback taken and passed to the dev team.
If you still see the database mismatch after checking the points above, I would request you to reach out to us directly so we can understand it and work on it properly.

Best regards,
Thread Starter Andis
(@andydegroo)

7 months, 2 weeks ago
Hi,

No, there was only one job scheduled and executed on time.
I already had determined that the database wasn’t backed up by reading the log file and opening the archive. There are no .sql files in archive and here’s a snippet from beginning of log file:
```
[INFO] BackWPup 5.5.0; A project of WP Media
[INFO] WordPress 6.8.3 on https://[redacted]/
[INFO] Log Level: Debug
[INFO] BackWPup job: Weekly backup [NEW]; FILE+WPPLUGIN
[INFO] Runs with user: (0)
[INFO] Cron: 24 06 * * 2; Next: Otr, 14 Okt 2025 @ 06:24
[INFO] BackWPup job started from wp-cron
[INFO] PHP ver.: 8.3.6 (64bit); fpm-fcgi; Linux
[INFO] Maximum PHP script execution time is 600 seconds
[INFO] Script restart time is configured to 30 seconds
[INFO] MySQL ver.: 10.11.13-MariaDB-0ubuntu0.24.04.1
[INFO] Web Server: Apache
[INFO] curl ver.: 8.5.0; OpenSSL/3.0.13
[INFO] Temp folder is: /var/www/[redacted]/wp-content/uploads/backwpup/b00bee/temp/
[INFO] Logfile is: /var/www/[redacted]/wp-content/uploads/backwpup-b00bee-logs/backwpup_log_37324c_2025-10-07_06-24-21.html
[INFO] Backup file is: /var/www/[redacted]/wp-content/uploads/backwpup/b00bee/backups/2025-10-07_06-24-21_5H6THIHC04_FILE-WPPLUGIN.tar.gz
[07-Oct-2025 06:24:21] 1. Trying to make a list of folders to back up …
[07-Oct-2025 06:24:21] 459 folders to backup.
[07-Oct-2025 06:24:21] 1. Trying to generate a file with installed plugin names …
[07-Oct-2025 06:24:21] Added plugin list file "Psihologa-Konsultacijas.pluginlist.2025-10-07.txt" with 2,80 KB to backup file list.
[07-Oct-2025 06:24:21] 1. Trying to generate a manifest file …
[07-Oct-2025 06:24:21] Added manifest.json file with 4,26 KB to backup file list.
[07-Oct-2025 06:24:21] 1. Trying to create backup archive …
[07-Oct-2025 06:24:21] Compressing files as TarGz. Please be patient, this may take a moment.
[07-Oct-2025 06:24:21] Adding Extra files to Archive
...
```
If the log confirms it but the file isn’t there, please share the job ID so I can look deeper.

I’m not sure how job ID would help look deeper. It’s a number – "jobid": 4.

I’ve already filed an issue report on GitHub regarding the main issue.
I’ll try to get to the bottom of the main issue and update the GitHub issue when I have more time to dive into the BackWPup codebase.
At first glance, looks like it’s caused by differences between how the jobs array is accessed in amin UI view templates and other code paths.
Plugin Support Saransh
(@saranshwpm)

7 months, 1 week ago

Hello,

I have escalated this to our developers and am waiting for their feedback.

I appreciate you filing it on GitHub with the complete details.

Best Regards,

Plugin Support Saransh
(@saranshwpm)

7 months, 1 week ago

Hi @andydegroo,

After reviewing your GitHub report and JSON file, our dev team confirmed that the inconsistencies you noticed are related to the first backup job, which carries the flag “tempjob”: true. This is actually expected behavior in the current version and not a data corruption issue.

That said, we truly appreciate your thorough feedback and analysis. If you happen to find anything else related to this behavior, I’d suggest following up directly on the GitHub thread, so the devs can review it further in context.

Thanks again for your time and effort in helping improve BackWPup!

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

The topic ‘Multiple issues with version 5.5’ is closed to new replies.