Troubleshoot remote widgets and feeds

Samples > Starter stores > Starter store enhancements > Remote widgets > Work with remote widgets

Troubleshoot remote widgets and feeds

If you encounter problems while using remote widgets or feeds, refer to the following troubleshooting topics to help determine the cause of the problem and find possible solutions.

Troubleshoot remote widget and feed content

Problem Possible causes Solution or explanation
When creating a remote widget in KickApps:

I cannot see any feed data in the remote widget.
OR

The data looks like #{feed_list.contentSource.::title}.

The computer you are using is not accessible from the Internet. To see and edit the feed data in KickApps, you must specify a feed URL for the widget that comes from a computer that KickApps can access.
Note that you can still edit the widget template frame (static text and images) in KickApps without seeing the feed data.
The Web service providing data for the feed is not returning any data.

To determine whether the Web service is returning data, paste the feed URL into a news reader or browser that supports Atom feeds and see if any feed data displays.

If the Web service is not returning data:

For e-Marketing Spot remote widgets, ensure that there is a Web activity running in the e-Marketing Spot.

For wish list or gift registry remote widgets, ensure that the wish list or gift registry contains products.

Check for and fix any errors in the system logs.

If you are using a secure feed URL, the SSL certificate might not be valid, for example, it might be unsigned, missing or expired. Consult the Web server documentation to learn how to correct the certificate.
The e-Marketing Spot on the store page shows different content than the Atom feed displayed in the remote widget or feed reader. The Web activity uses targets that are not supported for remote widgets and feeds, for example, the Cookie Contents target. In other words, the target works on the store page but it does not work for the remote widget or feed. Change the Web activity so that it uses supported targets, or remove the target. See Personalization in e-Marketing Spot remote widgets and feeds.
The e-Marketing Spot on the store page is configured to display a maximum number of items (catalog entries, categories, or content) that is different from the maximum number configured for the Atom feed. To make the numbers match, modify either the parameters passed to the e-Marketing Spot snippet JSP file or the parameters passed to the Atom feed URL. See URL structure for Web service feeds (the URL parameters are numberProductsToDisplay, numberCategoriesToDisplay, and numberContentToDisplay).
The browser or feed reader does not render the Atom feed correctly. The browser or feed reader does not support the Atom feed format. Use a browser or feed reader that supports the Atom feed format. Try a different browser or feed reader, or install a newer version.

Troubleshoot Share and Subscribe links in Madisons
Problem Possible causes Solution
The Share link for the remote widget does not display on the Madisons store page.
The Share link is not enabled or configured correctly on the page.
Complete the appropriate procedure:

Add a Share link for an e-Marketing Spot remote widget

Enable the Share link for a wish list remote widget

Enable the Share link for a gift registry remote widget

If you have already completed the procedure, double-check the code for the Share link using the example in the procedure for reference. For the Share link to display, specify a widget ID value for at least one of the following two parameters:
  
<c:param name="sidebarWidgetId" value=""/>   
<c:param name="bannerWidgetId" value=""/>
The Change flow option for remote widgets is not enabled in WebSphere Commerce Accelerator. Enable the appropriate Change flow option using this topic as reference:Remote widgets change flow options
The connection to KickApps is not configured in the Administrative Console. Complete the procedure Configure WebSphere Commerce to communicate with KickApps for remote widgets
The Subscribe links for the three e-Marketing Spot feeds demonstrated for Madisons do not display after I publish the MadisonsEnhancement.sar store archive. You did not publish the Madisons.sar store archive after installing WebSphere Commerce v7.0 fix pack 1 or later. When you install the fix pack, a new version of the Madisons.sar store archive installs on the machine. This store archive contains the latest Madisons fixes plus necessary extension points for the MadisonsEnhancements.sar store archive. The MadisonsEnhancements.sar store archive will not work properly with earlier versions of the Madisons starter store.

Ensure that WebSphere Commerce Version 7 fix pack 1 is installed.

Publish a new Madisons store using the Madisons.sar store archive included with fix pack 1.

Publish the MadisonsEnhancements.sar store archive on top of the new Madisons store.
Troubleshoot Management Center remote widget functions

Problem Possible causes Solution
In Management Center, the Get Widget button does not display on the e-Marketing Spot properties page, or it does not connect to KickApps. The KickApps transport in the Administration Console is not set up, or it is set up with some incorrect or missing values. Set up, or review the setup of the KickApps transport in Administration Console. See Configure WebSphere Commerce to communicate with KickApps for remote widgets.

Troubleshoot miscellaneous remote widget and feed issues

Problem Possible causes Solution
When sharing my KickApps widget on Facebook or MySpace, the preview thumbnail does not load. The dimensions of the widget template defined in KickApps do not meet the requirements of the social network. Facebook and MySpace have the following layout requirement for thumbnails: the ratio of height divided by width, and width divided by height, cannot exceed 3.0. For example, if the widget template is 700 pixels wide and 200 pixels high, the ratio is 700/200 = 3.5. As a result, the thumbnail will not load in the sharing preview. Redesign the widget template so that the height-to-width and width-to-height ratios are 3 or less.
When I select Change flow options for Wish Lists, Widgets, and Feeds in WebSphere Commerce Accelerator, the process hangs. This is known limitation. For more information, see Troubleshoot: Change flow process hangs.
When I e-mail my wish list, the e-mail is never received. The e-mail transport in the Administration Console is not set up, or the hostname in the transport is incorrect. For more information, see Configure a transport method for the site

