Infradox XS - 26.5 and later
Infradox XS websites are template driven. The templates use constants to output text depending on the active locale (user interface language). The constants files are centrally stored, i.e. all Infradox XS websites use the same files. You can change the values for these locales by creating a local copy of one or more of these files. Note that the constants can also be used in your custom templates. This article describes how you can create and modify a local copy of the constants files.
Changing the constants
Go to Site configuration and click Constants. Then select the locale that you want to change in the dropdown box at the top. The list at the top of the page shows all the constants files (you may need to scroll inside the boxes to see all the files). The list at the bottom of the page shows the changed constants files.
Make sure that you have read the itemised list in paragraph below before you make any changes!
- To create a new local copy for your changes, click on the file name in the box at the box (unmodified versions) to open the edit dialog. Make your changes and click save at the bottom. A local copy will be created if it didn't already exist. Your local copy will be overwritten if it did already exist.
- To make changes to a local copy of a constants file (i.e. the version of the file that was previously modified), click its name in the list at the bottom to open the edit dialog. When you are done, click the save button.
- To restore the original constants file, click the delete button on the right of the list with local copies.
Carefully read the list below, if you fail to follow these rules you may cause serious website problems and we will not be able to offer support.
- Constants files have name=value pairs on each line. A single line may have only one constant
- A constant must use the format name=value
For example cClosebutton=Close - where cClosebutton represents the name, and Close represents the value - you may only change the value part
- A constant (i.e. a line in the file) may have only one = character
- A constant may not have quotes (")
- You may not change the name part of a constant (see above)
- You may not remove constants from the file
- You may not add new constant names
- The changed value part preferably uses a similar length. You will have to test your changes carefully to make sure that your changes do not break the page layout. You may have to create custom css for certain elements if the changed version of a constant's value is longer or shorter than the original value.
- The constants files may have constants that are no longer used, but that are left in there for backward compatibility.
- The constants files may have constants that can be changed in other places in backoffice. Please check before you make a change.
- BEFORE 27.3 Some contant values have a code between square brackets (e.g. [cart] or [count]). These must stay and may not be changed.
- 27.3 OR LATER The value of a constant may start with a * (asterisk) to indicate that the value contains a replace tag (between square brackets). The * will automatically be removed and the tags will be replaced. E.g. cSomemessage=*Call us on [phone] for information about your [cart].
If a constant value has tags but doesn't start with a *, then the tags will not be replaced.
- Don't create a local copy of a constants file if you didn't change anything in that file.
- Constants are cached in each DLL instance. If you make changes, the current instance of the DLL will automatically flush its internal cache and it will try to unload other DLL's that may be in memory. However, sometimes it is not possible to unload other DLL instances. If you don't see your changes on the client facing website then try to view your changes using another browser or another computer. All DLL instances are autoamatically recycled every x-minutes so worst case you'll have to wait until this event has occurred on the server.
- If you create local copies of constants files, any changes that may be introduced by an XS update will not be in your local copy. The update documentation will list which locales are changed or added (if any) so that you know which changes to make to your local files.
- We can not offer support if you run into problems as a result of not following these rules. Delete your local copy if you suspect there are problems as a result of your changes.