UpdatePageInputType

No description

type UpdatePageInputType {
  authorization_policy_ids: [ID]
  content: String
  deleted_at: JSONDate
  dynamic_cache_expire: Int
  dynamic_cache_key: String
  dynamic_cache_layout: Boolean
  format: PageFormat
  handler: PageHandler
  layout: String
  layout_name: String
  manually_managed: Boolean
  max_deep_level: Int
  metadata: HashObject
  physical_file_path: String
  redirect_code: PageRedifectCode
  redirect_to: String
  request_method: PageRequestMethod
  response_headers: HashObject
  searchable: Boolean
  slug: String
  static_cache_expire: Int
}

Fields

authorization_policy_ids (ID)

ids of authorization policies which should be checked

content (String)

deleted_at (JSONDate)

dynamic_cache_expire (Int)

dynamic_cache_key (String)

dynamic_cache_layout (Boolean)

format (PageFormat)

handler (PageHandler)

layout (String)

name of the liquid layout to which the content should be injected

layout_name (String)

deprecated, use layout

manually_managed (Boolean)

defines whether this object will be manually managed, meaning it will not be affected via pos-cli deploy / sync

max_deep_level (Int)

max nesting of the url to be resolved by this slug. For example slug "abc"
with max_deep_level 2 will resolve /abc, abc/1, abc/2, but will NOT resolve
abc/2/something.

metadata (HashObject)

physical_file_path (String)

defines where the file definition will be available after pull; should start
with the module name follow by private/public scope, for example
manual/public/views/pages/my-page

redirect_code (PageRedifectCode)

redirect_to (String)

request_method (PageRequestMethod)

response_headers (HashObject)

searchable (Boolean)

slug (String)

slug will not be automatically if you modify physical_file_path, as this
operation is dangerous. After changing the slug you might want to ensure the
SEO will not be hurt by creeating Page with the old slug and setting the
redirect_to property to the new path.

static_cache_expire (Int)