Configure application profiles
Important
Settings and actions described below are only available for Rigi subscribers. For details, see the User roles section.
You can configure the Rigi script to recognize strings on overlay elements and behind them and ignore specific strings that should not be captured on HTML previews. To do so, perform the following steps:
Select the
icon (system menu) > Server settings > Context > Application profile.
Click the Create profile button in the top right-hand corner of the screen. The Create application profile wizard is displayed.
To edit an existing profile, click the
'Edit' icon in the Actions column.On the Frontend classes wizard screen, perform the following:
Give the newly created profile a name.
(Optional) In the Overlay classes field, enter the names of the overlay elements you want to recognize strings on. Click 'Enter' to add an element to the list.
(Optional) In the Invisible classes field, enter the names of the elements you want to hide. Click 'Enter' to add an element to the list.
Click the Next button.
On the Rigi script settings wizard screen, you can configure specific Rigi script key/value pairs.
The script includes several predefined keys. Those keys cannot be deleted, and their key name and type cannot be edited.
To define custom key/value pairs, enter the key name in the Key column, select its type, and then select or enter the required value.
Use custom keys to enable specific features in the Rigi script that are not yet published.
Click the Create button. The newly created application profile can now be selected in the project's URL settings. For details, see the Project settings – URLs
Important
Only use this setting if you experience runtime errors during capturing.
Some web applications will raise runtime errors during HTML preview capturing. This can be caused by strings that contain HTML elements. You can try to avoid those errors by setting the skipHtmlTexts variable to true. In this mode, the Rigi script will not replace texts on the page (DOM), and the Rigi tokens will stay on the page.
Assume that the developers defined a string with an HTML tag in their resource file:
key="__Hello <subElem>great</subElem> world__"
This will show in the HTML of the live application like this:
<topElem>__Hello <subElem>great</subElem> world__</topElem>
When Rigi is active on the live site (for example, during capturing, live translation, or live review), Rigi replaces the entire topElem inner HTML with a new string at runtime. As a result, the subElem in that inner HTML is a new element: it no longer has a connection with the topElem.
When the code tries to access the original subElem, it will result in an error.
To avoid such behavior at runtime, set skipHtmlTexts to true in the application profile selected in the project URL settings (for details, see the Project settings – URLs section). This will prevent the Rigi script from replacing texts that contain HTML elements.
Rigi can still replace strings in captured HTML previews.