Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Modified Files
rpjoseph
We have had to change permissions for update access within Teamsite Templating on nearly every file in our environment at least once since deploying Teamsite. We did not bother workflowing each of these files since we didn't change the content or any properties that would be propagated to our production environment.
Thousands of files show up in our 'view modified' list as a result. This makes it very hard to see what has actually changed and to do things like workflow deletes, etc.
I tried to do a 'Get Latest' with overwrite on to resolve the issue. That seemed to do nothing.
Any suggestions on how to start with a 'clean-slate' would be appreciated.
Thank you.
Find more posts tagged with
Comments
akshathp
After modifying the content in those files, did you submit the changes? If you have not submitted the changes, TeamSite will consider those files as changed and will always show as modified.
Your STAGING content is different then the content in your WORKAREA if it is not submitted.
Ofcourse you could create new workarea which wouldn't have such changes as it will be a copy from your latest edition but the best process would be to resovle existing it in existing workarea so that you do not loose the changes you have made.
Hope this helps!
Akshat Pramod Sharma
Interwoven Inc.
rpjoseph
Like I said - I changed permissions on the files for Teamsite access. The difference between the files shouldn't be replicated to stage. I changesd 1000's of files. It would take a week to publish all of the files.
Is there any other workaround than creating new workareas (we have mulitple workareas with the same issue) or submitting all files?
When we try to submit files from the modified files list - our PC's are locked up for about 15 minutes with CPU utilization at 100%. This is the behavior when trying to submit 3 files. I would hate to think what would happen trying to submit 1000's of files.
Bowker
We ran into a problem with just the same thing.
After adjusting the submit.cfg file I ended up submitting the whole site, one folder at a time. It took some time, but it could be scripted and done using a command line tool. If you have access to a telnet session of the ts server you could submit the files via a shell script or a dos bat file. It would take a while, but they would all get submitted and you could do it after hours/on a weekend.