Project config sync not applying single's changed template path
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Description
A change to a single section's template path setting isn't applied by project config sync. The specific change I noticed this with was adding an underscore prefix to the path.
Steps to reproduce
- In one environment, change a single's template setting from "my-section/_entry" to "_my-section/entry" (or probably any other change, the prefix change is what I was doing when I hit this bug.
- Push the change up to a remote environment
- See that the project config file on the remote environment has the updated template path
- Run project config sync on the remote environment
- See that the section's template has not changed on the remote environment
Additional info
I'm not on the latest version. Not seeing anything about this in later versions' changelog notes. There's a lot going on with this particular site I'm holding off on upgrading for the moment, but can if you expect that'll address the problem.
I have not run sync with --force yet in case there's anything I can do first to help diagnose the problem.
Possibly this is #6160?
- Craft version: 3.4.20
- PHP version: 7.2.24
- Database driver & version: MySQL 5.7.29
- Plugins & versions:
| Advanced Url Field | 1.0.0 |
|---|---|
| Amazon S3 | 1.2.8 |
| Analytics | 4.0.10 |
| Asset Rev | 6.0.2 |
| Control Panel Nav | 3.0.12 |
| Cookies | 1.1.12 |
| CP Field Inspect | 1.1.3 |
| Element Map | 1.2.1 |
| Embedded Assets | 2.2.4 |
| Entry Instructions | 1.0.7 |
| Environment Label | 3.2.0 |
| Expanded Singles | 1.1.2 |
| Field Manager | 2.1.6 |
| Flat Categories | 2.0.0 |
| Image Resizer | 2.0.8 |
| Inventory | 2.1.0 |
| Matrix Colors | 2.0.1 |
| Password Protect | 1.0.0 |
| Redactor | 2.6.1 |
| Redirect plugin for Craft 3 | 1.0.23 |
| SuperSort | 3.0.1 |
| Super Table | 2.4.9 |
| Twig Perversion | 2.1.0 |
| Video Embed | 1.2.1 |
Contributor guide
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.
Research direction
Start by reproducing the project config sync flow with a single whose template path changes from "my-section/_entry" to "_my-section/entry". Compare the project config and the single after synchronization; done when the changed template path is applied on the remote environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100