How long until a user session are invalidated? Controls when a user is automatically logged out etc. Set in milliseconds.
A commaseperated list of sitenodes to recache
This is to enable one of the recache strategies to know what to recache after a publication.
Can be one of these:
- requestCentric (recommended) – before flushing all caches the strategy makes a few requests to specified pages so a lot of data get’s reached. Minimizes the load after a publication.
- requestAndMetaInfoCentric - before flushing all caches the strategy makes a few requests to specified pages and indexes all pages meta info so a lot of data get’s reached. Minimizes the load after a publication – a bit slower.
- contentCentric - before flushing all caches the strategy indexes some contents. Minimizes the load after a publication – not recommended.
Used by the recache strategies which calls pages. Should point out the ViewPage.action with a full url.
Enable Nice/Friendly URI in working
Set to Yes if you want the working deliver engine to render url:s like /products/infoglue_cms instead for /ViewPage.action?siteNodeId=7 etc. Overrides next field.
Enable Nice/Friendly URI
Set to Yes if you want all the deliver engines to render url:s like /products/infoglue_cms instead for /ViewPage.action?siteNodeId=7 etc.
Nice/Friendly URI encoding
What encoding should be used if encoding takes place due to i18n-characters.
Nice/Friendly URI attribute
What meta info attribute should be used to generate the URI:s. Can be any page meta info attribute or SiteNode.name which uses the non localized name from the structure three.
Nice/Friendly URI Character mappings
This field allows you to state what characters/strings should replace non-ascii-characters in nice uri:s. Below is an example on how we map som special swedish characters:
Default replacement character (if not mapped) and non ascii
You can state here what character should be used for non ascii-chars in the nice uri. Use “none” if you want such chars to just be removed without replacement. Default replacement is “_” (underscore).
Nice/Friendly URI force lowercase
States if you wish the system to force lowercase on all nice uri-names.
Request argument delimiter
Should we use & or & or ; as the argument separator?
Error page URL
If you want a custom error page you can set that here. When an error occurs the user will be shown the information and the url can be relative or full.
Use short table names
The value should be “Yes” if you run InfoGlue against a DB/2 or Oracle database. Set by the installer usually but can be set here as well.
Number of content versions (for each language) to keep (-1 = all)
This field set’s up how many versions the content cleanup routine should keep. By default it keeps all. The cleanup routine runs each day and if you want to save space and think you don’t need all the old versions in the system you can state how many in each language you want to keep.
State how much time must have passed between two versions for the cleanup routine to keep both versions (leave empty to skip this logic)
This field makes if possible to have the cleanup routine be more selective about what it cleans.
Duplicate assets on version change (no default)
Here you can state if you want the old behaviour where all assets were duplicated between versions or if the system should use the new method (default) which shares assets between versions unless changed.
Asset upload transformations
This field let’s you define if there should be any global transformations of images. This feature let’s you force so images can be resized to predefined sizes upon uploads. Below is the syntax for transformation setups:
<transformations> <transformation assetKeyPattern="(minibild)" inputFilePattern=".*(jpeg|jpg|gif|png).*" keepOriginal="false"> <tranformResult type="scaleImage" width="50" height="50" outputFormat="jpg" assetSuffix="small"/> </transformation> <transformation inputFilePattern=".*(jpeg|jpg|gif|png).*" keepOriginal="false"> <tranformResult type="scaleImage" width="100" height="100" outputFormat="png" assetSuffix="medium"/> <tranformResult type="scaleImage" width="50" height="50" outputFormat="jpg" assetSuffix="small"/> </transformation> </transformations>
As you can see you can state 0..n transformations which will be checked for each upload (only new assets – not updates). For each transformation you can state regular expressions to control which images and asset keys it triggers on and transforms. You can also state if the original file should be kept or not. For now there is only a scaleImage transform result type but that could change in the future. Let us know what other results would be nice to have.
comments powered by Disqus