Skip to main content

Rigi Documentation

Why are some parts of my app not working anymore with Rigi?

In some cases, parts of the application might not work anymore when Rigi is active. To find the cause and resolve this problem, perform the following steps:

  1. Open your browser and navigate to the page with the Rigi language loaded. Does it still work?

  2. Open the developer console (F12). Execute command: RIGI_Initialize({}). Does it still work?

  3. In the developer console (F12), execute command: SaveScreenshot('name.html'). Does it still work?

  4. Capture a preview using the Rigi application. Does it still work?

Problem

Rigi tokenized language is basically the source language, extended with invisible characters (for details, see the Rigi tokenssection). It should not break the code because it is just a resource file that could also be returned by translators. However, there could be an internationalization issue that the developers must resolve.

Fix

Find the string causing the issue by replacing strings in the Rigi resource files with source strings one by one until the app works again.

Try to find out why that string breaks the app. Modify the code so that the string does not break anymore.

Problem:

Rigi script changes the DOM at run-time, which might cause the app to fail.

Fix:

Configure script capture settings so Rigi does not modify the DOM at runtime. For details, see the Advanced script capture settings section.

Problem:

The Rigi script’s method of capturing the page breaks your code.

This is unlikely to be caused by the capture itself because the capture does not make additional changes to the DOM. However, we do make a capture popup visible when the capture method is invoked.

Contact the Rigi team for help.