diff options
| author | Thomas Steur <tsteur@users.noreply.github.com> | 2019-09-11 10:42:26 +0300 |
|---|---|---|
| committer | diosmosis <diosmosis@users.noreply.github.com> | 2019-09-11 10:42:26 +0300 |
| commit | e31ec88c07621cf52283490e5ffc7935308d00d5 (patch) | |
| tree | 86b52a7a21a4430cea823e45d4da35b397ef3968 /plugins/Live/lang | |
| parent | a1cba093124040a6ea1b9695af9de3293c229723 (diff) | |
Allow configuration of max execution time (#14858)
* allow configuration of max execution time
* trigger event when query time exceeded
* fix screenshot test
* added some tests and mention mariadb not supported
Diffstat (limited to 'plugins/Live/lang')
| -rw-r--r-- | plugins/Live/lang/en.json | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/plugins/Live/lang/en.json b/plugins/Live/lang/en.json index 62d85f3a0e..f346c7557e 100644 --- a/plugins/Live/lang/en.json +++ b/plugins/Live/lang/en.json @@ -36,6 +36,10 @@ "ToggleActions": "Toggle visibility of all actions", "TopVisitedPages": "Top visited pages", "VisitsLog": "Visits Log", + "QueryMaxExecutionTimeExceeded": "The query took too long to execute.", + "QueryMaxExecutionTimeExceededReasonDateRange": "This can happen if the selected date range is too large. Please try to select a smaller date range.", + "QueryMaxExecutionTimeExceededReasonSegment": "This can happen if the selected segment doesn't match any visit. Please try to check your selected segment.", + "QueryMaxExecutionTimeExceededReasonUnknown": "Please try again. If it happens repeatedly, please get in touch with the administrator or support.", "VisitorLog": "Visits Log", "VisitorLogDocumentation": "This table shows the latest visits within the selected date range. You can see when a visitor's last visit occurred by hovering over the date of a visit. %1$s If the date range includes today, you can see your visitors real time! %2$s The data displayed here is always live, regardless of whether and how often you are using the archiving cron job.", "VisitorLogNoDataMessagePurged": "Likely the data has been purged because the regular deletion of old raw data is enabled and the date for this report is more than %s days old. A super user can change this setting by going to Administration => Privacy.", |