forked from wallabag/wallabag
If reload content failed, don’t update it
In case user wants a fresh version of the current one and the website isn’t available, don’t erase it with a boring message saying wallabag wasn’t able to refresh the content.
This commit is contained in:
@ -40,7 +40,7 @@ services:
|
||||
class: Graby\Graby
|
||||
arguments:
|
||||
-
|
||||
error_message: "wallabag can't retrieve contents for this article. Please report this issue to us."
|
||||
error_message: '%wallabag_core.fetching_error_message%'
|
||||
http_client:
|
||||
user_agents:
|
||||
'lifehacker.com': 'PHP/5.2'
|
||||
|
||||
Reference in New Issue
Block a user