Support

Description of my issue:

Recently purchased the support for Joomla backup pro. I am trying to set the download id but it doesn't seem to be saved.

I tried the following things suggested in the previous tickets:
- installing backup pro twice
- uninstalling and installing fresh while preserving my settings via export
- setting the id from settings page -- this comes back with "Error Could not save data. Error:". Yes, no actual error message is displayed. Other components don't have a problem with saving any settings. I have easyblog, k2 and several jsn extensions installed alongside with Akeeba.

Akeeba doesn't seem to have a problem saving profiles (like my Dropbox login info etc), just the download id and other settings. Same thing happens when I just try to flip one of the settings, i.e. "Enable front-end and remote backup". When I click Save (or Save and Close) same error appears.

Nothing in the php error log, nothing in Joomla logs.

By the way, manual backups run just fine, including post-processing to Dropbox API V2 (have not tried restoring nor scheduled backups yet).

Please confirm that the PHP module mbstrig is installed and enabled. This module is required by Joomla!, you can't install the current version without it. We are seeing quite a few sites that were installed before the module was required and the need is just now becoming known. We are using those functions in saving the settings.

Yes, confirmed via phpinfo().
libmbfl version 1.3.2

Adding a screenshot of mbstring settings from phpinfo().

Well, I hate to report this but the problem went away.

All I did on the host was to trigger a backup from the command line. The backup completed successfully. Some time later, I wanted to see if the problem leaves any traces in the "administrator/components/com_akeeba/backup/akeeba.cli.log" logs, so I had one on tail -f and tried updating the download id again from the options, and it worked this time.

My suspicion is that either the double install or reinstall actually helped but one backup run was necessary to flush some settings away.

Please let me know if you wanted to capture any logs or settings from my system for future debugging.

The backup logs really wouldn't tell us anything about this problem. My guess is that you fixed it with the double install or uninstall/reinstall but the old code was stuck in a cache. When the cache expired, everything magically was fixed. I'm glad it is working for you, if you have any further problems, please let us know.