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)
Templating dir-regex
Jeremy
Hi,
I am on TS552 on Win2000.
I am trying to generate a file from a new or saved DCR, but every time I click on Save it comes back with the popup window where I am supposed to navigate to where I would like to save this, however the directory structure is not there - it does not give me any options of where to save other than the root.
In templating.cfg the
<directory dir-regex=".*" />
.
There is a similar problem in the DCR's while browsing for an image - the folder where it is directed to is full of images, but the popup comes back showing no images.
Any ideas if this might be a setting somewhere?
Any help -
Thanks!
Find more posts tagged with
Comments
akshathp
On one of my test server I did face a similar situation. It would take a long time but eventually fetch the list in the dialog box. I ran some tests and figured out that there were couple of processes running interminently on my test server which were eating the CPU time.
Maybe, it's just slow.. (Again, *Maybe*)
Hope this helps!
Akshat Pramod Sharma
Interwoven Inc.
Jeremy
Thanks for the response, but unfortunately it does not populate itself. I have left it for quite a while (about 10 minutes) and it still does not populate itself.
Any other ideas out there? It is not convenient to have to type in the full path to the file as we cannot browse.
Thanks.
Adam Stoller
Off the top of my head:
1) Ensure that "SYSTEM" is in the IWHOME/conf/roles/master.uid file
2) Verify permissions on the workarea
3) include, as an attachment, your IWHOME/local/config/templating.cfg file
--fish
(Interwoven Senior Technical Consultant)
Jeremy
Thanks for the response.
1) I checked my master.uid file - does contain SYSTEM
2) Checked my permissions on the WORKAREA - shared to "Teamsite User" - a group we have set up whcih contains all users who use Teamsite.
3) I have zipped my templating.cfg and attached it.
I have also opened a case with Interwoven support and will copy the emails I have sent them below:
Upgrading from 451 to 552 on Win2000 at Conde Nast.
I have attached my templating.cfg and an example of a
datacapture.cfg.
In the datacapture.cfg there is a browse section.
When I edit the DCR in the Browser based interfase, I can
edit all the other fields, but when I click on the browse
button to browse to a new image, the popup window comes back
blank. If I new the location of the image and the name of the
image I could type this in and it would work, but this is
very tedious and not the correct funtionality.
Also, when I click to Generate the file the popup where i
should be able to browse to where I want to save the file
comes back empty, so I cannot browse to save the file in a
particular location. Again, if I know the location of the
file then I can type it in, but again, this is not correct.
As you suggested I have created another test category within
a current templatedata. This datacapture.cfg only contains a
browse, and when I create a test DCR I can browse to the
images folder (before this was not possible) however no
images are shown, but there are images in the folder. Even
when I select "Files of type *.*" no files are shown.
I have attached this test DCT as datacapture.cfg.test. I can
also browse to Generate this DCR, but could not do this on
the other DCR.
And a little more info:
I just tried putting that datacapture.cfg that I created into
the branch that I was having trouble with, and it did not
work there. But it was working in another branch where the
other migrated DCR's are also working fine. So it appears to
be only happenning in this one branch.
However there was still the issue of browsing for an image
and the popup comes back empty.
That is with the setting set to Files *.*.
Thanks again.
Jeremy
Just to let you all know - it seems it was some kind of permissions thing. I tried creating a new Workarea and copied the latest stuff across in the Y: from the other Workarea. I then reset all the extended attributes using the script and after that everything seemed to work fine.
Not at all sure why this happened but it works now...so who knows!