Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
moodle-tool_lifecycle
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
elc
moodle-tool_lifecycle
Commits
f7ed63d2
Commit
f7ed63d2
authored
3 years ago
by
Justus Dieckmann
Browse files
Options
Downloads
Patches
Plain Diff
Remove try catch in backup step, to let it show up on the error page
parent
884dc5d3
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
classes/local/manager/backup_manager.php
+41
-47
41 additions, 47 deletions
classes/local/manager/backup_manager.php
with
41 additions
and
47 deletions
classes/local/manager/backup_manager.php
+
41
−
47
View file @
f7ed63d2
...
...
@@ -45,7 +45,6 @@ class backup_manager {
*/
public
static
function
create_course_backup
(
$courseid
)
{
global
$CFG
,
$DB
;
try
{
$course
=
get_course
(
$courseid
);
$record
=
new
\stdClass
();
$record
->
courseid
=
$courseid
;
...
...
@@ -91,11 +90,6 @@ class backup_manager {
$DB
->
update_record
(
'tool_lifecycle_backups'
,
$record
,
true
);
return
true
;
}
catch
(
\moodle_exception
$e
)
{
debugging
(
'There was a problem during backup!'
);
debugging
(
$e
->
getMessage
());
return
false
;
}
}
/**
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment