 |
FirstClass resources
Where default resources reside and how the server accesses them
FirstClass stores the standard shipping images, pictures, icons, forms, language strings, and help files for the client and Internet Services in the FC Resource Registry located on the administrator's Desktop. For information on how Internet Services accesses resources, see Understanding Internet Services Resources.
Note
This is the default setup for an English FirstClass site. Sites with a different default language will have the appropriate language names.
FirstClass server serves out resources from:
A conference's Rules and Resources folder |
Every container template, conference, and Mailbox on your system has a Rules and Resources folder. Uploading resources directly to the container will automatically load the resources for the user when the container is opened. |
English Resources |
Stores standard registration and licensing forms. It's main purpose is to safely store global custom resources (images, icons, forms, strings, and so on) that you may use on your site or sites that won't be overridden during a system upgrade. |
Pictures.rez |
Contains the shipping pictures and images used for the web client. Although you can place images in different locations, from an Internet Services perspective it is best to place them in the Pictures.rez file. NoteAll pictures and images must have unique names and ID numbers. |
Icons.rez |
Contains the shipping icons used for both the FirstClass client and the web client. If you have either a multiple-site or a multiple-language site setup and you want different icons for each site, you must create an Icons.rez file (see FirstClass Designer) and place it in each
of the site folders at the root level (for example, at the same level as the .sitepref form). Keep in mind, you only need to put the custom icons in the site-specific folders. If Internet Services cannot find an icon in these locations, it will fall back to the Resource Registry hunt chain. |
MobileIcons.rez |
Contains icons specific to the mobile templates and sits in the Resource Registry only. If you want to override the shipped icons, you can use the HeaderMatch SET icons or SET pictures options in the HeaderMatch document: *: IF User-Agent == "UPG1 UP/4\\.0 (compatible; Blazer 1\\.0)" SET .templates = .mobiletemplates AND SET icons = mobileicons.rez *: IF User-Agent == "Mozilla/2\\.0 (compatible; MSIE 3\\.02; Windows CE; 240x320)" SET .templates = .mobiletemplates AND SET icons = mobileicons.rez If you want to run mobile templates on a separate site, you could put the MobileIcons.rez file in the site folder, rename it Icons.rez and remove this line in the HeaderMatch document: *: IF VAR INTERFACE == 4 SET icons = MobileIcons |
Lang.rez files |
Lang.rez contains the specific shipping resources (forms and strings) for a particular language. Since Internet Services processes Lang.rez files independently of the language-specific site content processing, you can have multiple Lang.rez files on a site. If you want to support multiple languages on your site, place the specific Lang.rez file (for example, fr.rez, es.rez, dk.rez) in the Resource Registry. If you want to support multiple sites with different languages, place the specific Lang.rez file in the respective site-specific folder. |
Putting custom resources on your server
If you use custom resources globally (for all of your sites), we recommend placing them in English Resources (or the linguistic equivalent), since resources contained in this location are not overwritten during an upgrade process. To do this,
Custom resources intended only for specific sites must be stored at the site level. If you use custom pictures or images, place them in the site-specific Images folder in the same location as the site templates. If Internet Services cannot find a picture or image in the site-specific Images folder, it will look in the Resource Registry, as per the Internet Services hunt chain.
For custom icons or custom language strings and forms, create either an Icons.rez or lang.rez file respectively and place it in the site folder at the same level as the site templates. For information on creating resource files, see FirstClass Designer.
For custom resources for particular conferences, or groups of containers (container templates), upload the resource to the conference or container template's Rules and Resources folder. The resources will download automatically when the conference is opened.
For custom resources for an individual user, upload the resources to the user's Mailbox Rules and Resources folder. The resources will download automatically when the Mailbox is opened.
Making server resources available to users
Resources stored in a container's Rules and Resources folder are applied as soon as the user opens the container.
Resources stored in the FC Resource Registry are not available to users (for example, they do not show up in menus) until users do one of the following:
• log in with a settings file that contains the resources
• work with objects that use these resources
• type the resource names in appropriate fields, such as an "Image" field.
As soon as a user works with an object that uses a resource stored in the FC Resource Registry, that resource is added to the user's settings file. Then the resource is available to the user, and will show up in the user's menus.
To force FirstClass to add these resources to users' settings files, you need to make objects that use these resources available to users. For example, you might:
• post a message using a particular form to all users or to a conference
When users open this message, the form will be downloaded to their settings files.
• add a folder containing other folders that use certain icons to a conference.
When users open the parent folder, the icons for the folders inside will be downloaded to their settings files.
If users cannot see resources
If someone sends a message using one version of a form, and the recipient has an older version of the form in their settings file, there may be inconsistencies when the form displays. Each user will see the form stored in their local settings file in the client.
To force FirstClass to use the new form, users can flush their caches. This removes forms and other resources from their settings files, allowing new resources to download as required.
|  |