nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ForceDelete

keith999

In TeamSite 5.5, the result of submit log sometimes shows an file as "forcedelete". Does anybody know what it is. What is the difference from delete?

Find more posts tagged with

Comments

abackenr

when you do a submit from your workarea, you can choose to overwrite in case of conflicts. whenever you overwrite, it's considered a forced submit. this isn't a bad thing, it just means you haven't merged.

for a concrete example:

you are sumbmitting file A, which in your workarea has version 5+ (+ meaning it is modified in your workarea). STAGING contains version 6, since someone has submitted modifications since the last time you did a get latest. if you merge before submitting, you submit will not be forced. if you do an overwrite submit, your submit will be forced.

generally, deletetions are forced submits, especially in the case of deleting directories, since directory versions are not completely implemented in TeamSite.

ariel

staff engineer @ interwoven

Adam Stoller

(emphasis added)
generally, deletetions are forced submits, especially in the case of deleting directories, since directory versions are not completely implemented in TeamSite.
Is this an indication that we may [soon] be getting versioned directories - or do you mean that the only aspect of versioning is (and will remain) that the directory is either there or not there based on the contents of [for example] an edition?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

abackenr

no commitment here, but there is talk of more fine grained directory versioning coming out in TeamSite soon (i know the server group is looking at it).

not quite sure about the second part of your question.

staff engineer @ interwoven

Adam Stoller

There wasn't really a second part of the question - it was just an alternative interpretation of what you had previously written.

Hmm - "more fine grainined directory versioning" - cool - it would be nice (though obviously not required) if someone could expand on this a bit more ... I'd be very interested in figuring out the ramifications and how to best take advantage of such functionality --- but that's a topic for another thread (at another time I'm sure)

Thanks

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com