JS API - getAttributes content_type_nest_content

(Chris Horikx) #1

Hi Guys,

 

Trying to work with JS API replacing content in divs, primarily asset ids in content and nested content.

 

On a nested content div type, using getAttributes, it seems I can get every field apart from the selected nested asset - the most important field!

getAttributes =>

{
  "html": "",
  "name": "DIV Content",
  "paint_with": "raw",
  "additional_get": [
    {
      "name": "topic",
      "value": "commercial_fishing"
    }
  ],
  "dynamic_nest_get": ""
}

The same occurs on asset listings root nodes, it doesn't show in attributes: 

getAttributes =>

{
  "customised": [],
  "statuses": [
    "2",
    "4",
    "8",
    "16",
    "32",
    "64",
    "128",
    "256"
  ],
  "list_effective": "1",
  "submit_button_text": "Submit",
  "sort_by": [
    {
      "params": {
        "field": ""
      },
      "type": "",
      "name": "No Sorting"
    }
  ],
  "default_sort_by": "0",
  "direction": "down",
  "a_z_style": "multiple",
  "name": "Demos",
  "a_z_letter_format": " <h3> %letter_group% </h3> ",
  "exclude_assets": [],
  "column_layout_type": "table",
  "asset_positions": [],
  "lineage_seperator": " > ",
  "root_in_lineage": "0",
  "prev_page_text": "Previous",
  "link_types": "1",
  "asset_selections": [],
  "structured_dropdown_options": {
    "name": "root_node_selection",
    "all_text": "All",
    "root_node": "0",
    "asset_types": [],
    "max_depth": "0",
    "height": "0",
    "width": "0",
    "seperator": "-"
  },
  "form_submit_method": "get",
  "min_depth": "",
  "max_depth": "",
  "submit_to_page_url": "1",
  "proxy_types": [],
  "page_link_format": " <a href=\"%page_link%\">%page_number%</a> ",
  "current_page_format": " %page_number% ",
  "start_position": "0",
  "hide_no_href_links": "0",
  "types": {
    "page": "1",
    "folder": "0",
    "file": "1",
    "page_redirect": "0",
    "image": "0"
  },
  "exclude_root_nodes": [],
  "exclude_current_asset": "0",
  "list_permission": "1",
  "reset_button_text": "Reset",
  "other_page_text": "[Other]",
  "metadata_sort_type": "presentation",
  "reverse_sort": "0",
  "sort_direction_asc_text": "Ascending",
  "sort_direction_desc_text": "Descending",
  "subs_only": "1",
  "group_by": "number",
  "num_per_page": "0",
  "column_layout": [
    "1"
  ],
  "div_row_class": "",
  "self_in_lineage": "0",
  "next_page_text": "Next",
  "parameter_map": "a:1:{s:9:\"root_node\";a:1:{i:0;a:3:{s:6:\"source\";s:5:\"ASSET\";s:9:\"attribute\";s:7:\"assetid\";s:7:\"keyword\";s:13:\"asset_assetid\";}}}",
  "asset_grouping": [],
  "all_root_nodes": "0",
  "asset_targets": [],
  "link_value_filter": "",
  "link_value_filter_enabled": "0",
  "check_boxes": "0",
  "link_value_filter_logic": "1",
  "dynamic_asset_selection_option": "static_root",
  "dynamic_root_option": "static_root",
  "short_name": "Demos"
}

Is there a reason that field was left out?

 

 

(Chris Horikx) #2

If anyone is interested, I've been able to get this working - so far - on asset listings by creating a notice link such as this:

js_api.createLink({

“parent_id”:<!-- id of asset listing -->,

“child_id”:<!-- id of root -->,

“link_type”:8,

“link_value”:“root”,

“sort_order”:1,

“is_dependant”:0,

“is_exclusive”:0,

“dataCallback”:function(data){console.log(JSON.stringify(data))}

})

 

It looks like creating links with appropriate link values will allow me to create a root node, or redirect etc.
 
I had tried this prior to writing the original topic but must have got something wrong. 
(Bart Banda) #3

Cool, I think that's also what the nested asset content container uses for the asset it's linking to? A link value rather than an attribute?