Why aren’t the INCLUDE_EXTENSIONS file types uploaded as expected?


When trying to upload a file type that should be allowed based on the contents of the INCLUDE_EXTENSIONS and EXCLUDE_EXTENSIONS lines, the user gets a message stating that uploading a file of that type is not allowed. Why?

Adding spaces in the extension list will invalidate any other defined value after the first one listed. In the TRIRIGA 3.5.2 and later releases, more variables were added to the TRIRIGAWEB.properties file, for more-precise control over what can be loaded as an attachment to a record, or added to Document Manager. These variables are documented in the TRIRIGA Release Notes, but to give the basic information, these are the two new sets of variables:

  • COMPANY_FILE_UPLOAD_EXCLUDE_EXTENSIONS and COMPANY_FILE_UPLOAD_INCLUDE_EXTENSIONS
  • IMPORT_CONTENT_EXCLUDE_EXTENSIONS and IMPORT_CONTENT_INCLUDE_EXTENSIONS.

Any file extensions can be added here, but the format of the list needs to be properly set. Use only comma-separated values (CSV) without spaces to build the string. If there are any spaces in the list, remove them…

[Admin: To see other related posts, use the “include_extension” search phrase.]

Continue reading

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.