Fix service option name being set wrongly after adding a new variable. closes #208
This commit is contained in:
parent
2e33b9c4e4
commit
c1bf757623
2 changed files with 2 additions and 1 deletions
|
@ -16,6 +16,7 @@ This project follows [Semantic Versioning](http://semver.org) guidelines.
|
|||
* Fixes bug that would allow creating multiple subusers with the same email address.
|
||||
* Fixes bug where Sponge servers were improperly tagged as a spigot server in the daemon causing issues when booting or modifying configuration files.
|
||||
* Use transpiled ES6 -> ES5 filemanager code in browsers.
|
||||
* Fixes service option name displaying the name of a nwly added variable after the variable is added and until the page is refreshed. (see #208)
|
||||
|
||||
### Changed
|
||||
* Filemanager and EULA checking javascript is now written in pure ES6 code rather than as a blade-syntax template. This allows the use of babel to transpile into ES5 as a minified version.
|
||||
|
|
|
@ -231,7 +231,7 @@ class ServiceController extends Controller
|
|||
]));
|
||||
Alert::success('Successfully added new variable to this option.')->flash();
|
||||
|
||||
return redirect()->route('admin.services.option', [$service, $option])->withInput();
|
||||
return redirect()->route('admin.services.option', [$service, $option]);
|
||||
} catch (DisplayValidationException $ex) {
|
||||
return redirect()->route('admin.services.option.variable.new', [$service, $option])->withErrors(json_decode($ex->getMessage()))->withInput();
|
||||
} catch (DisplayException $ex) {
|
||||
|
|
Loading…
Reference in a new issue