Closed diogovitzo closed 7 months ago
What does your Posts
blueprint look like?
title: Posts
tabs:
main:
display: Main
sections:
-
fields:
-
handle: title
field:
type: text
required: true
validate:
- required
localizable: true
-
handle: image
field:
mode: grid
container: assets
restrict: false
allow_uploads: true
show_filename: true
max_files: 1
display: Image
type: assets
instructions: 'Will be displayed as featured image on post, and used as post thumbnail.'
listable: hidden
validate:
- required
localizable: false
-
handle: article
field:
always_show_set_button: false
sets:
image:
display: Image
fields:
-
handle: image
field:
mode: grid
container: assets
restrict: false
allow_uploads: true
show_filename: false
max_files: 1
display: Image
type: assets
icon: assets
listable: hidden
validate:
- required
image_grid:
display: 'Image Grid'
fields:
-
handle: image_grid
field:
options:
two: 'Two Columns'
three: 'Three Columns'
four: 'Four Columns'
default: two
display: 'Image Grid'
type: button_group
icon: button_group
instructions: 'Select grid columns, default is two.'
listable: hidden
-
handle: images
field:
mode: grid
container: assets
restrict: false
allow_uploads: true
show_filename: true
display: Images
type: assets
icon: assets
instructions: 'Displays images in a grid'
listable: hidden
validate:
- required
video:
display: Video
fields:
-
handle: video
field:
display: Video
type: video
icon: video
instructions: 'Youtube or Vimeo Link'
listable: hidden
buttons:
- h2
- h3
- bold
- italic
- unorderedlist
- orderedlist
- removeformat
- quote
- anchor
container: assets
save_html: false
toolbar_mode: fixed
link_noopener: false
link_noreferrer: false
target_blank: false
reading_time: false
fullscreen: true
allow_source: false
enable_input_rules: true
enable_paste_rules: true
display: Article
type: bard
listable: hidden
localizable: true
-
handle: one_click_content_translation
field:
display: 'One-click Content Translation'
type: one_click_content_translation_inputs
listable: hidden
visibility: hidden
localizable: false
sidebar:
display: Sidebar
sections:
-
fields:
-
handle: slug
field:
type: slug
localizable: false
validate:
- required
instructions_position: above
listable: hidden
visibility: visible
replicator_preview: true
generate: false
show_regenerate: false
hide_display: false
-
handle: date
field:
type: date
required: true
default: now
validate:
- required
localizable: false
-
handle: author
field:
max_items: 1
mode: select
display: Author
type: users
listable: hidden
localizable: false
-
handle: category
field:
max_items: 1
mode: select
create: true
taxonomies:
- categories
display: Category
type: terms
listable: hidden
localizable: false
-
handle: tags
field:
display: Tags
type: taggable
listable: hidden
localizable: false
seo:
display: SEO
sections:
-
fields:
-
import: seo
custom_code:
display: 'Custom Code'
sections:
-
fields:
-
handle: custom_code_in_head
field:
theme: light
mode: htmlmixed
mode_selectable: true
indent_type: tabs
indent_size: 4
key_map: default
line_numbers: true
line_wrapping: true
antlers: false
type: code
display: 'Before </head>'
instructions: |-
Accepts all sorts of code. Doesn't validate it. Use with caution.
If there's GLOBAL custom code, this code will run AFTER.
localizable: false
listable: hidden
instructions_position: above
visibility: visible
replicator_preview: true
hide_display: false
-
handle: custom_code_in_body
field:
theme: light
mode: htmlmixed
mode_selectable: true
indent_type: tabs
indent_size: 4
key_map: default
line_numbers: true
line_wrapping: true
antlers: false
type: code
display: 'Before </body>'
instructions: |-
Accepts all sorts of code. Doesn't validate it. Use with caution.
If there's GLOBAL custom code, this code will run AFTER.
localizable: false
listable: hidden
instructions_position: above
visibility: visible
replicator_preview: true
hide_display: false
Hmm, that seems to be working fine for me. 🤔
What does your seo
fieldset look like? Also, do you get a more helpful error message if you disable xdebug?
I ended up just increasing xdebug's max nesting level. Not ideal, but I also don't believe that this is an "infinite loop" as the stack trace only shows signs of a possible infinite loop between trace #2 and ~#25, but that's just the nature of the parser.
Sorry for taking your time.
No worries - I'll close this issue now. 👍
Bug description
I was running version 4.45.0 and everything was working fine.
After upgrading to 4.51.0, I started having issues when:
The issue that occurs is:
How to reproduce
As in title, but please ask for details if needed.
Logs
Environment
Installation
Starter Kit using via CLI
Antlers Parser
None
Additional details
No response