Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Bruno Meilick
@bnomei
hello world
Fabian
@fdnklg
@bnomei Hi Bruno, is there a way to store the created auto Ids within the content txt files? Right now my autoid field just stays empty..
Bruno Meilick
@bnomei
hi @fdnklg
which version of autoid plugin are you using? i recently updated it to v2.
with default settings of plugin the autoid field should be created in the content file (the txt file) if any hook is triggered (create/update).
Fabian
@fdnklg
I'm using the current version (downloaded the zip file from your github repository). Is there a way to check if one of the hooks is triggered? I added the keys to the blueprint but the key in the content stays empty.
Bruno Meilick
@bnomei
the blueprint work fin in the panel? can you post the relevant parts of the blueprint?
Bruno Meilick
@bnomei
i just verified with a plainkit and current zip. i used type: autoid and it seemed to work fine
Bruno Meilick
@bnomei
ohmy. gitter seems to remove spaces.
Fabian
@fdnklg
title: Institution
pages: false
files: true
options:
  preview: false
fields:
  institution:
    label: Institution
    type: structure
    columns: 
      name: 
        width: 3/6  
      category: 
        width: 3/6  
    fields:

      autoid:
        type: autoid
        translate: false 

      introHeadline:
        label: Kontakt
        type: headline
Bruno Meilick
@bnomei
tada
Fabian
@fdnklg
I'll try to reproduce it with a plain starter kit, thank you anyway for your response!
Bruno Meilick
@bnomei
i am sorry. i removed the structure support for v2 but if you use the zip with v1.4.1 you should be fine
Fabian
@fdnklg
Ah, okay! Why so?
Bruno Meilick
@bnomei
different reasons. how detailed description do you want? :D
Fabian
@fdnklg
Haha, was just curious because it's a neat feature to mee
Bruno Meilick
@bnomei
i removed it because i never needed it other than for fake pages which did not go well in most cases in the end. it creates a hellish codebase for the plugin.
care to explain what relation exactly you setup with the autoid in the structures?
Fabian
@fdnklg
Okay, I'm using kirby as a headless cms and need unique ids for my content type.
with v1.4 autoid equals null for all items. Maybe i have to find another workaround
Bruno Meilick
@bnomei
if you can avoid structures it might be better in the long run. why excatly do you use structures not page objects?
hm. v1.4 should haven be pretty stable. if you create an issue with detailed errors. i can take a look later. need to leave chat now for a while.
Fabian
@fdnklg
My institution structure field contains lots of different nested other content fields like, other structured fields, multi selects and others..
is it possible to handle all of this within a page object?
Bruno Meilick
@bnomei
imho you can swap any structure for a pages-collection. but with headless you would have to recreate the nice array that structures give you. that might be a hassle if you dont want to. personally i would create pages only and use custom pagemethods to recreate the array that the structures had. if you create an issue with some blueprints i could draft some rough setup.
:wave: need to leave now. see ya later.
Fabian
@fdnklg
thanks, see you!