Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upgrade to 1.18 breaks cross-references #3626

Closed
vasyugan opened this issue Apr 26, 2021 · 4 comments
Closed

upgrade to 1.18 breaks cross-references #3626

vasyugan opened this issue Apr 26, 2021 · 4 comments

Comments

@vasyugan
Copy link

vasyugan commented Apr 26, 2021

I today tried to upgrade from 1.17 to the present version, which failed. So I opted to do a piecemeal upgrade instead, my Uwazi is now at version 1.20.0 and I see that the upgrade step from 1.17 to 1.18 has broken the handling of cross references.

e.g https://fpic.enip.eu/en/entity/ft228hi5pr5?ref=5c925ef073bb98001d833805 get me to an all-white screen while
the plain address of the document https://fpic.enip.eu/en/entity/ft228hi5pr5 works.
I am submitting this after noticing that the issue persists through version 1.20. Apologies if this is something that has already been fixed in subsequent releases.

@RafaPolit
Copy link
Member

This was a known issue and fixed in 1.27 (https://github.com/huridocs/uwazi/tree/1.27.0) on PR #3572 . Please update to the latest stable release (currently 1.28).

@vasyugan
Copy link
Author

This was a known issue and fixed in 1.27 (https://github.com/huridocs/uwazi/tree/1.27.0) on PR #3572 . Please update to the latest stable release (currently 1.28).

Yes, that was the first thing I tried, but that broke other stuff, that is, the yarn migrate && yarn reindex failed once again. Will have another look at this tomorrow or so.

@RafaPolit
Copy link
Member

In theory, you shouldn't need to move one version at a time. You could put 1.28 on top of 1.17 and migrations should happen correctly. Please, let us know of any findings / errors.

Thanks for the report.

@vasyugan
Copy link
Author

ok, closing this one, opening a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants