Basic management

Post system messages, read open sockets, and close or reopen the editor for maintenance.

Click Admin, then Manage Site. The Admin Panel has three tabs: System Messages, Open Sockets and Open/Close Editor.

​

System messages

A system message is a blue banner at the top of the Projects page and the editor. Every user sees it.

​

Post a message

Enter the text under Message and click Post Message. The tab lists the messages that are showing now.

Two posted messages

What users see

• A user can close a message with the ×. It stays closed in that browser.
• A page that is already open checks for new messages every 15 minutes. Reloading the page shows them at once.

​

Remove messages

Clear all messages removes every message at once and does not ask for confirmation. You cannot remove a single message.

​

Open sockets

A diagnostic view of the outgoing connections the web service has open at this moment. It does not show who is online: the list can be empty while users are in the editor.

​

Close the editor for maintenance

Use the Open/Close Editor tab. Its buttons act at once and do not ask for confirmation, and the tab does not show whether the editor is closed. To check, click Projects: you see the Maintenance page while it is closed.

The Open/Close Editor tab

1. Tell your users

   Post a message with the time of the maintenance.

2. Click Close Editor

   Despite its name, this closes almost the whole site. Every page except the admin panel shows Maintenance, including Projects, Account Settings, Templates and the login page. Manage Users and Project/Object Lookup keep working.

   

   What users see while the editor is closed

   Users who already have the editor open stay connected. They can keep typing and their changes are kept, but Recompile ends with Server Error.

   To change the text of this page, see Maintenance page.

3. Click Disconnect all users

   Users in the editor see the dialog Please wait, which counts down from 10 seconds. Then their page refreshes and shows Maintenance.

   

   What users in the editor see

   Close the editor first: otherwise the refresh brings users straight back into the editor.

4. Do the maintenance, then click Reopen Editor

   Every page works again at once. Users reload the page to continue.

The login page is closed too, so stay signed in until you have reopened the editor. If you are locked out, restart the instance: the closed state is only kept in memory, so a restart opens the editor again.

On Kubernetes with several replicas, Close Editor only closes the replica that served your request. Use Maintenance mode instead.