> For the complete documentation index, see [llms.txt](https://www.locksmith.guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.locksmith.guide/faqs/more/i-switched-themes-and-locksmith-isnt-working.md).

# I switched themes, and Locksmith isn't working

## **The solution: trigger a new Locksmith install for your theme**

**Click the "Help" button, and then click the "Update Locksmith" button:**

When changing around themes, Locksmith needs to be re-installed each time you do this. To initiate a new theme install on your *currently published theme*, press the "Update Locksmith" button on the "Help" page:

![](https://277214568-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUeGWHuijBPr8Og1Gta%2Fuploads%2FFNEJLIKXPm6NtvlFlbj7%2FhelpPageUpdateLocksmithButton.png?alt=media\&token=03fb2ea4-e54e-4f9c-9982-d5ef477cc571)

This will trigger a full reinstall of Locksmith's code into your theme - this is important, because Locksmith is able to do what it does via Liquid code in your shop's theme.

## **Using manual locking?**

{% hint style="warning" %}
**This is important!** If you are using Locksmith for price hiding or other types of manual locking, *or any other type of Locksmith code manually added to your theme by a developer or our team,* you'll need to re-instate the code changes in your new theme.
{% endhint %}

If this is the case, contact us via email at **<team@uselocksmith.com>,** and we'll be happy to add the manual code to your new theme for you.


---

# 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://www.locksmith.guide/faqs/more/i-switched-themes-and-locksmith-isnt-working.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.