There are currently no pages on your favorites list. You can add pages to this list by selecting Favorite from the Tools menu on the page you're viewing.
URLs that are presented on forwards and as links in returned documents oftentimes do not follow the configuration parameter web.application_root_url. Sometimes they contain the local adress of the backend webserver, sometimes even different values from the re³gistry database (eg. https://github.com/ec-jrc/re3gistry/issues/438#issuecomment-2186367203).
Comments
This needs to be resolved, as it hinders using the software and is a security threat.
Documentation doesn’t match with actual procedures, especially in installation and data migration
Front-end not documented
Comment
Template
#3 Template
reported by
BKG
Github Ticket
Description
Comment
Prioritization
Capacities?
Minutes:
The migration from 1.5 to 2.3 did not work. The Issue was reportet and confirmed. But for the time beeing there were no ressources to solve it.
Migration from 1.3 to 2.x did not work either.
The Templates from 1.3 and 1.5 are very different.
2.0-2.5 did not work The error was a 404.
The backend cannopt be installed. This issue was reported.
Spain has not yet shared the many work-arounds they have tried sofar.
As the issues are identified, there must be something done for them to work.
High on the priority list is to update the software to get the migration to workor but the ressourses are limited and the issue cannot be adressed at the moment.
The issues stated by spain seem to be similar to the German ones.
Wallon Region Belgium is on Version 1.3. They have not tried to update because they new of the many problems beforehand. So the update was not executed. In Belgium the Registry was not used much. The Idea was to use it more in the future. There is no testing environment to test the 2.x versions.
Jane Heller (DE) says it would be good to teest the different versions in different places. This way we can see if there are the same problems everywhere.
Since the software will be updated in summer it must work then - or at least something must be working by thenn.
from the 1.x versions to the 2.x versions.
Spains first approach was to migrate. The second was to deploy and populate manually.
We Germany will try to talk to Jordi about priorization.