Open dispiste opened 4 years ago
I attach a snapshot to illustrate the problem:
Hi, I've finally found the cause of the problem. This deployment was updated from version 3.6.x to 3.10.1. We use an external data directory and the 3.10.1 version provides updated metadata schemas which were not automatically copied to the external data directory. This was causing the errors.
I am not sure if it is an expected behaviour or if it should be considered a bug. As the metadata schemas are automatically copied to the data folder on the initial execution, I would expect they are copied again when they change. However, I can also see some good reasons to overwrite the existing schemas in the data dir.
That's how it works. If the schema exists in the data directory it is not automatically copied there again. If you want to use the latest changes you can customize the schema plugins directory and point it to the folder included inside webapps/geonetwork
using the property geonetwork.schema.dir
. For example: -Dgeonetwork.schema.dir=/app/tomcat/webapps/geonetwork/WEB-INF/data/config/schema_plugins
Describe the bug When I try to edit any metadata record in the metadata editor, I get an HTTP 400 error while loading geonetwork/srv/api/records/68690/editor?&currTab=default&starteditingsession=yes&_random=xxxx and the metadata editor never loads (only the top bar is displayed).
This problem happens in 2 different servers (having the same exact environment). However, it works correctly in my local Tomcat installation. We have not modified Geonetwork code.
I have seen some relevant errors in the log, related with the wro4j cache, but I have deleted the cache and the problem persists.
To Reproduce Steps to reproduce the behavior:
Expected behavior The metadata editor should be loaded, but it is not correctly loaded
Log file (extract)
Environment:
Additional context I have also traced this "_custom_style" log entry in Geonetwork souce code. I found:
So probably the error is related with {/root/gui/nodeId} variable not being properly initialized. I see the following Java classes are related with nodeId: