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

Is autoprivate this stupid? Or is it just me...

System

OK I have been through the TS Admin Guide where it goes through Autoprivate. I won't even start on the fact that the pattern matching is different than any other normal regex pattern matching they use in other places. What I'm trying to do is match this pattern to make these files private:

*_fu.*

Based on the documentation, it is not clear at all that I can do this, and if so, how to represent it in the autoprivate.cfg file. It appears that the wildcard character * has no meaning here. From the looks of things, I am getting the feeling that I need to know every possible file extension and enter that in explicitly for each one to create a pattern that this stupid thing will recognize. Is this true? I hope not.

Can anyone provide some help or am I doomed...

Find more posts tagged with

Comments

jbonifaci

I haven't used this in a long time, but reading through the manual, I think you're right. It looks like it can only do the following:

1) complete file name matches
2) matches at the beginning of a file name
3) matches at the end of a file name
4) matches at the beginning and end of a file name

It doesn't look like it can do matches in the middle of a file name, which is what you're looking to do. If this is true, you are going to need to specify all of the file extensions.

Not sure how they could write something this dumb when everything else uses regular expressions, but there you go.

~Jeff

Migrateduser

Thanks Jeff. It really irritates me that they couldn't use normal regex for this. Why they feel the need to complicate things to the point of making them have limited use is beyond me. This seems like a relic from the beginning of time at Interwoven, which of course they had to make in some inane proprietary format, and they just never saw fit to update it to something more useful and common, like regex. The fact that they utilize regex in many other places makes it even more maddening. I am irked beyond belief...

The good news, I suppose, is that this time at least, I am not the stupid one. Smiley Surprised

Adam Stoller

Thanks Jeff. It really irritates me that they couldn't use normal regex for this. Why they feel the need to complicate things to the point of making them have limited use is beyond me. This seems like a relic from the beginning of time at Interwoven, which of course they had to make in some inane proprietary format, and they just never saw fit to update it to something more useful and common, like regex. The fact that they utilize regex in many other places makes it even more maddening. I am irked beyond belief...

The good news, I suppose, is that this time at least, I am not the stupid one.

I believe Russell Nakano was responsible for autoprivate.cfg using a lisp-like syntax or something like that, and - yes, it comes from the very early days of the product (pre-3.1 which is where I first got involved).

Yes - it only handles exact, prefix, and suffix matches.

If your *_fu.* files are all in (or can be made to be in) a uniquely named directory you can use the second-part of the autoprivate.cfg file to mark that directory as private - though somehow I don't think that will help you too much.

What creates these files?
Perhaps you can use an iwat trigger script or perhaps code something into an externaltask script that runs iwprv -s (or the CSSDK equivalent: CSFile's setPrivateToWorkarea ?)

Migrateduser

I believe Russell Nakano was responsible for autoprivate.cfg using a lisp-like syntax or something like that, and - yes, it comes from the very early days of the product (pre-3.1 which is where I first got involved).

Yes - it only handles exact, prefix, and suffix matches.

If your *_fu.* files are all in (or can be made to be in) a uniquely named directory you can use the second-part of the autoprivate.cfg file to mark that directory as private - though somehow I don't think that will help you too much.

What creates these files?
Perhaps you can use an iwat trigger script or perhaps code something into an externaltask script that runs iwprv -s (or the CSSDK equivalent: CSFile's setPrivateToWorkarea ?)

The files will not all be in one place, so unfortunately I can't use the directory name. These files are being created for a "secret" part of the website that needs to be developed now, but won't go live until some later date. So they need to be worked into the website, but we cannot deploy them to production just yet. I would use a deployment filter, but we are already using an include pattern and you can't use an exclude pattern together with an include pattern (another peeve of mine, but I won't go there...).

I do like your event trigger idea. That is definitely compelling. I'm going to pursue that one, but in the meantime, I will likely just explicitly state all the possible file extensions we use and hope they don't create a different one.

Thanks for the tips - that is really helpful.

Crsb

I gave up on this file a while ago, it never seemed to work for me. And I always got annoyed with "invalid autoprivate.cfg format" msg in iwtrace.log even when using the default provided with TS install or from the docs.

ISCBorisB

I would use a deployment filter, but we are already using an include pattern

Something as simple as suffix filtering in/out is often possible to do using inclusion Filters only.
For example, the following should match "/boo/foo/whatever_mu.html" and "/boo/foo/whatever_nu.asp"
but will not match "/foo/moo/whatever_fu.jsp"

 /^.*([^_]..|_[^f].|_f[^u])\.[^\\\/]+$/

addSpace.rptdesign

Migrateduser

Well that's very interesting, too. I recall Adam helped me create this monster regex when we wanted to include index.html, but exclude index.jhtml (or something like that - I don't recall anymore). I think this was before there was an include option available:

"(^|.*\/)(i.{1,3}|i[^\/]{5,}|i([^n][^d][^e][^x]\.)[^\/]*|[^i\/][^\/]*)\.jhtml$"

And this regex is somewhat similar. I will play with that also. Thanks Boris.

Migrateduser

Unfortunately, however, because we are already using includePath filters in our deployments, we cannot also use includePattern filters. You can't combine them in the same definition.

Which is also ridiculous.

For whatever reason, you can combine excludePath and excludePattern filters in the same definition.

Sometimes I really don't like Interwoven.

Adam Stoller

I gave up on this file a while ago, it never seemed to work for me. And I always got annoyed with "invalid autoprivate.cfg format" msg in iwtrace.log even when using the default provided with TS install or from the docs.

Interesting - I've never had a problem copying autoprivate.cfg.example to autoprivate.cfg (and they fixed the example file as per an enhancement request I filed too!)

Adam Stoller

The files will not all be in one place, so unfortunately I can't use the directory name. These files are being created for a "secret" part of the website that needs to be developed now, but won't go live until some later date. So they need to be worked into the website, but we cannot deploy them to production just yet. I would use a deployment filter, but we are already using an include pattern and you can't use an exclude pattern together with an include pattern (another peeve of mine, but I won't go there...).

I do like your event trigger idea. That is definitely compelling. I'm going to pursue that one, but in the meantime, I will likely just explicitly state all the possible file extensions we use and hope they don't create a different one.

Thanks for the tips - that is really helpful.

Do you have any control over the file naming for these "secret" files? like maybe they could use an "fu_" prefix? Perhaps you can inject such an idea to those responsible for doing the design work...

Crsb

Interesting - I've never had a problem copying autoprivate.cfg.example to autoprivate.cfg (and they fixed the example file as per an enhancement request I filed too!)

in what version was it fixed?
I also tried just renaming the .example to .cfg and TeamSite still complained. This was in linux (redhat), I haven't tried in windows.
could you give me one that is working for you and i will try ?

Migrateduser

Do you have any control over the file naming for these "secret" files? like maybe they could use an "fu_" prefix? Perhaps you can inject such an idea to those responsible for doing the design work...

That's another good idea. I'm not sure of the requirements have been carved in stone yet for filenaming conventions for this project, but I sort of suspect they have. They are kind of waiting on me to getthis implemented in TeamSite. I will check, though. Thanks!

Adam Stoller

in what version was it fixed?
I also tried just renaming the .example to .cfg and TeamSite still complained. This was in linux (redhat), I haven't tried in windows.
could you give me one that is working for you and i will try ?

Responding privately - as this is not really part of this thread.

Annad

reply deleted