sharpetronics/jekyll-algolia
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix(record_too_big): Reformulate error message

Browse Source
This commit is contained in:
Pixelastic 2018-02-12 17:45:09 +01:00
parent 918524009d
commit e7d782b6bf
1 changed files with 5 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
lib/errors/record_too_big.txt
View File

@ -5,26 +5,23 @@ E: the {size_limit} size limit.
W:
W: The plugin will create one record for each element matching your
W: `nodes_to_index` value (currently set to "{nodes_to_index}"). Each record
W: should not weight more than {size_limit}. One of your records weights {size}
W: and has been rejected.
W: should not weight more than {size_limit}.
W: One of your records weights {size} and has been rejected.
W:
W: Here are more information about the rejected record:
W:
W: objectID: {object_id}
W: title: {object_title}
W: url: {object_url}
W:
W: Most probable keys causing the issue:
W: {probable_wrong_keys}
W:
W: Complete log of the record has been extracted to:
W: {record_log_path}
W:
W: Most probable keys causing the issue:
W: {object_hint}
W:
I: This issue can be caused by malformed HTML preventing the parser to correctly
I: grab the content of the nodes. Double check that the page actually renders
I: correctly with a regular `jekyll build`.
I:
I:
I: If you're having trouble solving this issue, feel free to file a bug on
I: GitHub, ideally with a link to a repository where we can reproduce the issue.
I: https://github.com/algolia/jekyll-algolia/issues