Open pReya opened 2 years ago
how exactly did you setup the generator? the seed is expected by default to start with 0
. the created .autoid
file will store the most recent used id.
are there any other autoid fields that might get set (to the value 1) before the structure is parsed?
I tried this again, to make sure this is not due to another plugin or my complicated blueprints, but I can recreate it, even with a plainkit setup. So I'm pretty sure this is actually a bug. How to reproduce:
default.yml
title: Default Page
preset: page
fields:
text:
label: Text
type: textarea
size: large
mydata:
label: Addresses
type: structure
translate: false
fields:
firstname:
label: First Name
type: text
lastname:
label: Last Name
type: text
Add new entry to structure via the panel, so content file looks something like this:
Title: Test
----
Text: asd
----
Mydata:
-
firstname: Michael
lastname: Meyers
config.php
'bnomei.autoid.generator' => function () {
return (new \Bnomei\IncrementingGenerator(0))->generate();
},
autoid
field to blueprint:
title: Default Page
preset: page
fields:
text:
label: Text
type: textarea
size: large
mydata:
label: Addresses
type: structure
translate: false
fields:
autoid:
type: hidden
translate: false
firstname:
label: First Name
type: text
lastname:
label: Last Name
type: text
Autoid in content file starts with "2"
Title: Test
----
Text: asd
----
Mydata:
-
autoid: "2"
firstname: Michael
lastname: Meyers
-
autoid: "3"
firstname: Peter
lastname: Mueller
I used the Autoid on otherpages with the regular generator but on the homepage I use the increment generator and it starts by 14. I have no clue if the generator switch is a problem.
This is a minor bug, but it's annoying because the AutoIDs don't match the default row enumerations in the Kirby panel for structure fields.
To reproduce:
IncrementingGenerator
type: autoid
to an existing structure field