Possible Bug: Structure not sortable when in block's edit panel?

The CMS Questions
1

I have a blueprint with a Blocks field, and one of the blocks has a Structure field. Sorting does not work when editing the block, even though the table has the draggable/sortable classes. There’s another Structure in the blueprint outside of the blocks field which works fine (screenshot below, left side is working but right side is missing the draggable button in the table cell). Seems like maybe the draggable js is not firing for that field when it’s in the block’s panel. Other sortable fields like Files work fine though. Has anyone run into this?

CleanShot 2025-03-06 at 14.42.55
CleanShot 2025-03-06 at 14.42.551686×473 160 KB

2

And the field definitions for both structure field (inside and outsite the block are identical), please post blueprint definitions. And your Kirby version.

3

v4.6.1
Here’s the outer definition defined in site/blueprints/pages/default.yml (ignore the tabbing):

hero:
  type: fields
  fields:
          ...
          words:
            label: Fading Words
            type: structure
            width: 1/2
            help: The first word should match the bolded Heading word
            fields:
              word:
                type: text
content:
    type: fields
        fields:
          pageBuilder:
            type: blocks
            label: Sections
            fieldsets:
              - project
              - splitLayout
              - logoGrid
              - textOnly
              - testimonials
              - divider

And the definition for the testimonials fieldset defined in sites/blueprints/blocks:

type: testimonials
icon: quote
fields:
  testimonials:
    type: structure
    limit: 8
    columns:
      name: true
      company: true
    fields:
      name:
        type: text
      title:
        type: text
        width: 1/2
      company:
        type: text
        width: 1/2
      quote:
        type: textarea
        buttons: false

Interestingly, I just tried removing the limit on the testimonials definition and that does fix the issue. Moving the limit to the words definition and it breaks sorting there. So maybe if pagination is in play sorting is disabled?

4

Indeed that’s the reason looking at kirby/panel/src/components/Forms/Field/StructureField.vue at main · getkirby/kirby · GitHub

I vaguely recall that there were really difficult edge cases to solve sorting when in a paginated structure field and not on page 1. Which is why we probably decided to disable it then. As sorting across pages wouldn’t be possible, there would be little value for sorting within a pagination page, I would think.

5

Ah, so actually it’s a skill issue: I should have used max and not limit. I want to prevent the client from adding too many items and saw limit first without considering that was for pagination. Switching the blueprint to max solves this.