ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-24 05:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

find/replace all universal error types links

Browse Source
This commit is contained in:
mDuo13
2018-05-11 12:15:00 -07:00
parent d062798429
commit e30fb03a48
52 changed files with 54 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/can_delete.md
View File

@@ -62,7 +62,7 @@ Use this command with no parameter to query the existing `can_delete` setting.
### Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `notEnabled` - Not enabled in configuration.
* `notReady` - Not ready to handle this request.
* `lgrNotFound` - Ledger not found.

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_cleaner.md
View File

@@ -64,5 +64,5 @@ The response follows the [standard format](#response-formatting), with a success
### Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `internal` if one the parameters is specified incorrectly. (This is a bug; the intended error code is `invalidParams`.)

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/ledger_request.md
View File

@@ -173,6 +173,6 @@ When the server is in the progress of fetching a ledger, but has not yet finishe
### Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing. This error can also occur if you specify a ledger index equal or higher than the current in-progress ledger.
* `lgrNotFound` - If the ledger is not yet available. This indicates that the server has started fetching the ledger, although it may fail if none of its connected peers have the requested ledger. (Previously, this error used the code `ledgerNotFound` instead.) [Updated in: rippled 0.30.1][New in: rippled 0.30.1]

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/log_level.md
View File

@@ -131,5 +131,5 @@ Otherwise, the request contains the following field:
### Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.

2
content/references/rippled-api/admin-rippled-methods/logging-and-data-management-methods/logrotate.md
View File

@@ -72,4 +72,4 @@ The response follows the [standard format](#response-formatting), with a success
### Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].