> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/button/troubleshooting-buttons.md).

# Troubleshooting Buttons

If PixieBrix doesn't find the right button, you have a few options

You can try the more advanced route of trying to select a CSS selector by hand. This however requires you to be able to somehow place a button anywhere on the page, even if it’s not in your desired location. Then to change the button placement, you will have to tweak the ***Location*** (under the button’s configuration) and the ***Template*** (under Advanced)

> *Sometimes however none of this works, that’s when we suggest to simply try another starter brick as mentioned above, either a Quick Bar or a Context Menu*

### Troubleshooting Buttons

Here are some things you can try if you have problems adding buttons.

**Option 1: While placing a button, press the Shift key**

Try clicking around in different areas of the page while holding down the **Shift** key. To see this in action, watch the [Advance Button Placement and Alternatives](https://www.loom.com/share/343fa92f9cd846eaba38046220e470fe) video.

**Option 2: Use the CSS Selector manually**

You can also try using the [CSS selector](https://www.w3schools.com/cssref/css_selectors.php) manually. First, place the button anywhere on the page, even if it’s not your desired location. Then, you may tweak the CSS in the **Location** field and the code in the **Template** \*\*field.

**Option 3: Use a different extension**

If all else fails, you can use a [Context Menu](https://www.notion.so/Creating-and-Configuring-a-Context-Menu-Item-12e0fa2a29a049c38d266c6841253c16?pvs=21) or a [Quick Bar](https://www.notion.so/Creating-and-Configuring-a-Quick-Bar-Action-29e4099c921f401ab5f888a06c266ae9?pvs=21) instead of a button. The look will be different, but the functionality will be the same.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pixiebrix.com/developing-mods/developer-concepts/types-of-mods/button/troubleshooting-buttons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.