vREST-API-1.0.6

• Replaced Cascade Server logo with Cascade CMS logo
• Replaced references to Cascade Server with Cascade CMS

vREST-API-1.0.5

• Order of Metadata and Data Definition fields will be preserved from Cascade CMS when adding mappings
• REST requests use Content-Type of application/json

REST API 1.0.4

Fixed displaying field mappings in summary

REST API 1.0.3

Fixed "Overwrite Existing" behavior

REST API 1.0.2

• Fix to get UTF-8 characters to work

• Fixed an issue with moving a page to a folder as index page

REST API 1.0.1

Fixed an issue with XPath test

Universal Migration Tool using REST API 1.0

• The tool now uses REST API. This means that it is not tied to any Cascade CMS version, as long as the version supports REST API (so 8.1.1 and up)
• You can now map an XPath to a "multiple" field. Whenever XPath returns more than one element, each element will be assigned to a separate field. For example, with this HTML:

<ul>
  <li>Item 1</li>
  <li>Item 2</li>
</ul>

and an XPath /ul/li/text() pointing to a "multiple" text field, the tool will create two text fields: Item 1 and Item 2

• If there is a page with the same path as folder, this will not cause an infinite loop anymore. Instead, the page will be created inside of that folder as an index page. All links pointing to the old path will be rewritten to point to the new location of the page. Similarly, relative links in the moved page will get updated during migration to point one level up (so that they end up pointing to the same assets as before).
• If there is already another asset in the site with the same path as folder to be created, this will not cause an infinite loop anymore. Instead, an error will be shown preventing migration. User will need to move or delete the conflicting existing asset in the site and restart migration. Also, fixed an issue with restarting migration, where the tool was reusing previously loaded folder structure, which might be outdated.
• Added ability to test XPaths so that users don't need to run migration just to see if their XPaths work.
• Made it possible to assign the same XPath to more than one field.
• Fixed a number of issues with links pointing to root level folders.
• Made absolute links work and get correctly rewritten during migration.

REST API beta 5

Not populating empty fieldValues #15

Creating a structured data group with no children results in a "null"
error. Preventing this by not pupulating structured data when
fieldValues is an empty list.

Also:
- Moved the XPath test result above tidied XHTML
- Hid the "Back" button from Migration screen, which currently causes
issues with restarting migration

REST API beta 4

vREST-API-beta4

Added static metadata fields

REST API beta 3

Using POST request to avoid issues with Request header too large

... when testing XPath.

Also, outputting the cleanXml if tidy cleans it up.