PT Photo Gallery Import - Revision history

Dbeckstrom: /* Verify Imports */

2010-04-14T17:16:00Z

‎Verify Imports

Dbeckstrom: /* Verify Imports */

2010-04-14T17:06:15Z

‎Verify Imports

Dbeckstrom: /* Verify Imports */

2010-04-14T17:05:37Z

‎Verify Imports

Dbeckstrom: /* Verify Imports */

2010-04-14T17:04:45Z

‎Verify Imports

Mcarroll: /* Import */

2010-04-08T16:11:40Z

‎Import

Mcarroll: /* Import */

2010-03-31T14:22:02Z

‎Import

Mcarroll at 14:21, 31 March 2010

2010-03-31T14:21:48Z

Mcarroll at 18:38, 26 March 2010

2010-03-26T18:38:20Z

Mcarroll: moved Import Photo Gallery Components to PT Photo Gallery Import

2010-03-24T23:21:39Z

moved Import Photo Gallery Components to PT Photo Gallery Import

Renee.mckechnie at 23:40, 20 December 2009

2009-12-20T23:40:04Z

@@ Line 31: / Line 31: @@
 If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.
-Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, delete the new imported field from the list of custom field types.
+Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. Note that when you assign the existing general chooser you will need to click on the "properties" tab and enter "photoSizeGC" as the bean name.  After reassigning the field type, delete the new imported field from the list of custom field types.
 [[Category:Photo Gallery]]

@@ Line 27: / Line 27: @@
 The imported components' render handlers and custom field types must be verified.  During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path.
-Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview|custom field types that were imported]] with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
+Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview#Contents|custom field types that were imported]] with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.

@@ Line 27: / Line 27: @@
 The imported components' render handlers and custom field types must be verified.  During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path.
-Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview|custom field]] types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
+Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview|custom field types that were imported]] with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.

@@ Line 27: / Line 27: @@
 The imported components' render handlers and custom field types must be verified.  During the import process, the render handler and custom field types paths may have been changed to reflect the current site's path.
-Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
+Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the [[PT_Photo_Gallery_Overview|custom field]] types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.

@@ Line 18: / Line 18: @@
 # PhotoSizeRender (PhotoSizeRender-Metadata-Form.zip)
-## Bind this form to the Photo Gallery Listing Display Render Handler
+## Bind this form to the following Photo Gallery Render Handler
 == Verify Imports ==

@@ Line 17: / Line 17: @@
 Import Metadata form:
-*PhotoSizeRender (PhotoSizeRender-Metadata-Form.zip)
+# PhotoSizeRender (PhotoSizeRender-Metadata-Form.zip)
-**Bind this form to the Photo Gallery Listing Display Render Handler
+## Bind this form to the Photo Gallery Listing Display Render Handler
 == Verify Imports ==

@@ Line 4: / Line 4: @@
 To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information.
 Import Custom Elements in this order:
@@ Line 18: / Line 20: @@
 **Bind this form to the Photo Gallery Listing Display Render Handler
-During the installation, import all portions of the components.
+== Verify Imports ==
-'''Important Note:'''
+Review and update these paths to reference the ADF path.  In most cases, this will just require to be unlocked and a change in the path from the site name to 'ADF'.  Check the paths for the custom field types that were imported with the custom elements by unlocking them and fixing the explicit paths to point to "/ADF/extensions/".
 If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.

← Older revision		Revision as of 18:38, 26 March 2010
Line 1:		Line 1:
−	The Photo Gallery Application has several Custom Components defined within CommonSpot. The components have been exported and are available in the Photo Gallery's "exported-objects" folder located at the root of the ~~Profile~~ application directory (e.g. /ADF/apps/pt_photo_gallery/exported-objects/)	+	The Photo Gallery Application has several Custom Components defined within CommonSpot. The components have been exported and are available in the Photo Gallery's "exported-objects" folder located at the root of the Photo Gallery application directory (e.g. /ADF/apps/pt_photo_gallery/exported-objects/)

	Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Photo Gallery Elements'.		Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Photo Gallery Elements'.

← Older revision	Revision as of 23:21, 24 March 2010
(No difference)

@@ Line 1: / Line 1: @@
 The Photo Gallery Application has several Custom Components defined within CommonSpot. The components have been exported and are available in the Photo Gallery's "exported-objects" folder located at the root of the Profile application directory (e.g. /ADF/apps/pt_photo_gallery/exported-objects/)
-Optional: You may want to create a new category for 'Photo Gallery Elements'.
+Optional: You may want to create a new category within the CommonSpot Element Gallery for 'Photo Gallery Elements'.
-To import these objects you will need to be an administrator for your site. If you are not, please consult your Server administrator for more information.
+To import these objects, you will need to be an administrator for your site. If you are not a site administrator, consult your Server administrator for more information.
-Import Custom Elements: (please import in the order stated)
+Import Custom Elements in this order:
 # Photo (Photo-Custom-Element.zip)
@@ Line 13: / Line 13: @@
 # PTPhotoGallery Configuration (PTPhotoGallery-Configuration-Custom-Element.zip)
-Import Metadata:
+Import Metadata form:
 *PhotoSizeRender (PhotoSizeRender-Metadata-Form.zip)
-**Bind this form to the Photo Gallery Listing Display RH
+**Bind this form to the Photo Gallery Listing Display Render Handler
-Note: During the installation, import all portions of the components.
+During the installation, import all portions of the components.
 '''Important Note:'''
-The imported components render handlers and custom field types must be verified.  During the import process the render handler paths may have been changed to reflect the current sites path.  Review and update these paths to reference the ADF path.  In most cases, this will just require a change in the path from the site name to 'ADF'.  Custom field types will need to be unlocked.
+The imported components render handlers and custom field types must be verified.  During the import process the render handler paths may have been changed to reflect the current site's path.  Review and update these paths to reference the ADF path.  In most cases, this will just require a change in the path from the site name to 'ADF'.  Custom field types will need to be unlocked.
 '''Important Note 2:'''
-If the custom elements that are imported contain custom field types that are already on the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.
+If the custom elements that are imported contain custom field types that are already in the site, the naming convention for the custom field type will be unique.  To resolve this, unlock the field types and elements, and reassign the element field type to the pre-existing field type.
-Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new naming convention. The new name will be something like "General Chooser_import_1250003208472". To resolve this, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, you can delete the new imported field from the list of custom field types.
+Example: The Photo Category custom element contains two uses of the General Chooser field type, if the General Chooser field type is already installed on the site then the import process will attempt to import another General Chooser but with a new name such as "General Chooser_import_1250003208472." To resolve this issue, open the custom element and assign the field type (General Chooser_import_1250003208472) to the field type with the simple name General Chooser. After reassigning the field type, delete the new imported field from the list of custom field types.