Document not uploading
HI all, I'm very new to Collaborator, but I was asked to quickly create a new Collaborator server a few weeks ago. I put it on a Rhel 8 VM, it's licensed and has been working normally for a few weeks. It is still using the internal database though, as I haven't had time to migrate it yet. Yesterday, I was notified that oone of the Devs couldn't upload a new document. He gets the "upload successful" message, but it doesn't actually get uploaded. I"ve tried the normal stuff, restarted the service, I rebooted the server, but the issue continues. I feel like it's something simple and to do with the internal database possibly, but I'm not sure what to try next to get the devs working again. Is anyone able to point me in the right direction to get this working? Edit: Not a diskspace issue. Users are accessing Collaborator through a web browser.This is on an air-gapped network and using LDAP in case it matters.... TIA
Collaborator Server operation with Java 17
The IT department has performed a Java update on the server, as it is necessary for the operation of other software on the server. Unfortunately, the operation of the CollabServer 14.4.14400 is now no longer possible. It would be nice to have a CollabServer installation that supports Java 17. Furthermore it would be desirable to know how many users are active and how many users are logged in but without activity for x minutes.
AWS Code Commit Support
Howdy, Please add Code Collaborator support for AWS Code Commit repository integrations to the web client. Example of this current functionality can be found here: https://support.smartbear.com/collaborator/docs/source-control/git.html https://support.smartbear.com/collaborator/docs/source-control/repo-hosting/index.html In the same way that Github, Bitbucket, and Azure can easily be integrated to the Collaborator, I would like for this process to also function with AWS Code Commit Repos. I may currently use Code Collab and AWS Code Commit via the client gui and local changes, but I would also like to have direct repo integration like the hosted repos do. Thanks.
Collaborator displays an HTTP 404 error
Hello, We've been using collaborator community 11.5.11500, and it works well. The collaborator server is upgrade to 14.3.14303 in 15th Jul, and now it shows 404 error. I'm not sure if the reason is that collaborator server is no longer community version anymore, and it has a 30-day limitation?😂 If so, can we back to the community version? I've tried the solution in this page:https://support.smartbear.com/collaborator/faq/collaborator-is-displaying-an-http-404-error/ It doesn't work. Thanks
Option to not re-open review after comment
Hello, is there a way (admin option?) to not re-open a review after it's been completed, if someone puts a comment after the fact? Often times, the reviewer has already approved a review, and some other observer will put a comment to ask a question or propose a future modification. It would be nice for the author to be notified that such a comment has been added to the review. But right now this action will put the review from "completed" to back in "inspection". Meaning everyone is notified and all the reviewers will have to approve the review again!! that is the most annoying flow ever. Is there a way to disable that feature? I haven't found the option in the documentation. thanks, JMT
