A lot of errors are present on the explorer production server logs, for instance:
FTL stack trace ("~" means nesting-related): - Failed at: @googleSearchFrame This.searchCriterion [in template "base.ftl" at line 77, column 16] - Reached through: @block name="middle" [in template "base.ftl" at line 68, column 7] - Reached through: @extends src="base.ftl" [in template "file:/opt/apidoc/nuxeo-cap-8.2-tomcat/nxserver/web/root.war/modules/org.nuxeo.apidoc.webengine/skin/views/documentation.ftl" at line 2, column 1] ---- at freemarker.core.InvalidReferenceException.getInstance(InvalidReferenceException.java:131) at freemarker.core.UnifiedCall.accept(UnifiedCall.java:111)
Suspecting these pages should be more robust to avoid the error
Note: this error actually happens when managing documentation, see NXP-23830
- depends on
-
NXP-28839 Reorganize explorer packages, make service pluggable
- Resolved
-
NXP-28913 Improve Explorer webengine navigation and display
- Resolved
- is duplicated by
-
NXP-23830 "Manage documentation" links give a 500 error
- Resolved
- is related to
-
NXP-28995 Remove documentation management on explorer
- Resolved
- is required by
-
NXP-19497 Review Platform Explorer styles and UX
- Resolved