Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Recursion problem with fieldsets

未关闭
#12,698 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
laravel, php
领域
backend

调研方向

Start by reproducing the linked-fieldset chain described in the issue: Block Constructor → Page Section → Page Tabs → Page Section. The issue does not identify files or tests, so trace fieldset linking from that reproduction and determine where the server failure occurs. Done means the recursive setup no longer causes a 502 or server crash; whether recursion itself must be supported remains unclear.

由索引模型根据 Issue 内容生成。

描述

blueprints & fieldsets
Bug description

Hello. There is an issue with the recursive use of Fieldsets. I need to familiarize you with the context of CMS usage so that you understand the problem.

Our goal is to create a block constructor in collections. To do this, we use fieldsets:

  • Block constructor
  • Page Section
  • Page Title
  • Page Text
  • Page Tabs

etc...

Block constructor is the main fieldset that includes the main sections, with Page Section as the priority. Page Section uses a grid to build columns and a replicator to build content in columns (Page Text, Page Title, etc.).

The problem arises when I try to recursively connect Page Section to Page Tabs in order to use it to build content within the component. Immediately after saving such a change, the server crashes and the database needs to be restored.

It would be great to implement recursion so that fieldsets could be reused. However, it would be enough to at least avoid Bad Gateway behavior.

How to reproduce

Chain:
Collection ->
Blueprint ->
Linked Fieldset: Block Constructuror (replicator) ->
Linked Fieldset: Page Section (grid -> replicator) ->
Linked Fieldset: Page Tabs (grid -> replicator) ->
Linked Fieldset: Page Section

Logs
502 Bad Gateway
Environment
Application Name: Laravel
Laravel Version: 12.32.5
PHP Version: 8.4.11
Composer Version: 2.8.10
Environment: local
Debug Mode: ENABLED
URL: localhost
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: database
Database: pgsql
Logs: stack / single
Mail: log
Octane: swoole
Queue: redis
Session: database

Storage
public/storage: NOT LINKED

Statamic
Addons: 7
Sites: 4 (English, Spanish, Ukrainian, Portuguese)
Stache Watcher: Disabled
Static Caching: Disabled
Version: 5.66.0 PRO

Statamic Addons
appswithlove/statamic-one-click-content-translation: 5.2.3
daun/statamic-widget-collection-count: 1.3.3
doefom/statamic-export: 0.6.5
mitydigital/statamic-two-factor: 2.7.2
sortarad/extraextra: 1.0.1
statamic/eloquent-driver: 4.32.0
teamnovu/statamic-unused-assets: 2.0.2

Statamic Eloquent Driver
Asset Containers: eloquent
Assets: eloquent
Blueprints: eloquent
Collection Trees: eloquent
Collections: eloquent
Entries: eloquent
Fieldsets: eloquent
Form Submissions: eloquent
Forms: eloquent
Global Sets: eloquent
Global Variables: eloquent
Navigation Trees: eloquent
Navigations: eloquent
Revisions: eloquent
Sites: eloquent
Taxonomies: eloquent
Terms: eloquent
Tokens: eloquent
Installation

Existing Laravel app

Additional details

No response

主要语言
PHP
星标
4.9k
派生
647
平均合并
1 天 8 小时
30 天内合并 PR
100

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

statamic/cms 的其他 Issue

查看 statamic/cms 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。