Problem
When using drush commands from the SKILL.md skills (dxt, dxb) in a multisite environment, the commands default to the sites/default database instead of the intended site.
Current Behavior
Running drush dxb:page:update 6 --markup=@/tmp/file.html from the project root edits node 6 on the default site, not the intended multisite (e.g., hengelaars.test).
The user must either:
cd into web/sites/{sitename} before running drush
- Or use
--uri=http://sitename.test (which doesn't always work reliably)
Suggested Solution
Update the SKILL.md files to:
- Document the multisite context requirement clearly
- Consider adding a
--site or --uri parameter reminder in command examples
- Potentially add site detection/validation before running commands
Example Scenario
# This edits the WRONG site (default)
drush dxb:page:update 6 --markup=@/tmp/homepage.html
# This is the correct approach
cd web/sites/hengelaars.test
../../../vendor/drush/drush/drush dxb:page:update 6 --markup=@/tmp/homepage.html
Environment
- DXPR CMS multisite setup
- Multiple sites in
web/sites/ directory
- Using Valet or similar local development environment
🤖 Generated with Claude Code
Problem
When using drush commands from the SKILL.md skills (dxt, dxb) in a multisite environment, the commands default to the
sites/defaultdatabase instead of the intended site.Current Behavior
Running
drush dxb:page:update 6 --markup=@/tmp/file.htmlfrom the project root edits node 6 on the default site, not the intended multisite (e.g.,hengelaars.test).The user must either:
cdintoweb/sites/{sitename}before running drush--uri=http://sitename.test(which doesn't always work reliably)Suggested Solution
Update the SKILL.md files to:
--siteor--uriparameter reminder in command examplesExample Scenario
Environment
web/sites/directory🤖 Generated with Claude Code