re3gistry
re3gistry copied to clipboard
Re3gistry2 version 2.5.0 webapp problem
I installed Re3gistry2 version 2.5.0 and tried the application. Managed to install empty database version and the restapi is working. Now however has problem with webapp application.
I have the following configured in httpd:
DocumentRoot "/var/www/luettelopalvelu/public_html" ServerName dev.luettelopalvelu.fi
ProxyPass /re3gistry2 http://localhost:8080/re3gistry2 ProxyPassReverse /re3gistry2 http://localhost:8080/re3gistry2
ProxyPass /registry/rest http://localhost:8080/re3gistry2restapi/items/any ProxyPassReverse /registry/rest http://localhost:8080/re3gistry2restapi/items/any
Then in webapp i tried to configure in conf.js:
// The app's base URLs registryApp.domainURL = 'http://dev.luettelopalvelu.fi/registry'; registryApp.hostURL = 'http://dev.luettelopalvelu.fi/re3gistry2'; registryApp.searchURL = 'http://dev.luetteloplavelu.fi/registry/search'; registryApp.searchApiURL = 'http://dev.luettelopalvelu.fi/registry/searchapi'; registryApp.dataServiceURL = 'http://dev.luetteloplavelu.fi/registry/rest';
Is there still something i have missed to make the webapp work??
Dear @TeijoKal, I will bring this topic to the attention of our contractors, who probably missed it.
@campoxab and @arantzaetxebarria - My suggestion is to organise a technical meeting next week to unlock FI Re3gistry installation. And please assure to respond, classify and start working in the issues in a maximum 3 business days.
Dear @TeijoKal,
Apologies for the delayed response. We will start the analysis of the problem. We will keep you updated on our findings and we will try to provide an answer as soon as possible.
Regards
Dear @TeijoKal,
Thank you for bringing this issue up. We would like to ask you a couple of questions in order to understand the problem better.
- Can you check if the items in the database are generated with the URI you have provided? (In this case dev.luettelopalvelu.fi/registry).
- Can you attach a screenshot of what happens when you try to access the frontend of the application? Any error that shows up on console on the page load would be appreciated.
Thank you for your feedback.
Regards, Eneko
Here is the screen shot of the Admin start page (http://dev.luettelopalvelu.fi/re3gistry2).
And the restapi is working as it should be. For example https://dev.luettelopalvelu.fi/registry/rest?lang=fi&uri=http://dev.luettelopalvelu.fi/codelist/KiinteistonluovutuksenKohdistumisenLaji&format=xml
Returns the following:
https://dev.luettelopalvelu.fi/registry results the following
Dear @TeijoKal,
The URI seems to be fine, but we still need some more information about the issue.
- Can you attach some screenshots showing the console errors when accessing the frontend?
- Can you try to access a children item on the frontend? (We want to check if the issue is with the main page only or if it is present on the whole frontend).
Regards, Eneko
There is no error messages. Only it does not show the data.
Here is the screen shots of the example data entry.
Dear @TeijoKal, we will try and replicate the error that you're currently having in that installation process in order to solve it. For that, could you send us the database dump you used for the migration?
Thank you in advance, Unai.
Here is the dump of old version 1.3.1 database dumppi_2023_2.txt
Dear @TeijoKal,
Analysing the docx file with the screenshots you provided, specifically in this screenshot you indicate that ''There is no visible data in this Finnish subpage''.
What exactly is not visible? (we see the screenshot with data) Do you mean the table with the "available items"? Could you send us a screenshot of the part where you see that the data is not loaded? Best regards, Unai.
If after migration i open the Content the visible is the following:
The Finnish subpage:
And the English subpage
If i now choose Koodiluettelorekisteri in Finnish subpage the Available items stays empty
But if i choose the English subpage the Available items are all visible
Dear @TeijoKal,
Since this issue pertains to an older version of the app, we recommend installing the latest version. If you continue to experience this issue, please open a new ticket.
Best regards,
Irati