Can't create new taxonomy term in non-active site
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the issue using the steps in the report: create a multisite taxonomy, set its field to Stack Selector, then try creating a term for the first site while viewing the second site in the CP. Start by examining the error shown in the attached screenshot or video and trace the term-creation flow from there. Done means the term can be created for the selected site without an error.
Written by the indexing model from the issue text.
Description
Bug description
If you have a multi-site (A & B) and you're in site B (in the CP), and an entry has a stack selector terms field, you can't pick site A to create the new term in.
Confusing I know, sorry, hopefully the video is clear
https://github.com/user-attachments/assets/53faf3e2-068e-4748-8340-0c2d0a723de1
How to reproduce
- create site
- make multisite
- make taxonomy,
Categoriesthat's in both site - change the pages blueprint and set the categories field to Stack Selector
- Set the site to the second site
- open home page in the cp
- click create on the categories field
- click the first site
See error
Logs
Environment
Environment
Application Name: Statamic
Laravel Version: 12.19.3
PHP Version: 8.3.22
Composer Version: 2.8.9
Environment: local
Debug Mode: ENABLED
URL: terms.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file
Storage
public/storage: NOT LINKED
Statamic
Addons: 0
Sites: 2 (Statamic, Second)
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.57.0 PRO
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
- Dominant language
- PHP
- Stars
- 4.9k
- Forks
- 647
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 113
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 statamic/cms
-
preferences
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
accessibility
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
[7.x] Reintroduce parser error for mixed pipe/shorthand modifier syntaxPossibly taken A pull request linked to this issue is open or already merged. Openantlers
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
navigations
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 4 days
-
Перевод устарел
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Adapter: Algolia Performance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100