> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/installation-and-upgrade-issues/user-console-themes-render-improperly-after-upgrade.md).

# User Console themes render improperly after upgrade

There are two possible causes for improperly rendered User Console themes:

* If you are seeing unusual rendering problems in the User Console shortly after performing a Pentaho Server upgrade, the problem may be related to old JavaScript files being held in the browser cache:

  To fix this problem, clear your web browser's cache, then reload the Pentaho User Console.
* If the login page appears blank with all input fields left-justified:

  To fix this problem, stop the Pentaho Server. Navigate to the `pentaho/server/pentaho-server/pentaho-solutions/system` directory and open the `pentaho.xml` file with any text editor. Edit the **\<default-theme>** parameter so that only lower-case letters are used in the parameter value (for example, `ruby`, `crystal`, or `sapphire`). Save and close the file. Start the Pentaho Server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/install/9.3-install/pentaho-installation-overview-cp/installation-and-upgrade-issues/user-console-themes-render-improperly-after-upgrade.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
