RY indexing fails on custom content that is not parseable

Description

See support case ES-28. The customer has various types of plugins and content types, Requirement Yogi is designed to attempt parsing custom types and abort if the content is not recognizable. However, there was one type of exception that wasn't caught and produced an error, preventing the content from being saved.

Environment

None

Observations

None

Activity

Show:
Adrien Ragot (Play SQL / Requirement Yogi)
September 6, 2019, 10:29 AM

Resolved in 2.2.2.

Resolved

Assignee

Unassigned

Reporter

Adrien Ragot (Play SQL / Requirement Yogi)

Labels

None

Participants

None

Fix versions

Priority

Matter of months