cessda / cessda.cvs.two

Apache License 2.0
0 stars 2 forks source link

CV export doesn't work for old versions #487

Closed cessda-bitbucket-importer closed 1 year ago

cessda-bitbucket-importer commented 1 year ago

Original report on BitBucket by Martin Šeleng (GitHub: pakoselo).


@‌dolinarm The export e.g. to pdf doesn’t work if the user selects previous versions of the vocabulary. If the user is watching e.g. this: https://vocabularies.cessda.eu/vocabulary/AnalysisUnit and later switch through the versions tab to e.g. the 2.0.0 version (I am not providing the direct link, because it will work as it will be opened in new window), the system tries to select the latest versions (in this case 2.1.2, but it should be 2.1.3) and not the 2.0.x and the export will be empty as a mix between vocabulary 2.0.x. and latest versions 2.1.y (can be seen also in the name of the pdf file). Another issue is that the checkboxes are randomly checked and also not every language version is included in the export. This errors shows as an outcome of resolving the #484.

cessda-bitbucket-importer commented 1 year ago

Original comment by Maja Dolinar.


This is still not resolved on staging. If I am on AnalysisUnit and want to export in pdf English version 2.1.0 I get an empty pdf file.

cessda-bitbucket-importer commented 1 year ago

Original comment by Maja Dolinar.


The same is for HTML export - empty file, whereas I cannot seem to download a SKOS version at all - nothing happens if I click download.

cessda-bitbucket-importer commented 1 year ago

Original comment by Martin Šeleng (GitHub: pakoselo).


@‌dolinarm @Joshocan When I checked the dev and staging environment, they probably don’t have the latest master branch deployed. Please look into this branch: https://github.com/cessda/cessda.cvs.two/tree/bugfix/487, which has this pull request: [link to pull request removed](link to pull request removed) and this PR is already merged into the master. These changes aren’t at the dev and staging environments.

cessda-bitbucket-importer commented 1 year ago

Original comment by Joshua Tetteh Ocansey (GitHub: Joshocan).


@pakoselo Deployment halted. It s fixed now. @‌dolinarm See if changes are effected on Dev and Staging

MajaDolinar commented 1 year ago

This is working now on staging. Closing the issue, ready for 3.0.1 release