mxgross / easybackupbundle Goto Github PK

Hi there,

I am using the Docker containers as provided by Tobybatch. I'm hoping to use Easy Backup but I'm having some trouble with the plugin and wondered if you may have had any experience with this use case.

When I tried to run a backup, I received the following error:

NOTICE: PHP message: request.CRITICAL: Uncaught PHP Exception Symfony\Component\Filesystem\Exception\IOException: "Failed to touch "/opt/kimai/var/easy_backup/easybackup.log"." at /opt/kimai/vendor/symfony/filesystem/Filesystem.php line 151 {"exception":"[object] (Symfony\\Component\\Filesystem\\Exception\\IOException(code: 0): Failed to touch \"/opt/kimai/var/easy_backup/easybackup.log\". at /opt/kimai/vendor/symfony/filesystem/Filesystem.php:151)"} []

When I went to that directory /opt/kimai/var/easy_backup it wasn't there, so I created it. Is this expected behavior?

I was able to run a backup after this, however the SQL database did not backup successfully.

[2021-11-13 00:03:23] INFO: Start database backup.
[2021-11-13 00:03:23] INFO: Used database: 'mysql'.
[2021-11-13 00:03:23] ERROR: mysqldump: 'Usage: mysqldump [OPTIONS] database [tables]'.
[2021-11-13 00:03:23] ERROR: mysqldump: 'OR     mysqldump [OPTIONS] --databases DB1 [DB2 DB3...]'.
[2021-11-13 00:03:23] ERROR: mysqldump: 'OR     mysqldump [OPTIONS] --all-databases'.
[2021-11-13 00:03:23] ERROR: mysqldump: 'OR     mysqldump [OPTIONS] --system=[SYSTEMOPTIONS]]'

My SQL server URL is perhaps not what the plugin is expecting due to it being containerized:

DATABASE_URL=mysql://user:password@sqldb/kimai

Can I format the command(s) in such a way to make the connection across the containers? Which .env file is read from, the one in /opt/kimai/.env?

I also have an exclamation for git rev-parse HEAD, though I do have git installed.

Finally, thank you for the plugin.

The user should be able to define a cron job, so that e.g. every night a backup is created.

(Not only) FTP users will not have the bin/console command and likely not have git as well.
Deployment process does not involve GIT in every environment.

You can pull the Kimai version via PHP constants directly:

$version = \App\Constants::VERSION . ' ' . \App\Constants::STATUS;

And I'd remove the "git rev-parse HEAD" call completely or at least make sure to catch possible exceptions and write an empty string if it couldn't be fetched.

I have Kimai 2.0.22 setup and running fine (no added data yet), I added EasyBackup and the screen loads and runs backup without error, but nothing shows up in the list (json file is empty and the nothing else in the backup folder).

Status check is all greeen.

Log:
[2023-05-21 01:59:00] INFO: --- S T A R T C R E A T I N G B A C K U P ---
[2023-05-21 01:59:00] INFO: Creating backup dir '/home/site/time2.site.com/kimai/var/easy_backup/2023-05-21_015900/'.
[2023-05-21 01:59:00] INFO: Creating manifest file '/home/site/time2.site.com/kimai/var/easy_backup/2023-05-21_015900/manifest.json'.

No PHP errors in error log.

Hi,

I posted an issue over at the kimai repo - maybe you find the time to have a look :-)

tobybatch/kimai2#443

Thanks in advance

Axel

As I use a Synology NAS for Kimai the path to mysqldump is:
/volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysqldump

instead of the default setting:
/usr/bin/mysqldump

When I changed the path in EasyBackup configurations (Kimai UI) I finally was able to backup the mysql database.
The files and paths to backup didnt change, so the following files/folders should be backed up too:

• .env
• config/packages/local.yaml
• var/data/
• var/plugins/
• var/invoices/
• templates/invoice/
• var/export/
• templates/export/

Unfortunately now the created zip-file does only contain following files:

• templates (folder with subfolders)
• database_dump.sql
• manifest.json

Why cant I backup all the necessary files anymore?
Kimai is a great Software, but it would be useless for me, if i cant backup my files reliably.
Can anybody help me?

Currently the flash messages are hardcoded in english. They should be made translatable and be available at least in english and german.

Add your invoices directory to $arrayOfPathsToBackup in Controller/EasyBackupController.php to have them backed up automatically.

Hi there!

Thank you very much for your effort you put in to this great plugin!
Maybe you could point me in the right direction to solve my problem. I am having difficulties trying to get EasyBackup running. When I hit Create Backup it throws a error ('Something is wrong'), but the status checks are all green ticked.
I was thinking about setting the right permissions, but as it is a shared hosting environment (ionos) I don't have a sudo user.

Here is my status check and log.

[2021-11-09 10:18:05] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []
[2021-11-09 10:18:03] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Filesystem\Exception\IOException: "Failed to touch "/homepages/44/d706901053/htdocs/kimai2/var/easy_backup/easybackup.log"." at /homepages/44/d706901053/htdocs/kimai2/vendor/symfony/filesystem/Filesystem.php line 151 {"exception":"[object] (Symfony\\Component\\Filesystem\\Exception\\IOException(code: 0): Failed to touch \"/homepages/44/d706901053/htdocs/kimai2/var/easy_backup/easybackup.log\". at /homepages/44/d706901053/htdocs/kimai2/vendor/symfony/filesystem/Filesystem.php:151)"} []
[2021-11-09 10:18:03] security.DEBUG: Guard authenticator does not support the request. {"firewall_key":"secured_area","authenticator":"App\\Security\\TokenAuthenticator"} []
[2021-11-09 10:18:03] security.DEBUG: Checking support on guard authenticator. {"firewall_key":"secured_area","authenticator":"App\\Security\\TokenAuthenticator"} []
[2021-11-09 10:18:03] security.DEBUG: Checking for guard authentication credentials. {"firewall_key":"secured_area","authenticators":1} []
[2021-11-09 10:18:03] security.DEBUG: User was reloaded from a user provider. {"provider":"App\\Security\\KimaiUserProvider","username":"sampleUser"} []
[2021-11-09 10:18:03] security.DEBUG: Read existing security token from the session. {"key":"_security_secured_area","token_class":"Symfony\\Component\\Security\\Core\\Authentication\\Token\\UsernamePasswordToken"} []
[2021-11-09 10:18:03] request.INFO: Matched route "create_backup". {"route":"create_backup","route_parameters":{"_route":"create_backup","_controller":"KimaiPlugin\\EasyBackupBundle\\Controller\\EasyBackupController::createBackupAction","_locale":"en"},"request_uri":"https://kimai.website.de/en/admin/easy-backup/create_backup","method":"GET"} []

View status checks have every entry in the list displaced as correct. However, when tried to create a backup this page with a critical error pops up. The backup is attempted to be done through the super admin account

Hi,

I host my Kimai on an Synology NAS. The paths are different compared to a usual linux server.
My Synology has it installed at:
/usr/local/mariadb10/bin

When I recently wanted to do a backup, the database is not included in the backup file anymore.
The log says:
"[2022-05-22 22:21:38] ERROR: mysqldump: 'sh: /usr/bin/mysqldump: No such file or directory'."

However, a long time ago, I changed the default mysqldump command in the Kimai settings to:
"/usr/local/mariadb10/bin/mysqldump --user={user} --password={password} --host={host} --port={port} --single-transaction --force {database}"

For some reason, the setting seems to be ignored? In January 2022, it worked fine.
I tried to switch back to PHP 7.4 (instead of PHP 8.0), but it did not help.

I created a issue for your test result @biologghe

