Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Cannot regenerate files in TS 7.3 unless lock the file manually first
syim
Hi,
We are under go upgrading TS 6.5 to TS 7.3. We migrated our old content, templates and workflows to TS 7.3. We are currently doing testing in TS 7.3 to ensure our old templates and workflows still works in TS 7.3.
We have "Mandatory Write" Locking in our workareas. For some of our migrated content files, we are not able to regenerated the file when clicking the Generate button within the template, unless we manually place a file lock on the generated file first. In TS 6.5, the file lock will be placed automatically whenever we click on the Edit link. However, it does not seem to be the case in TS 7.3.
I wonder if any of you encountered the same issue after upgraded to TS 7.3? I wonder if there is a bug in TS 7.3 caused this problem?
Thanks,
Susan
Find more posts tagged with
Comments
nipper
I expect you are on your own.
Bery few people use Mandatory write lock, almost all use the default
Also 7.3 has been replaced with 7.3.1
It was up on the support for a very short time. There most certainly was one or more showstoppers in it that made it out. This issue may be in that list.
syim
I just found out with Autonomy Tech Support that starting with TeamSite 6.7.1 Service Pack 1, by default, when a ContentCenter GUI (or LaunchPad or the TeamPortal portlets) is enforcing mandatory write locking, a file is only locked after being modified. To turn this behavior off (so that a lock is obtained when a file is opened but not modified), edit application_custom.xml as follows:
<applications>
<default-param id="iw.common.edit.lock_on_modification" value="false">
</default-param>
image1.png