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

Dataset page stays on the url with "version=DRAFT" after the dataset is published #8548

Open
landreev opened this issue Mar 29, 2022 · 7 comments
Labels
SPA These changes are required for the Dataverse SPA UX/UI Input Needed Apply to issues involving UX or UI implications that need additional input

Comments

@landreev
Copy link
Contributor

... this results in "DRAFT version not found" warning message. Refreshing the page does not fix it, because "version=DRAFT" is in the url.
This is a sub-issue of #7653. Opening a "small chunk" issue for this specific problem, since it's the most annoying to the users; and should be the easiest to fix.

@landreev
Copy link
Contributor Author

Copy-and-pasting what I said in the parent issue:

Do we actually need that "DRAFT not found" message at all? Should we quietly redirect to the last published version instead, if there's no DRAFT? - That would be so much easier than messing with that redirect-on-unlock...

@sbarbosadataverse
Copy link

Yes, Leonid. I think it's confusing to have the DRAFT not found message.

@landreev
Copy link
Contributor Author

To clarify, when I said "Do we actually need that ... message at all?" above - I meant, not just in this scenario, but do we EVER need it, when somebody tries to go to a DRAFT and it does not exist.

@sbarbosadataverse
Copy link

I can't see how we would need that scenario? Maybe someone else may have a scenario in mind I can't think of...if they delete a DRAFT--what's the need?

@ofahimIQSS
Copy link
Contributor

I was able to reproduce this issue while I was testing for the 6.4 Release.

@cmbz cmbz added SPA These changes are required for the Dataverse SPA UX/UI Input Needed Apply to issues involving UX or UI implications that need additional input labels Oct 24, 2024
@cmbz
Copy link

cmbz commented Oct 24, 2024

2024/10/24: Should be implemented in the SPA as per conversation here. Added to the SPA Beta backlog for review there.

@pdurbin
Copy link
Member

pdurbin commented Oct 24, 2024

I already tested it and it works fine on the SPA. Some screenshots:

Screenshot 2024-10-24 at 10 50 34 AM
Screenshot 2024-10-24 at 10 50 43 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SPA These changes are required for the Dataverse SPA UX/UI Input Needed Apply to issues involving UX or UI implications that need additional input
Projects
Status: No status
Development

No branches or pull requests

5 participants