FYI I did a restore attempt but bumped into this error:
[2020-12-27 15:48:00] request.CRITICAL: Uncaught PHP Exception
Symfony\Component\Filesystem\Exception\IOException: "Cannot rename
"/home/pi/kimai2/var/easy_backup/2020-12-27_151908/.env" to
"/home/pi/kimai2/.env"." at
/home/pi/kimai2/vendor/symfony/filesystem/Filesystem.php line 290
{"exception":"[object]
(Symfony\Component\Filesystem\Exception\IOException(code: 0): Cannot
rename "/home/pi/kimai2/var/easy_backup/2020-12-27_151908/.env" to
"/home/pi/kimai2/.env". at
/home/pi/kimai2/vendor/symfony/filesystem/Filesystem.php:290)"} []

I had changed the permissions of .env to g+rw

So we can communicate here, I closed the other issue because it was another topic which was solved.

I did not get this overwrite/rename error, so I think my permissions are different. At least I should catch these errors, log them and inform the user about it.

Best regards,
Max

Can you help explaining this message in the status checks:

fatal: detected dubious ownership in repository at '/var/www/kimai/var/plugins/EasyBackupBundle' To add an exception for this directory, call: git config --global --add safe.directory /var/www/kimai/var/plugins/EasyBackupBundle

This is the directory:

drwxrwxr-x 11 root www-data   4096 May 26 10:53 ./
drwxrwxr-x  4 root www-data   4096 May 26 10:55 ../
drwxrwxr-x  2 root www-data   4096 May 26 10:53 Command/
-rwxrwxr-x  1 root www-data   1827 May 26 10:53 composer.json*
drwxrwxr-x  2 root www-data   4096 May 26 10:53 Configuration/
drwxrwxr-x  2 root www-data   4096 May 26 10:53 Controller/
drwxrwxr-x  2 root www-data   4096 May 26 10:53 DependencyInjection/
-rwxrwxr-x  1 root www-data    448 May 26 10:53 EasyBackupBundle.php*
...

So owner = root and group = www-data.
After running chown -R www-data /var/www/kimai/var/plugins/EasyBackupBundle the error went away.
Why is the owner root dubious?

When try to use easybackup first time on a quite fresh KIMAI2 installation the application fails.
I can use kimai2 normal but when try to use the easyBackup the server throws an error 500.

Logdump below:
[2020-01-07 09:42:11] request.INFO: Matched route "easy_backup". {"route":"easy_backup","route_parameters":{"_route":"easy_backup","_controller":"KimaiPlugin\EasyBackupBundle\Controller\EasyBackupController::indexAction","_locale":"en"},"request_uri":"http://localhost:8080/en/admin/easy-backup","method":"GET"} []
[2020-01-07 09:42:11] security.DEBUG: Read existing security token from the session. {"key":"_security_secured_area","token_class":"Symfony\Component\Security\Core\Authentication\Token\RememberMeToken"} []
[2020-01-07 09:42:11] php.INFO: User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, {"exception":"[object] (ErrorException(code: 0): User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, at /var/www/kimai2/vendor/symfony/security-core/Authentication/Token/AbstractToken.php:325)"} []
[2020-01-07 09:42:11] php.INFO: User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, {"exception":"[object] (ErrorException(code: 0): User Deprecated: Checking for the AdvancedUserInterface in "Symfony\Component\Security\Core\Authentication\Token\AbstractToken::hasUserChanged()" is deprecated since Symfony 4.1 and support for it will be removed in 5.0. Implement the Symfony\Component\Security\Core\User\EquatableInterface to check if the user has been changed, at /var/www/kimai2/vendor/symfony/security-core/Authentication/Token/AbstractToken.php:325)"} []
[2020-01-07 09:42:11] security.DEBUG: User was reloaded from a user provider. {"provider":"Symfony\Component\Security\Core\User\ChainUserProvider","username":"rdc"} []
[2020-01-07 09:42:11] security.DEBUG: Checking for guard authentication credentials. {"firewall_key":"secured_area","authenticators":1} []
[2020-01-07 09:42:11] security.DEBUG: Checking support on guard authenticator. {"firewall_key":"secured_area","authenticator":"App\Security\TokenAuthenticator"} []
[2020-01-07 09:42:11] security.DEBUG: Guard authenticator does not support the request. {"firewall_key":"secured_area","authenticator":"App\Security\TokenAuthenticator"} []
[2020-01-07 09:42:11] php.CRITICAL: Class 'Symfony\Component\Process\Process' not found {"exception":"[object] (Symfony\Component\Debug\Exception\FatalThrowableError(code: 0): Class 'Symfony\Component\Process\Process' not found at /var/www/kimai2/var/plugins/EasyBackupBundle/Controller/EasyBackupController.php:333)"} []
[2020-01-07 09:42:20] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\ClassNotFoundException: "Attempted to load class "Process" from namespace "Symfony\Component\Process". Did you forget a "use" statement for another namespace?" at /var/www/kimai2/var/plugins/EasyBackupBundle/Controller/EasyBackupController.php line 333 {"exception":"[object] (Symfony\Component\Debug\Exception\ClassNotFoundException(code: 0): Attempted to load class "Process" from namespace "Symfony\Component\Process".\nDid you forget a "use" statement for another namespace? at /var/www/kimai2/var/plugins/EasyBackupBundle/Controller/EasyBackupController.php:333)"} []
[2020-01-07 09:42:20] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []

In my hands (Firefox Browser on Windows 10 Enterprise and Kimai 1.12 stable running on Pi) the paths entered in the settings 'Files and paths to backup) are not all taken into account. Only when content of the form field is deleted and saved (= defaults are taken) all files and folders are taken into account. As the default values are filled in automatically, you need to remember to delete the content every time you make changes to other settings.
Looks like a PHP_EOL issue (https://eidson.info/post/php_eol_is_broken)

Hi,
I have installed easybackup as described here
In the 'View status checks' overview I get this error

Path '/var/www/kimai2/var' readable 	
Path '/var/www/kimai2/var' writable 	
Backup directory '/var/www/kimai2/NOT SET' exists 	
PHP extension 'zip' loaded 	
Kimai version 	1.26.0 stable
Database 	mysql
NOT --version 	sh: 1: NOT: not found
NOT --version 	sh: 1: NOT: not found 

Any idea why?

Hello,

I get the following error when I try to load the plugin.

In PluginMetadata.php line 59:

Bundle "EasyBackupBundle" defines an invalid Kimai minimum version in extra.kimai.require. P
lease provide an integer as in Constants::VERSION_ID.

my PHP build is:

PHP 8.1.2-1ubuntu2.10 (cli) (built: Jan 16 2023 15:19:49) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.2, Copyright (c) Zend Technologies
with Zend OPcache v8.1.2-1ubuntu2.10, Copyright (c), by Zend Technologies

Thank you and regards,
Joseph

EasyBackup seems to work, but showing this message:

git 	fatal: detected dubious ownership in repository at '/var/www/kimai/var/plugins/EasyBackupBundle' To add an exception for this directory, call: git config --global --add safe.directory /var/www/kimai/var/plugins/EasyBackupBundle 

I've tried the recommendation written there, but it doesn't solve the issue. So what ownership is working for the directory? What is the reason for the error message, since I followed the instructions step by step?

I'm posting here based on Kevin's recommendation.
I'm on the last release, 2.14.0 as you see in the screenshot.

Some effort is also in invoice templates and customized objects. It will be nice to get them backed up too.

Thanks for the Plug-In!
Nevertheless backups have no sense if the restore of them is not rock solid. It would be great to have some restore capabilities or at least a guidance how to restore what is in the backup.

Hi there!

Thank you very much for your effort you put in to this great plugin!
Maybe you could point me in the right direction (again) to solve my problem?
Kimai is doing fine, but the mysqldump in the backup routine is not working in my configuration.

The mysqldump via ssh is working fine. Also it is working fine, if I replace the password wildcard --password={password} in the user interface with the actual password. I know it is not the best to do this, but for testing...
I do have a pasword that is URL-encoded (in the DATABASE_URL). Could this cause the error?

If I leave the standard command in the ui it throws this error:
ERROR: mysqldump: 'mysqldump: Got error: 1045: "Access denied for user 'user1234'@'subdomain.hosting.de' (using password: YES)" when trying to connect'.

Best regards
Lukas

Due to bigger changes in Kimai >=2.0.0 this plugin must be converted as well.

Hi,

Please can somebody help in my case,
I have installed this plugin without any error, but when I try to make a backup I got the following error:
Attempted to call an undefined method named "flashError" of class "KimaiPlugin\EasyBackupBundle\Service\EasyBackupService".

Please somebody can help me?

Best Regards,
GáborS

After fix #11 :-) and Idea.

Can you include the
templates/
var/invoice/

dirs in the backup. Thats where the maintaint documents relies :-)

/Martin
PS: excelent fast work with isuue #11 :-) !!

Current version of plugin and Kimai2.

The plugin was pulled from git without any modifications or configuration:

Running it results in

[2022-10-03 13:20:52] INFO: Start database backup.
[2022-10-03 13:20:52] INFO: Used database: 'mysql'.
[2022-10-03 13:20:52] ERROR: Usage: mysqldump [OPTIONS] database [tables]
OR     mysqldump [OPTIONS] --databases DB1 [DB2 DB3...]
OR     mysqldump [OPTIONS] --all-databases
OR     mysqldump [OPTIONS] --system=[SYSTEMOPTIONS]]
For more options, use mysqldump --help
[2022-10-03 13:20:52] INFO: Start zipping '/opt/kimai/var/easy_backup/2022-10-03_132052/' to '/opt/kimai/var/easy_backup/2022-10-03_132052.zip'.

so it looks like the correct parameters are not found in the Kimai configuration...

Is there a way to automatically trigger an backup (e.g. via CronJob, or via API-Call?
That would be awesome.

Which license do you plan to use?
You haven't indicated it on the repos README, the phpdocs and there is no LICENSE file as well.

I had to change the path to mysqldump to include --force and -h 127.0.0.1 to make it run fine.

Hi,
The dump as produced on an Ubuntu 18 server contained the line
"mysqldump: [Warning] Using a password on the command line interface can be insecure."
At the top of the file, which means that when you try to restore it, it fails with a format error. Removing the line makes restoring the database possible.

Suggestion: An automated restore from the web interface would be useful. Or at least, instructions on how to extract and restore a database from a dump.

I have Kimai v2.0.23 running on docker and when I tried to install the the EasyBackupBundle plugin, It is does not show up in the kimai.
The installation steps I took:

1. Created the "EasyBackupBundle" directory in the plugins directory and move all the downloaded files into it. Contains the EasyBackupBundle.php under the EasyBackupBundle Directory.
2. Set the permissions: docker exec --user root kimai chown -R www-data:www-data /opt/kimai/var
3. Reloaded the cache: docker exec -ti kimai /opt/kimai/bin/console kimai:reload --env=prod
4. Set the permissions again (just incase): docker exec --user root kimai chown -R www-data:www-data /opt/kimai/var

When I logged back into kimai on my browser, I do not see the easybackup option in the menu and the plugins page shows no plugins installed.
The logs on the doctor menu shows the following two entries related to easybackup:

[2023-05-23T10:51:07.826782+00:00] deprecation.INFO: User Deprecated: Since symfony/console 6.1: Relying on the static property "$defaultDescription" for setting a command description is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "KimaiPlugin\EasyBackupBundle\Command\EasyBackupBackupCommand" class instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/console 6.1: Relying on the static property \"$defaultDescription\" for setting a command description is deprecated. Add the \"Symfony\\Component\\Console\\Attribute\\AsCommand\" attribute to the \"KimaiPlugin\\EasyBackupBundle\\Command\\EasyBackupBackupCommand\" class instead. at /opt/kimai/vendor/symfony/console/Command/Command.php:104)"} []
[2023-05-23T10:51:07.825446+00:00] deprecation.INFO: User Deprecated: Since symfony/console 6.1: Relying on the static property "$defaultName" for setting a command name is deprecated. Add the "Symfony\Component\Console\Attribute\AsCommand" attribute to the "KimaiPlugin\EasyBackupBundle\Command\EasyBackupBackupCommand" class instead. {"exception":"[object] (ErrorException(code: 0): User Deprecated: Since symfony/console 6.1: Relying on the static property \"$defaultName\" for setting a command name is deprecated. Add the \"Symfony\\Component\\Console\\Attribute\\AsCommand\" attribute to the \"KimaiPlugin\\EasyBackupBundle\\Command\\EasyBackupBackupCommand\" class instead. at /opt/kimai/vendor/symfony/console/Command/Command.php:85)"} []

