<-- Back

How to locate and modify a custom offline page in Mendix

Introduction

When a Mendix app is offline and stopped, an offline page is displayed. This page can be customized.

In some cases, a previously configured custom offline page is served from cache. The cached page can continue to appear after redeploying the app or removing the Mendix Deployment Archive (MDA). In this situation, the custom offline page HTML file is not available in the current project for editing.

Deploy a new custom offline page to replace the cached offline page.

Environment

  • Applications hosted in Mendix Cloud
  • Studio Pro (all versions)

Instructions/Procedure

If the project does not contain the custom offline page HTML file, it cannot be modified directly. To update the offline page, create and deploy a new custom offline page. Deploying a new offline page replaces the previously cached version in Mendix Cloud. 

A cached version is a previously deployed copy of the custom offline page that Mendix Cloud continues to serve even after the application is redeployed, and it can remain in use even when the HTML file is no longer present in the current project.

Steps to update the offline page:

  1. Open the project in Mendix Studio Pro.
  2. In the project directory, open the theme folder.
  3. Create an error_page folder in the appropriate location for the Atlas UI version used by the app.
  4. In the error_page folder, create a file named offline.html.
  5. Open offline.html and add the required HTML content for the offline page.
  6. Deploy the application to Mendix Cloud.
  7. Stop the application.
  8. Open the environment URL and verify that the updated offline page is displayed.

Outcome

Deploying the new offline page replaces the previously cached version in Mendix Cloud.

Internal information related

  • 266341
  • C07BE6K6F5L/p1765197802216429

Additional information

Mendix documentation: Custom Error Page

Have more questions? Submit a request

0 Comments

Article is closed for comments.

To provide feedback, please open a ticket here. Don't forget to include the article's URL along with the feedback you would like to provide.