I am (trying) to support a small team through an evaluation of Web Author as a collaboration/reviewing tool. We are using a trial floating license with a floating license server. Our files are stored in Bitbucket Server.

One of the writers had a problem installation--somehow the installation appeared to become corrupted and would not complete. Our IT department was able to resolve this. However, his Git connection appears to have become stuck on his cloned repository (i.e. his C:// file location). He does not have the Edit git repository button that I do. He used the log out function, but was only given the option to re-log into the cloned repository location. We did a stop/start of the server (using the Manage Web Author functionality), but again, he is only given the option to log into the cloned repository location. We also tried uninstalling and reinstalling Web Author (after IT resolved the initial issue), which again produced no change.

We are using the basic Git plugin because the Bitbucket plugin documentation appears to be specific to Bitbucket Cloud. I cannot find any equivalent to the Authorize User Key/Secret steps on Bitbucket Server. Googling suggests this has to do with OAuth 2.0 incompatibilities with Bitbucket Server.

This is time sensitive as we are trying to complete this evaluation before our trial runs out.

his Git connection appears to have become stuck on his cloned repository

We have identified a bug which allows a user to input invalid repository URLs such as "C://file/location". This bug will be fixed in the next version of Web Author.

He does not have the Edit git repository button that I do... We did a stop/start of the server... but again, he is only given the option to log into the cloned repository location.

The information about the last used repository is stored on the user's browser so restarting the Web Author server is not a solution.To fix this, the user needs to clear their browser's cache. An easy way to do this is to open the browser's developer console type this in and press enter:

Update in case anyone else runs into this issue and does a forum search: clearing the cache worked to reset my repository location when I tested it, but did not work for my writer when he tried it.

However, we realized that we'd made an error when we did the uninstall: we forgot about the uninstall instructions on the download page that said the configuration and log files would persist. We did another uninstall, and this time we deleted the installation folder completely.

This was the missing step. When we reinstalled, everything installed perfectly. We set the repository location correctly and so far, all seems to be working as expected.

The only confusing moment in this go round was that after setting the repository location, the window displayed a timeout error message instead of the expected user login/password screen. However, we selected the Login as different user button and were switched to the login/password screen. The writer input his login and password and connected successfully.