It's all about the answers!

Ask a question

Source control in web ui - download question


Brian Thompson (41184) | asked Jun 18 '10, 3:58 p.m.
We are having a case where when, through the web ui, a user does an 'lock and download' on an xls file and the file is created on his laptop in a read-only state. In order to change the file he must copy it do a different file and edit that.

He has tried, in windows, to changing the file property to read-write but that seems to not have had any effect.

The person has a developer's license, is a member of the team area that owns the stream. His role allows all source control options.

He is later able to upload a change to the file.

Any ideas on why this is being created as a read-only file and how we can stop this behavior ? What are we missing ?

Thanks - Brian

One answer



permanent link
Geoffrey Clemm (29.4k23035) | answered Jun 18 '10, 5:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
By default, when a file is locked in the repository for download, it
should be loaded into the file system in a writable state. And once it
is in the file system, it is under file system control, not RTC control,
so if you can't make it writeable in the file system, then there is
something about your file system ACL that is forcing the read-only behavior.

So to track this down, we'd need to know what exact file system you are
using, and what the current ACL's are on the directory into which you
are loading the file.

Something else to try is:
- If you create a file in that directory using some other tool, is it
created writeable?
- If you download the file into a different directory, is it writeable?

Cheers,
Geoff

On 6/18/2010 4:07 PM, bltjazz wrote:
We are having a case where when, through the web ui, a user does an
'lock and download' on an xls file and the file is created on his
laptop in a read-only state. In order to change the file he must
copy it do a different file and edit that.

He has tried, in windows, to changing the file property to read-write
but that seems to not have had any effect.

The person has a developer's license, is a member of the team area
that owns the stream. His role allows all source control options.

He is later able to upload a change to the file.

Any ideas on why this is being created as a read-only file and how we
can stop this behavior ? What are we missing ?

Thanks - Brian

Your answer


Register or to post your answer.