joseph_michaud
StaffJoined 14 years ago
User Profile
Staff
User Widgets
Contributions
Re: 'Failed to open result JSON file' error with PDF.GetTextContent and PDF.ConvertToText
Also, how do I open a support ticket: The link https://support.smartbear.com/testcomplete/message/ doesn't seem to work anymore? The chatbot should automatically show up now. Use the chatbot to "Create a case".65Views1like1CommentRe: Reference the Line of Another File in the Same Review
The syntax is a little different than the original request. From the docs: https://support.smartbear.com/collaborator/docs/working-with/concepts/chats.html#chat-new line NNN - will create link to desired range of the lines of the current file. lines N1:N2 - will create link to desired range of the lines of the current file. [file name]/L:NNN - will create link to line number of the another file. For example, test.txt/L:10 [file name]/L:N1-N2 - will create link to desired range of the lines of the another file. For example, test.txt/L:10-12 That first example should say: line NNN - will create link to desired line of the current file.11Views0likes0CommentsRe: Viewing the subscription(s) of others
I can't see any way to get a report or even see what subscriptions a user has defined. Suggest the feature request in the Feature Request forum: Collaborator Feature Requests | SmartBear Community Since you know which user is being added, as Administrator you could view that user's preferences and forcibly change their subscriptions through the WebUI.31Views1like0CommentsRe: Looking for information on SoapUI Open Source and Oracle Java Licensing.
If the bundled JRE is installed it will be found in the "jre" subdirectory of the SoapUI installation. Run "jre\bin\java -XshowSettings:properties -version" and look for the java.vendor string. SoapUI-5.7.0 had a java.vendor of "Oracle Corporation" SoapUI-5.7.1 had a java.vendor of "BellSoft"36Views0likes1CommentRe: Collaborator instability
XSRF relates to Cross-Site Request Forgery. (The code is just going to get a new token and retry the request.) This is not going to be the cause of your problem. Look in the collab.log for any errors or warnings. Create a case at https://support.smartbear.com/collaborator/message/ , provide a zip file with the logs and configuration files, and we can take a look: *.log *.vmoptions tomcat/logs/* tomcat/conf/*24Views0likes0CommentsRe: How to migrate Code Collaborator database from MySQL 5.6 on RedHat to MySQL 8.0 on Ubuntu?
When doing a migration consider that you are installing the Collaborator application moving the database moving content cache The easiest way to do this is to export a migration dump file on your source machine, install Collaborator on your destination machine, create a new empty database, and then import the migration dump file into the new empty database. To do that you must use the same version of Collaborator on both source and destination machines. When exporting the migration dump file, you will specify to perform a complete system dump. This copies the database into the zip file. You will also specify to include file contents. This copies the content cache into the zip file. (For those who haven't read it) see this article: https://support.smartbear.com/collaborator/docs/server/admin-tasks/backup.html#migrate There shouldn't be any problems going from MySQL v5 to MySQL v8 but see the article about setting up for MySQL: https://support.smartbear.com/collaborator/docs/server/install/db/mysql.html The dump file is DB-agnostic. It merely represents the tables in an XML format.31Views0likes0Comments