Related tasks

Create an e-Marketing Spot remote widget
Add a Share link for an e-Marketing Spot remote widget
Add a Subscribe link for an e-Marketing Spot feed
Create a wish list remote widget
Enable the Share link for a wish list remote widget
Create a gift registry remote widget
Enable the Share link for a gift registry remote widget

+
Search Tips | Advanced Search

Problem	Possible causes	Solution or explanation
When creating a remote widget in KickApps: I cannot see any feed data in the remote widget. OR The data looks like #{feed_list.contentSource.::title}.	The computer you are using is not accessible from the Internet.	To see and edit the feed data in KickApps, you must specify a feed URL for the widget that comes from a computer that KickApps can access. Note that you can still edit the widget template frame (static text and images) in KickApps without seeing the feed data.
The Web service providing data for the feed is not returning any data.	To determine whether the Web service is returning data, paste the feed URL into a news reader or browser that supports Atom feeds and see if any feed data displays. If the Web service is not returning data: For e-Marketing Spot remote widgets, ensure that there is a Web activity running in the e-Marketing Spot. For wish list or gift registry remote widgets, ensure that the wish list or gift registry contains products. Check for and fix any errors in the system logs.
If you are using a secure feed URL, the SSL certificate might not be valid, for example, it might be unsigned, missing or expired.	Consult the Web server documentation to learn how to correct the certificate.
The e-Marketing Spot on the store page shows different content than the Atom feed displayed in the remote widget or feed reader.	The Web activity uses targets that are not supported for remote widgets and feeds, for example, the Cookie Contents target. In other words, the target works on the store page but it does not work for the remote widget or feed.	Change the Web activity so that it uses supported targets, or remove the target. See Personalization in e-Marketing Spot remote widgets and feeds.
The e-Marketing Spot on the store page is configured to display a maximum number of items (catalog entries, categories, or content) that is different from the maximum number configured for the Atom feed.	To make the numbers match, modify either the parameters passed to the e-Marketing Spot snippet JSP file or the parameters passed to the Atom feed URL. See URL structure for Web service feeds (the URL parameters are numberProductsToDisplay, numberCategoriesToDisplay, and numberContentToDisplay).
The browser or feed reader does not render the Atom feed correctly.	The browser or feed reader does not support the Atom feed format.	Use a browser or feed reader that supports the Atom feed format. Try a different browser or feed reader, or install a newer version.

Problem	Possible causes	Solution
The Share link for the remote widget does not display on the Madisons store page.	The Share link is not enabled or configured correctly on the page.	Complete the appropriate procedure: Add a Share link for an e-Marketing Spot remote widget Enable the Share link for a wish list remote widget Enable the Share link for a gift registry remote widget If you have already completed the procedure, double-check the code for the Share link using the example in the procedure for reference. For the Share link to display, specify a widget ID value for at least one of the following two parameters: <c:param name="sidebarWidgetId" value=""/> <c:param name="bannerWidgetId" value=""/>
The Change flow option for remote widgets is not enabled in WebSphere Commerce Accelerator.	Enable the appropriate Change flow option using this topic as reference:Remote widgets change flow options
The connection to KickApps is not configured in the Administrative Console.	Complete the procedure Configure WebSphere Commerce to communicate with KickApps for remote widgets
The Subscribe links for the three e-Marketing Spot feeds demonstrated for Madisons do not display after I publish the MadisonsEnhancement.sar store archive.	You did not publish the Madisons.sar store archive after installing WebSphere Commerce v7.0 fix pack 1 or later. When you install the fix pack, a new version of the Madisons.sar store archive installs on the machine. This store archive contains the latest Madisons fixes plus necessary extension points for the MadisonsEnhancements.sar store archive. The MadisonsEnhancements.sar store archive will not work properly with earlier versions of the Madisons starter store.	Ensure that WebSphere Commerce Version 7 fix pack 1 is installed. Publish a new Madisons store using the Madisons.sar store archive included with fix pack 1. Publish the MadisonsEnhancements.sar store archive on top of the new Madisons store.

Problem	Possible causes	Solution
When sharing my KickApps widget on Facebook or MySpace, the preview thumbnail does not load.	The dimensions of the widget template defined in KickApps do not meet the requirements of the social network. Facebook and MySpace have the following layout requirement for thumbnails: the ratio of height divided by width, and width divided by height, cannot exceed 3.0. For example, if the widget template is 700 pixels wide and 200 pixels high, the ratio is 700/200 = 3.5. As a result, the thumbnail will not load in the sharing preview.	Redesign the widget template so that the height-to-width and width-to-height ratios are 3 or less.
When I select Change flow options for Wish Lists, Widgets, and Feeds in WebSphere Commerce Accelerator, the process hangs.	This is known limitation.	For more information, see Troubleshoot: Change flow process hangs.
When I e-mail my wish list, the e-mail is never received.	The e-mail transport in the Administration Console is not set up, or the hostname in the transport is incorrect.	For more information, see Configure a transport method for the site