1. Issue:
A “Could not load file or assembly Personify.SitecoreConnector or one
of its dependencies. This assembly is built by a runtime newer than the
currently loaded runtime and cannot be loaded.” error displayed.
Resolution: The Personify web controls
and the Sitecore connector require .NET 4.0 or greater. Check the application
pool settings for the IIS site and make sure it states v4.0.
2. Issue:
An “Unable to load one or more of the requested types. Retrieve the LoaderExceptions
property for more information.” error displayed.
Resolution: This is likely a configuration
issue with the assembly binding for the Telerik control. Review the <bindingRedirect>
settings from the example configuration file to make sure they are correct
in the web.config file.
3. Issue:
A “Loader Exception Error" displayed.
Resolution: A paired assembly is
most likely missing. For example, if the Store.UI.dll is present, the
Store.dll assembly is also required.
4. Issue:
The Product List control does not return results.
Resolution: Check to be sure the
Personfiy.DataServices.Serialization.dll is present and review the web
service paths in the web.config file.
5. Issue:
The \Themes directory is not displaying.
Resolution: Themes are cached by
IIS. Recycle the application pool and this should clear it.
6. Issue:
The page containing the Biography control does not load.
Resolution: The Tools.xml file
has not been deployed in the \App_Data folder of the Sitecore site.
7. Issue:
A Personify web control does not display properly on the published page.
Resolution: The Personify web controls
are designed to display correctly on a standard .ASPX page. Any display
issues on a Sitecore installation are most likely caused by a conflict
between the overall skin CSS file for the site and the individual skin
CSS files for the controls. The individual skin CSS files for each control
can be found in the \Themes\PersonifyDefault directory of the Sitecore
site.
8. Issue:
The sharing icons do not pass the complete URL for the page attempting
to be shared.
Resolution: The URL properties for the Personify
web control are defined as relative URLs instead of PWF Parameters or
absolute URLs. It is not recommended to use relative URLs for Sitecore
installations that use Personify web controls.
9. Issue:
After upgrading the Personify web controls to a newer version, the Sitecore
installation produces errors.
Resolution: The binding redirect
reference for the Personify.WebControls.Base.dll file needs to be updated
in the web.config file in the <assemblyBinding> section. The reference
would be similar to:
<dependentAssembly>
<assemblyIdentity name="Personify.WebControls.Base" publicKeyToken="b5a5ba0ab302bbc2"/>
<bindingRedirect oldVersion="0.0.0.0-1.3.9.9" newVersion="1.4.0.0"
/>
</dependentAssembly>
Update the newVersion value to the version
of the Personify.WebControls.Base.dll being used for the installation.
The example above is for an installation using the Personify 1.4.0 web
controls.
10. Issue:
A “Could not load file or assembly 'Personify.Data.Services.Serialization...'
or one of its dependencies. The located assembly's manifest definition
does not match the assembly reference.” error displayed.
Resolution: A binding redirect
reference for the Personify.DataServices.Serialization.dll file needs
to be updated in the web.config file in the <assemblyBinding> section.
The reference would be similar to:
<dependentAssembly>
<assemblyIdentity name="Personify.DataServices.Serialization"
publicKeyToken="b5a5ba0ab302bbc2"/>
<bindingRedirect oldVersion="0.0.0.0-1.5.2.14" newVersion="1.5.2.15"
/>
</dependentAssembly>
Update the newVersion value to the version
of the Personify.DataServices.Serialization.dll being used for the installation.
The example above is for an installation using the Personify 1.5.2 SP1
Data Services.
11. Issue:
A handful of the controls, such as the Education control, Customer Name
control, Customer Special Needs control, Emergency Contact control, and
Shopping Cart Savings control, fail after upgrade from a previous version
of the Personify web controls.
Resolution: The assemblies for
these controls may have changed in the Personify web control files. The
connector did not update the existing sublayouts, but the new layouts
were created. Simply copy the Personify Type Name value from the new sublayout
to the existing sublayout for the control(s) on the pages.