8000 "The following assets could not be successfully checked out from revision control" when checking out already checked out assets · Issue #205 · ProjectBorealis/UEGitPlugin · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

"The following assets could not be successfully checked out from revision control" when checking out already checked out assets #205

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

Open
Rawalanche opened this issue Feb 12, 2025 · 2 comments

Comments

@Rawalanche
Copy link

This is a relatively minor issue but still could be improved I believe.

When selecting multiple assets and manually checking them out using the context menu, a warning message will pop up saying:
"The following assets could not be successfully checked out from revision control"

The wording of the message is a bit misleading as it indicates some error, while nothing serious has happened. It would be cool if this case can be detected and shown as info popup on the bottom right of the editor rather than blocking popup window. Something like "Skipped # already checked out items."

Steps to reproduce:

  1. In the Content Browser, navigate to any folder containing multiple assets
  2. Select one asset and check it out manually using context menu Revision Control->Check Out
  3. Select multiple assets including already checked out one
  4. Check out the entire selection again using context menu Revision Control->Check Out

Result: Once Check Out process is finished, a blocking warning window pops up with an ambiguous message "The following assets could not be successfully checked out from revision control"
Expected: In case of checking out already checked out assets, provide softer way of warning/informing user as it's not a critical issue

@mastercoms
Copy link
Member
mastercoms commented Feb 12, 2025

Hi, thanks for the write up. I agree that this is bad behavior for users to have to deal with. This is an engine issue, it's fixed in one of our engine patches. I'll give a link soon once I can find it.

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
0