Restrictions on preview generation in Visual mode
Assets required for preview generation might not be added to the preview package ZIP file in these cases:
Reason why assets are not added to preview package | Description |
|---|---|
Use of relative paths to assets | Only absolute paths to internal resources are valid: the use of relative paths will prevent references from being found. The assets concerned will not be added to the preview package ZIP file. (See step 4. in the Visual mode process description for details.) |
Javascript 1 | The Visual mode preview is generated from raw content. Data that is rendered on the client side, such as content that is pulled with an AJAX request, will not be displayed in the preview. To be certain that previews can be generated, ensure that data required for the preview is not rendered in this way. |
Javascript 2 | Nested applications can also prevent previews from rendering. You might need to disable import of some javascript files for that reason. Example: the way some REACT- or Vue-based applications are rendered can mean that the content is only displayed once the app is fully initialized. Until then, the HTML content might simply be hidden. |
Invalid markup | To guarantee that the preview is correct, you must ensure that the markup generated by your application is valid. If not, this might cause problems with displaying the content in the preview. |
Iframes | Content displayed in iframes can cause issues. If present, the preview generator will simply try to display the content of the iframe itself, which is not intended for translation. This means that the content that is actually inside the iframe will not be translatable. |
Using nonstandard locations for CSS or JS files | In Adobe Experience Manager, the clientlibs are now served by the /etc.clientlibs servlet. To prevent preview display issues, ensure that all your CSS and JS files are a part of a clientlib. |