make the config global

src/app/Library/CrudPanel/Traits/Create.php

@@ -24,7 +24,7 @@ public function create($input)
     {
         [$directInputs, $relationInputs] = $this->splitInputIntoDirectAndRelations($input);
 
-        if ($this->get('create.useDatabaseTransactions')) {
+        if ($this->get('create.useDatabaseTransactions') ?? config('backpack.base.useDatabaseTransactions', false)) {
             return DB::transaction(fn () => $this->createModelAndRelations($directInputs, $relationInputs));
         }
 

src/app/Library/CrudPanel/Traits/Update.php

@@ -27,7 +27,7 @@ public function update($id, $input)
         $item = $this->model->findOrFail($id);
 
         [$directInputs, $relationInputs] = $this->splitInputIntoDirectAndRelations($input);
-        if ($this->get('update.useDatabaseTransactions')) {
+        if ($this->get('update.useDatabaseTransactions') ?? config('backpack.base.useDatabaseTransactions', false)) {
             return DB::transaction(fn () => $this->updateModelAndRelations($item, $directInputs, $relationInputs));
         }
 

src/config/backpack/base.php

@@ -163,6 +163,17 @@
     // You can rename this disk here. Default: root
     'root_disk_name' => 'root',
 
+    /*
+    |--------------------------------------------------------------------------
+    | Application
+    |--------------------------------------------------------------------------
+    */
+
+    // Should we use DB transactions when executing multiple queries? For example when creating an entry and it's relationships.
+    // By wrapping in a database transaction you ensure that either all queries went ok, or if some failed the whole process
+    // is rolled back and considered failed. This is a good setting for data integrity.
+    'useDatabaseTransactions' => false,
+
     /*
     |--------------------------------------------------------------------------
     | Backpack Token Username

src/config/backpack/operations/create.php

@@ -35,9 +35,6 @@
     // Should we warn a user before leaving the page with unsaved changes?
     'warnBeforeLeaving' => false,
 
-    // Should the create process (queries to insert the entry and it's relationships) be wrapped in a transaction?
-    'useDatabaseTransactions' => false,
-
     // Before saving the entry, how would you like the request to be stripped?
     //  - false - use Backpack's default (ONLY save inputs that have fields)
     //  - invokable class - custom stripping (the return should be an array with input names)

src/config/backpack/operations/update.php

@@ -35,9 +35,6 @@
     // Should we warn a user before leaving the page with unsaved changes?
     'warnBeforeLeaving' => false,
 
-    // Should the update process (queries to update the entry and it's relationships) be wrapped in a transaction?
-    'useDatabaseTransactions' => false,
-
     // Before saving the entry, how would you like the request to be stripped?
     //  - false - use Backpack's default (ONLY save inputs that have fields)
     //  - invokable class - custom stripping (the return should be an array with input names)