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; } } }

Global change

reeturaj

Is there a way in teamsite to make the same changes in all the generated files. The generated files are stored within teamsite.

Find more posts tagged with

Comments

akshathp

One way is to make a change in your presentation layer (TPL) and regenerate all the files once again. You can regenerate using TeamSIte command line tool REGEN. You could even automate this for entire folder by writing a small PERL script which makes a system call on each file one by one for regen command.

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

Adam Stoller

Do you mean TeamSite Templating generated files or some other engine-generated files?

In the case of TeamSite Templating generated files assuming the change is made in the Presentation Template layer - you can regenerate all the existing generated files and then submit / deploy them - there's a script posted in the tech-notes section[48941] for recursing through a directory structure and running iwregen on all files that have the appropriate TeamSite extended attributes (brute-force approach) - the script is currently written for Windows, but I just posted a variant that should work on either Windows or Unix (when verified the script assocaited with the TechNote will get updated)

Is that the kind of information you were looking for?

--fish
(Interwoven, Curriculum Development)

reeturaj

Thanks for your response. We imported several hundred pages into teamsite in the directory structure (we also generated pages through templates in the same directory structure).

We need to make the global changes in the directly imported files. That is the files that are not generated through templating. Let me know if you require any other information.

Appreciate your response

Adam Stoller

If the files were not generated with TeamSite Templating - do they share some other form of common component, like SSI's?

If not - I cannot see any trivial way to make a "global" change to these non-generated files. If they conform to some kind of "standard" structure/format - scripting such changes will be easier - but if they are a hodgepodge of different structures/formats then I'd say all bets are off.

For a longer-term solution - are you planning to covert the imported files into templated files? As you can hopefully see - having template-generated files makes it easier to make "global" changes and have them re-applied.

If you're planning on going that route - you might consider the costs (time/effort) of just making the hard-coded global change to these files now, versus translating them into templated files now and using a PT to implement the global changes you want.

--fish
(Interwoven, Curriculum Development)

reeturaj

They are basically html files and we need to remove javascript's and change the stylesheet links. This operation needs to be done on all the non-generated pages.

mogoo

You could always mount your teamsite drive to your desktop, then have Homesite or Dreamweaver crawl through and make the change. It would be nice if TeamSite had an equivalent, though. I don't know of any, maybe I'm wrong...
-maureen

akshathp

Seems you need to change content in the static html files in your TeamSite repository. Also, only those files that are not templatized.
I would suggest to write a simple perl script that would
a) crawl the site, and check for only html content
b) check for the extended attributes using iwextattr to see if it is not generated using Templating
c) Once these two checks are performed then simple read and write operation in the file with regex to filter content as per your criteria.
d) Once this is done then iwsubmit to submit it at the same time.

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

Edited by akshat on 09/24/02 12:43 PM (server time).

reeturaj

Permissions are set in both the individual workareas and in the staging area so we are not able to browse to to any of the folders. I have a couple of questions.

Do we need to change the permissions and then mount teamsite drive to our desktop to make the global change.

Also, will we be making the changes in a particular workarea or in the staging area.

Appreciate your response

TextToPDF(SP4).dcpackage.zip

output(SP4).pdf

mogoo

We don't have our system set up where we can map the teamsite drive to our computer, so I haven't tested this.... akshat or ghoti, please help out, and correct me where I'm wrong.... also, are there any implications to editing files this way -- do external attributes and versioning work normally??

I'm pretty sure you still need to make the changes in a WA, since staging is read-only.

When you map the teamsite drive to your computer, I'm guessing someone has enough privileges to access all the files in TeamSite? If so, that's who's computer you want to use, because I believe the permissions carry over to the mounted drive.

Hope that helps,
maureen

akshathp

You *cannot* modify content in STAGING as staging is always readonly. What you should do is have a workarea in which you can perform a GetLatest so that the content is fresh as per STAGING.

Second, the script that I was talking about would have to run on your TeamSite server. So, you would need to either telnet into the sytem or SSH (depending upon the server permissions). I would suggest your TeamSite administrator should run this utlility and it can be run as a command line tool.

So once this Workarea is latest as per STAGING after performing GetLatest, your custom script should do the following:
1) Check for HTML content
2) Then check if it is not a file generated via templating (using iwextattr CLT)
3) Read the file, perform REGEX operations that would alter the content as per your needs
4) Write the fresh content in the same file
5) If you are confident and have tested this over a couple of test files, then you could even have iwsubmit CLT submit this altered file into STAGING within the same script.

Hope this helps.

Akshat Pramod Sharma
Interwoven Inc.

Adam Stoller

Connecting to the TeamSite server at the file system interface is reasonably well covered in the TeamSite Administration Guide.
"Extended" (not "external") attributes and versioning work just fine - in terms of being there and being accessible, and generating new ones.
If you aren't using the GUI interface though, you need to know how to use the CLTs to achieve the same results (e.g., iwextattr, iwsubmit, iwupdate, etc.)
Yes - you can only make changes in the workarea. Staging and Editions are read-only at the file system level too (this is managed by the IFS)
Restrictions on who can map drives from where to where are administrative functions - but yes, it has to be someone who has a defined role within TeamSite in order to be able to interact with it.

--fish
(Interwoven, Curriculum Development)

tecthis

The best and easiest way to do it, is to make all the changes on your harddrive before importing to teamsite.

Thanks,
Alex...

Alexander Correaa
alex_correa@baxter.com