Strange thing is, it seems to be enough that the page.uuid (or also page.uuid.id) is present anywhere in the blueprint ā i.e. in an info field, in the help: prop of any other field and even as a data argument in Bnomeiās Janitor Plugin:
button_copy_id:
type: janitor
command: 'janitor:clipboard --data {{ page.uuid.id }}'
label: 'Copy Page ID to Clipboard'
progress: Copied!
icon: copy
Hi, I encounter the same error but I do not use page.uuid in the bleuprint affected! If this has been solved meanwhile, it would be great to have the solution posted here.
@luca Did you file the issue and where can I find it?
Thank you @texnixe for the link! Meanwhile I analyzed my code and found the page.uuid causing the error in one of my custom models (instead of the blueprint ā¦) where I take the UUID of the page to find out if there are any other pages refering to it (which of course do not with a page currently being created!):
$uuid = $this->uuid()->toString();
Changed it according to @bastianallgeier ās suggestion in the issue mentioned above to:
Hey,
has there been any progress with this? I run into a similar problem with a custom field, where I need the page uuid in some of the props. I used:
$this->model()->uuid()
to get it, which works, but on page creation I get the error message described above and also the page is created AND in addition a second one named new is created.
I tried the workaround but it seems like I donāt get the uuid that way. So I am wondering if there is any chance to access that uuid somehow.
Seems that there was a hickupā¦ I now get the uuid using $this->model()->content()->get('uuid')
keep in mind that this only returns the uuid itself. I was using $this->model()->uuid() which returns page://UUID so you may need to prefix page:// when using the workaround.