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

Accessing files in another workarea

shilpapalkar

Hi,

I would like to know if i can access files from another workarea. If yes...please guide.

Find more posts tagged with

Comments

Adam Stoller

Hi,

I would like to know if i can access files from another workarea. If yes...please guide.

Sure - navigate into the other workarea and access the files.

If you wanted something else - you need to provide a lot more information.

shilpapalkar

Thanks forsuch a lovely solution....

Neways i have a workarea which has common files such as styles, images, scripts.

I want to access the files in this workarea from another workarea where i have the templates under the presentation folder.

To give you a short overview of my current structure is

SpecificWorkarea1
Category1
Datatype1
Data
Presentation
specifictemplate.tpl
datacapture.cfg

GeneralWorkarea
CommonCategory
css
styles.css

How can i access styles.css file from the GeneralWorkarea in the specifictemplate.tpl which is in the SpecificWorkarea1.

in my tpl i want to access the css file in the tag

please specify the full path to access as i am new to interwoven and yet to get a feel of the product.

ISCBorisB

please specify the full path to access...

Full Path is not how you should be doing that. Your PTs generate components for some Production Environment
that does not have Workareas, Staging, etc... So, in TS you normally generate "ready to go" code with the
referencing Syntax (Path and all) that reflects structure of the ultimate target Environment.

To make your Preview work with this arrangement in TeamSite, you configure IWOV Proxy Server. This component
basically "re-maps" rendered Pages assets (CSS, JS, images and whatnot) to the correct TS Preview Environment
location. You achieve that by supplying certain match/substitution Pairs for mapped resources.

See TeamSite® Administration Guide, Chapter "Configuring the TeamSite Web Daemon and Proxy Server" for details.

Adam Stoller

Thanks forsuch a lovely solution....

Neways i have a workarea which has common files such as styles, images, scripts.

I want to access the files in this workarea from another workarea where i have the templates under the presentation folder.

To give you a short overview of my current structure is

SpecificWorkarea1
Category1
Datatype1
Data
Presentation
specifictemplate.tpl
datacapture.cfg

GeneralWorkarea
CommonCategory
css
styles.css

How can i access styles.css file from the GeneralWorkarea in the specifictemplate.tpl which is in the SpecificWorkarea1.

in my tpl i want to access the css file in the tag

please specify the full path to access as i am new to interwoven and yet to get a feel of the product.

Are these workareas on the same branch or different branches?

If they're on the same branch - you're not doing things correctly (based on your statements) - because a workarea should be a view of the entire branch's contents.

If they're on different branches - then the iwproxy settings that Boris mentions is what you're looking for.

shilpapalkar

Hi,

they are in the same branch.

please help

LMX

When you submit files from a workarea, they are submitted to staging. By storing files in one workarea, you are "technically" making them available to all workareas once they are submitted (you can run a "get latest" to retrieve this data from staging). It's not to say that your setup is "wrong" (we would need more detail before we can critisize the architecture), but you have to realize that data found in workarea1 will eventually be available (and editable) to workarea2, workarea3, etc.

Without business requirements, it's hard to give you good advice. However, you should take a hard look at the TeamSite admin guide -- it'll give you a better understanding of how to use branches vs. workareas.

If you need to get thing up and running asap, submit all files to staging and resolve all of your conflicts. Then, update all of your workareas with the latest files in staging ("get latest"). At this point, you can configure your proxy to point to the specific workarea the user is in (iw.cfg -- pluging, preconnect and failover remaps).

This will copy all of your CSS (and other "support" files) to each workarea, and allow users to preview data found in their workarea prior to submitting it to staging.

I don't think this is the ideal solution, but it's probably the best way to solve your problem considering your existing branching structure...

G'luck.

rajathi

Hi,

If it is in the same branch, the best way to implement is to have the copy of CSS / JS files in the other workarea too.

nipper

Hi,

If it is in the same branch, the best way to implement is to have the copy of CSS / JS files in the other workarea too.

Copy no. Submit/Get latest (or update) yes. Copy from one to another is really a bad idea.