[opencms-dev] Undesired side effects on module export.

[Carl Alex Friis Nielsen]

I just discovered the following:

One of the resources in a module has to be placed on the site part of the VFS.

Let the resource be named /foo/bar/foobar.html, where "foo" is a
folder containing LOTS of other resources not having anything to do with
the module.

When importing this module the properties of the "foo" folder in the target
cms are overwritten by the properties of the "foo" folder in the source cms
but only if they are set in the source cms.

I could not find anywhere to tell the module that the properties of "foo"
should not be exported.

Unless someone can tell me some way to avoid exporting the properties of
"foo" this will force me to have the same properties on "foo" in my
devolpment cms and our production cms.

In my case the properties of the "foo" folder contain major configuration
stuff of our cms, and not being able to freely mess around with that in my
development environment is a real pain.

Is there some way to suppress exporting the properties with the module ?

Cheers,

Carl