AutoID changed after saving page

[frankmichel]

I am not sure what's going on here and if this is expected behaviour. I have a blueprint with basically the following fields configuration:

years:
  label: Years
  type: structure
  sortBy: name asc
  sortable: false
  translate: false
  fields:
    name:
      type: text
    autoid:
      type: hidden
      translate: false

events:
  label: Events
  type: structure
  sortBy: name asc
  sortable: false
  translate: false
  fields:
    name:
      type: text
    year:
      type: select
      options: query
      query:
        fetch: page.years.toStructure
        text: '{{ structureItem.name }}'
        value: '{{ structureItem.autoid }}'
    autoid:
      type: hidden
      translate: false

So basically I am using the structure years to populate the options which are available in the events structure. In reality these two structures are on two different tabs, but on the same page. And I think this is part of the problem since the blueprint example is exactly the same, but on two different pages.

So, when I add a year to my years structure and save the page everything looks fine and the content file gets the new values with an autoid:

However, after changing anything else on the same page and then saving the page again (without reloading) the autoid of the previously saved year will be changed behind the scenes. This causes some issues when trying to use the newly created year in the events structure on the same page. A newly created year will be available to be selected as an option, and it will look perfectly when saving the events structure.

But after reloading the page, the year will be empty since the autoid of the year has been changed. I have no idea why the autoid is changing once it has been previously saved. Is there a way to prevent the autoid from being updated/changed once it has been saved?

The autoid has magically changed:

The problem will not occur whenever I do the following:

1. add the year to the years structure
2. save the page
3. reload the panel
4. add an entry with the newly added year to the events structure
5. save the page

[bnomei]

thanks for the detailed issue report. i will take a closer look asap.

does your blueprint have an autoid field at root level. like $page->autoid()?

because if i remember correctly the index depends on each page having that. otherwise it might think the page has not been indexed yet and assign new values. so maybe you can not just have autoids in structures but you need one for the page object as well. BUT i need to verify that.

[frankmichel]

@bnomei Thanks for looking into it! It does have an autoid on root level. I can see it in the content folder .txt file (Autoid: osldmy9g) and I can also var_dump it in the template.