Local extensions are not installed
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- php
- Domain
- documentation
Research direction
Start with the extensions testing documentation at the linked Phase 1 page, then inspect the local extension layout, config.yml, and the referenced menuchain composer.json. Reproduce whether extensions/local/designspike/menuchain is detected; the documentation is done when it describes every required step for a local extension to appear as installed and expose its methods.
Written by the indexing model from the issue text.
Description
Hi, first of all thanks for making this awesome CMS! So I am trying to write an extension, and the documentation says:
in any Bolt site you can put local extensions within extensions/local/{author_name}/{extension_name}
(this is at https://docs.bolt.cm/3.6/extensions/basics/testing#phase-1-develop-your-extension-within-a-bolt-project)
However, there is probably something else to do, because Bolt does not seem to pick up the extension (it does not appear as an installed extension on the extensions page, and calling extension methods fail).
I did change the minimum-stability to dev in config.yml
And to exclude a problem with the extension itself, I downloaded a known-working extensions from github (https://github.com/designspike/bolt-extension-menuchain) and I renamed the directories so that the extension is in extensions/local/designspike/menuchain, as suggested in the docs above:
gpothier@tadzim4:~/myboltroot$ ls extensions/local/designspike/menuchain/
composer.json README.md src
The documentation doesn't mention any additional step for this to work. What am I missing?
- Dominant language
- PHP
- Stars
- 45
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bolt/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
-
Outdated Roadmap link in `https://docs.boltcms.io/other/contributing#step-2-rfc-moved-to-roadmap`Open
Difficulty 1/5 Under an hour Newbie friendliness 50/100
Similar issues
-
needs-maintainer-review review:approve
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Ultimate-Multisite/ultimate-ai-connector-compatible-endpoints#163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agentic documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MagnaCapax/PMSS#981 ·
Maintainers usually reply within 5 days