Also, I tried with reloading the cache with the following steps and did not work:

docker exec -ti kimai /opt/kimai/bin/console cache:clear --env=prod
docker exec -ti kimai /opt/kimai/bin/console cache:warmup --env=prod

Hi,

i host my kimai on an synology NAS. There are the paths different to an usual linux server.
My Synology has it installed here:
/volume1/@appstore/MariaDB10/usr/local/mariadb10/bin

Can you please add an possibility to change the path to the bins or check it via the server variables?

thanks
Andreas

my first wish: add some topics to your repo, so its easier to find

example screenshot from the CustomCSSBundle:

When changing the setting mysqldump path it is saved and correctly loaded in the settings page. But in the EasybackupController the requested setting always returns its default value.

I followed the instructions of EasyBackupBundle, but an error occurs after executing the command "cache:clear".

Steps:

cd /var/www/kimai2/var/plugins/
git clone https://github.com/mxgross/EasyBackupBundle.git

cd var/www/kimai2/
bin/console cache:clear

Error Message:

_In FileLoader.php line 208:

Expected to find class "KimaiPlugin\EasyBackupBundle\Controller\EasyBackupController" in file "/var/www/kimai2/var/plugins/E
asyBackupBundle/Controller/EasyBackupController.php" while importing services from resource "../../*", but it was not found!
Check the namespace prefix used with the resource.

Used software:
Kimai version: 1.8;
Ubuntu Desktop
nginx
php 7.2

Currently git status will report var/easy_backup and all backups as unknown/new files.

This could be fixed by creating a .gitignore file with the contents:

*

when creating the var/easy_backup/ directory.

Just installed the nice Easy Backup and get this error.
fatal: detected dubious ownership in repository at '/var/www/kimai/var/plugins/EasyBackupBundle' To add an exception for this directory, call: git config --global --add safe.directory /var/www/kimai/var/plugins/EasyBackupBundle
Did what it said, but with no positive result. No change!
But even when I'm getting this message, Easy Backup works perfect. Very fast it generated and no error in the log:

[2024-02-13 22:48:09] INFO: --- S T A R T C R E A T I N G B A C K U P ---
...
[2024-02-13 22:48:09] WARNING: No output received from the command.
[2024-02-13 22:48:09] WARNING: Command failed with exit code: 128
...
[2024-02-13 22:48:09] WARNING: Path '/var/www/kimai/config/packages/local.yaml' is not existing or not accessable
…
[2024-02-13 22:48:09] WARNING: Path '/var/www/kimai/var/invoices/' is not existing or not accessable.
...
[2024-02-13 22:48:09] WARNING: Path '/var/www/kimai/var/export/' is not existing or not accessable.
...
[2024-02-13 22:48:09] INFO: --- F I N I S H E D C R E A T I N G B A C K U P ---
So, what is the reason for that issue?

Undefined variable: pluginBackupDir at

Needs to be replaced with:

$sqlDumpName = $this->backupDirectory . self::SQL_DUMP_FILENAME;

Hello,

The password from DATABASE_URL can contain %40 to allow a @ character in the password. This works well in Kimai, but not in EasyBackup.

How about replacing this

            $mysqlDumpCmd = str_replace('{password}', $dbPwd, $mysqlDumpCmd);

by

            $mysqlDumpCmd = str_replace('{password}', urldecode($dbPwd), $mysqlDumpCmd);

Hello, is it possible to run this plugin in docker?
I am getting the following errors:
sh: /usr/bin/mysqldump: not found
sh: /usr/bin/mysql: not found

hi there..
I have updated and gone start to use your kimai 2 for time report and iam now trying to fix Easy Backup plugin first befor i go live. But i cant get it to work :-( When i press the backup butten it only go to login screen and say something whent wrong.
Is this plugin not working with the new update or do i need to set someting up?

Hi,

Just installed the branch mentioned in subject and the plugin functions correctly.
However, when clicking on "Settings" under "System" I get a 500 "Something is wrong" error.
In Doctor > Logs I find below error:

[2023-04-06T10:22:42.727078+02:00] request.CRITICAL: Uncaught PHP Exception Symfony\Component\ErrorHandler\Error\UndefinedMethodError: "Attempted to call an undefined method named "setSection" of class "App\Form\Model\SystemConfiguration". Did you mean to call "getSection"?" at /var/www/kimai2/var/plugins/EasyBackupBundle/EventSubscriber/SystemConfigurationSubscriber.php line 35 {"exception":"[object] (Symfony\\Component\\ErrorHandler\\Error\\UndefinedMethodError(code: 0): Attempted to call an undefined method named \"setSection\" of class \"App\\Form\\Model\\SystemConfiguration\".\nDid you mean to call \"getSection\"? at /var/www/kimai2/var/plugins/EasyBackupBundle/EventSubscriber/SystemConfigurationSubscriber.php:35)"} [] [2023-04-06T10:22:42.726062+02:00] php.CRITICAL: Uncaught Error: Call to undefined method App\Form\Model\SystemConfiguration::setSection() {"exception":"[object] (Error(code: 0): Call to undefined method App\\Form\\Model\\SystemConfiguration::setSection() at /var/www/kimai2/var/plugins/EasyBackupBundle/EventSubscriber/SystemConfigurationSubscriber.php:35)"} [] [2023-04-06T10:22:42.703555+02:00] request.INFO: Matched route "system_configuration". {"route":"system_configuration","route_parameters":{"_route":"system_configuration","_controller":"App\\Controller\\SystemConfigurationController::indexAction","_locale":"en_US"},"request_uri":"https://kimai.example.com/en_US/admin/system-config/","method":"GET"} []

Thanks for your software and hopefully this helps getting your plugin released for the 2.0 series of Kimai.

best,
peter

Hello 👋

I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@ixSly) has found a potential issue, which I would be eager to share with you.

Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.

Looking forward to hearing from you 👍

(cc @huntr-helper)

When creating backup, I get the following error:

P.S. Kimai deploy in docker

Respectfully,
Jamshid Tursunov

Hi,

I get the following error when creating a backup:
ERROR: sh: -c: line 0: syntax error near unexpected token ('`

I suspect this to happen due to the "(" character in the database password.
Can anyone confirm/fix this?

Thx

The failure handling can be optimized. And mariaDB should be tested.

See https://stackoverflow.com/questions/11679275/mysqldump-via-php

Backup is working perfect, but how can i restore it "with one click"?