You are here: Administrators Reference > Exporting and Importing Objects > Export/Import Scenarios

 

Export/Import Scenarios

In a typical Development server - Authoring server environment you:

  1. Create and test an object on a Development Server.
  2. Export the object.
  3. Import the object to the Authoring Server.

Later, if you change the original object and want to push changes to the site(s) using your object, you would:

  1. Re-export the object from the Development Server
  2. Re-import the object into the sites on your Authoring Server where the object was originally imported.

You might also want to use an object developed by a third-party. In that case, you would:

  1. Download the export packet from the third-party.
  2. Import the object into the desired site(s) on your Development Server.
  3. Test the object.
  4. Import the object into the desired site(s) on your Authoring Server.

Before importing or exporting, please note the following:

ADF (Application Development Framework) Considerations: When importing a Custom Element that includes custom field types or render handlers housed within the ADF, CommonSpot checks to see if the ADF is installed and stops the import if it does not find it. If you are using the CommonSpot Application Development Framework, check that both your web server mapping and the ADF directory are named ADF (all caps).

Path Considerations: Although you can specify any logical path for render handler modules, and export them or Custom Elements containing them to any logical server path, CommonSpot expects import modules to contain site-relative path locations and cannnot properly handle import packets unless the file references they contain are site-relative.

 

Related Links


You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).


For technical support:

http://www.paperthin.com/support/