Simple TPL Question - directory dir-regex

I'm trying to use a simple regex in the TPL to enforce where a generated output file can be saved in the work area directory structure.

For example on the following type of path I'm trying to prevent output files from being saved higher up than the /content/ directory. Any sub directory inside of /content/ should be fine.

/default/main/hnfs/va/WORKAREA/work/content/company/news

My entry in the templating .cfg is attached.

Where am I going wrong?

Many thanks!
-Ninerfan

Find more posts tagged with

Comments

Adam Stoller

I'm trying to use a simple regex in the TPL to enforce where a generated output file can be saved in the work area directory structure.

For example on the following type of path I'm trying to prevent output files from being saved higher up than the /content/ directory. Any sub directory inside of /content/ should be fine.

/default/main/hnfs/va/WORKAREA/work/content/company/news

My entry in the templating .cfg is attached.

Where am I going wrong?

Many thanks!
-Ninerfan

Try removing the highlighted dot

 <directory dir-regex="/content/..*" />

Ninerfan

Hi thanks for the reply.

I tried removing the extra dot as you suggested but I'm still getting the same problem. See the attached image error1.gif. It shows the alert box I see when I try to generate the page. The error2.gif only shows up if I try to save a output file in the root of the work area with your regex or in the root or /content folder using my regex (two dots).

It seems like the original regex was exactly what we wanted in other words with the two dots, files could NOT be saved directly in the work area root or here in the content folder. Which is the way we want it too work.

/default/main/hnfs/va/WORKAREA/work/content/

Files COULD be saved in any sub folder of content
/default/main/hnfs/va/WORKAREA/work/content/company
/default/main/hnfs/va/WORKAREA/work/content/company/news
/default/main/hnfs/va/WORKAREA/work/content/company/etc

But regardless of if we use the one dot or two dot regex no matter where we try to save the generated .jsp file we get the error1.gif message.

It feels like the dir-regex line is getting picked up correct when we are navigating to select our save path but NOT when we actually try to save the generated page there. Like it's passing one test but failing another.

Any guesses?

Adam Stoller

Hi thanks for the reply.

I tried removing the extra dot as you suggested but I'm still getting the same problem. See the attached image error1.gif. It shows the alert box I see when I try to generate the page. The error2.gif only shows up if I try to save a output file in the root of the work area with your regex or in the root or /content folder using my regex (two dots).

It seems like the original regex was exactly what we wanted in other words with the two dots, files could NOT be saved directly in the work area root or here in the content folder. Which is the way we want it too work.

/default/main/hnfs/va/WORKAREA/work/content/

Files COULD be saved in any sub folder of content
/default/main/hnfs/va/WORKAREA/work/content/company
/default/main/hnfs/va/WORKAREA/work/content/company/news
/default/main/hnfs/va/WORKAREA/work/content/company/etc

But regardless of if we use the one dot or two dot regex no matter where we try to save the generated .jsp file we get the error1.gif message.

It feels like the dir-regex line is getting picked up correct when we are navigating to select our save path but NOT when we actually try to save the generated page there. Like it's passing one test but failing another.

Any guesses?

Two things come to mind:

The last one is an oddity I've seen in some programs where although forward slashes work from a programmatic view point, if the internal code uses one type of slash and tries to do a comparison with a path using the other type of slash it will (erroneously) fail.

Ninerfan

Hi again,

Okay now I'm conviced this is a bug in the version of TeamSite we are running. 6.5.0 SP2 Build 51749 on Solaris.

The regex expressions we have tried with your help have behaved exactly as they should when it comes to navigating to the location to save the generated page. In other words during the navigation (folder selection) process the regex causes the warning message to correctly pop up when you pick an invalid location. However when we pick a valid location we get a completely different error message from a JavaScript Alert box which is the error1.gif attached previously. That message feel like it's coming from a different part of the system not from pasing our regex in templating.cfg.

It looks like our version of TeamSite won't allow us to have much control via templating.cfg of where our users can save generated output files. We are stuck with the default of directory dir-regex=".*"

Any other regex give us the error1.gif attached earlier.

Thanks for you help though I really appreciate your efforts! :-)