# # USERS # Hellonico\Fixtures\Entity\User: user{1..10}: user_login (unique): # '(unique)' is required user_pass: 123456 user_email: user_url: user_registered: first_name: last_name: description: role: meta: phone_number: address: zip: city: acf: facebook_url: twitter_url: # # ATTACHMENTS # Hellonico\Fixtures\Entity\Attachment: default (template): # templates can be extended to keep things DRY post_title: post_date: post_content: images{1..15} (extends default): file: , 1200, 1200, 'cats')> # is required, image() is the default faker provider and gets images from lorempixel. pics{1..15} (extends default): file: , 1200, 1200)> # Alternatively we provide a picsum() provider which uses picsum for images. It's quicker but doesn't support image categories. documents{1..2} (extends default): file: custom_images{1..10} (extends default): file: # # TERMS # Hellonico\Fixtures\Entity\Term: category{1..10}: name (unique): # '(unique)' is required description: parent: '50%? ' # 50% of created categories will have a top level parent category taxonomy: 'category' # could be skipped, default to 'category' tag{1..40}: __construct: ['post_tag'] # This is required to ensure the dynamic parent field above doesn't use tags as possible parents name (unique): # '(unique)' is required description: taxonomy: post_tag places{1..4}: # custom taxonomy name (unique): # '(unique)' is required description: taxonomy: place acf: address: zip: city: image: '@custom_images*->ID' # # POSTS # Hellonico\Fixtures\Entity\Post: # TEMPLATE default (template): post_title: post_date: post_content: post_excerpt: meta: _thumbnail_id: '@attachment*->ID' # POSTS post{1..30} (extends default): # 'meta' and 'meta_input' are basically the same, you can use one or both, # they will be merged, just don't provide the same keys in each definition meta: _thumbnail_id: '@attachment*->ID' meta_input: _extra_field: post_category: '3x @category*->term_id' # post_category only accepts IDs tax_input: post_tag: '5x @tag*->term_id' # post_tag: '5x # Or tags can be dynamically created # PAGES page{contact, privacy}: post_title: post_type: page # CUSTOM POST TYPE product{1..15}: post_type: product acf: # number field price: # gallery field gallery: '3x @attachment*->ID' # oembed field video: https://www.youtube.com/watch?v=E90_aL870ao # link field link: url: https://www.youtube.com/watch?v=E90_aL870ao title: target: _blank # repeater field features: - label: value: value: - label: value: # layout field blocks: - acf_fc_layout: text_image title: content: image: '@attachment*->ID' - acf_fc_layout: image_image image_left: '@attachment*->ID' image_right: '@attachment*->ID' # # COMMENTS # Hellonico\Fixtures\Entity\Comment: comment{1..50}: comment_post_ID: '@post*->ID' user_id: '@user*->ID' comment_date: comment_author: comment_author_email: comment_author_url: comment_content: comment_agent: comment_author_IP: comment_approved: 1 comment_karma: # 'meta' and 'comment_meta' are basically the same, you can use one or both, # they will be merged, just don't provide the same keys in each definition comment_meta: some_key: meta: another_key: # # NAV MENUS # Hellonico\Fixtures\Entity\NavMenu: header: name: header locations: - header - footer # # NAV MENUS ITEMS # Hellonico\Fixtures\Entity\NavMenuItem: custom_menu: menu_item_url: menu_item_title: menu_id: '@header->term_id' categories{1..3}: menu_item_object: '@category*' menu_id: '@header->term_id' posts{1..3}: menu_item_object: '@post*' menu_id: '@header->term_id' page: menu_item_object: '@page*' menu_id: '@header->term_id'