# Composer Footnote Button **URL:** https://meta.discourse.org/t/composer-footnote-button/243487 **Category:** Theme component **Tags:** footnote, end-of-life **Created:** [November 1, 2022, 12:58am UTC](https://meta.discourse.org/t/composer-footnote-button/243487 "2022-11-01T00:58:21Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![denvergeeks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/denvergeeks/32/327671_2.png) [@denvergeeks](https://meta.discourse.org/u/denvergeeks) #### Post date: [September 19, 2024, 7:48pm UTC](https://meta.discourse.org/t/composer-footnote-button/243487/5 "2024-09-19T19:48:37Z")
Hi @Don! There appears to be an error with this theme component… ![This image depicts a computer screen displaying a code editor with a Python script, featuring a code snippet for a Flask web application, likely for a "Discourse Composer" feature, with various tokens and footnote buttons. (Captioned by AI)](https://global.discourse-cdn.com/meta/original/4X/5/c/f/5cf6ee5719eed058e7fe4dfc04442af65240fa2c.png) … which it seems might be resolved as advised here… > [@Using modifyClass to change core behavior](https://meta.discourse.org/t/using-modifyclass-to-change-core-behavior/262064): > > For advanced themes and plugins, Discourse offers the modifyClass system. This allows you to extend and override functionality in many of core’s javascript classes. When to use modifyClass modifyClass should be a last resort, when your customization cannot be made via Discourse’s more stable customization APIs (e.g. plugin-api methods, plugin outlets, transformers). Core’s code can change at any time. And therefore, customizations made via modifyClass could break at any time. When using this A… --- _[View the full topic](https://meta.discourse.org/t/composer-footnote-button/243487)._