Troubleshooting Design Studio

The following sections describe how to solve commonly encountered problems in Design Studio:

Design Studio Hangs or Will Not Connect to a CTE

Design Studio frequently hangs.

Design Studio can hang if your PC runs out of memory (a minimum of 128 MB of RAM is required; 256 MB of RAM is recommended).

Design Studio cannot connect to a CTE.

This problem is probably due to the information that you entered when you logged into Design Studio or connected to a different CTE. Contact your CTE administrator to verify that you are using the correct username, password, IP address, and server upload port.

Simulator Does Not Work

I cannot open a URL in a simulator or browser. I'm getting messages such as "page not found" or "cannot connect to site."

To use a simulator or browser to preview a page, you must connect to a CTE. Verify that you are entering the URL in the correct format as shown in the following example: http:// ipAddress:portNumber/http:// pageURL

Transformed pages do not display in my browser. They display in a simulator.

When I try to open a URL in the Openwave Mobile Browser Simulator, the message "Unsupported content type" displays.

After I select "Click here to start" on the Go.Web Simulator, the simulator seems to hang while displaying a message about generating security keys.

This problem can occur if you are using a software firewall on your computer. To work around the problem, disable the software firewall while you are using the Go.Web Simulator.

General Issues when Using Design Studio

I opened a URL in Design Studio and the page is blank.

A page might appear blank if there is one Select rule on the page and that rule is dead.

I am having trouble creating Identifier rules that work the way I intend.

Identifier rules must be mutually exclusive. Here's a simple example to help you understand how your Identifier rules might be incorrect. Suppose that you have two types of bags of marbles: Type Bag1 contains red marbles and green marbles; Type Bag2 contains red marbles and blue marbles. Suppose that you create the following rules to identify the two types of bags:

If a bag contains a red marble, then it is type Bag1.
If a bag contains a red marble and a blue marble, then it is type Bag2.

You receive a new bag of marbles and need to determine which type of bag it is. First, you check if it has a red marble. It does, therefore it matches type Bag1. You then look at the rest of the marbles in your new bag and see that it contains red and blue marbles (type Bag2), not red and green marbles (type Bag1). Because the rule for type Bag1 is not mutually exclusive, you incorrectly identified the new bag.

I applied the Select rule to an element. I want to select another element, but only the element I selected appears in the Edit tab.

My transformation is requiring many rules.

Most transformations require fewer than a dozen rules. The most efficient transformations generally start with a Select rule, which eliminates most content that you do not want on the transformed page. Also, be sure that you take advantage of applying rules to multiple depths and positions as described in the "Applying Rules to Several Elements" section.

Rules in the rules area are displayed in red or gray.

Rules that are displayed in gray are no longer in effect on the page. For more information, see the "Evaluating Dead Rules" section.

The Configure dialog box contains the message "This is a Relative Element" and does not let me change the depth setting of the element.

When you select the first Source element of a Move rule.
When you select the first Location element of a rule that uses the Advanced setting to specify rule location.

In both cases, Design Studio does not allow you to change the depth setting of the element because the depth of that element is relative to the Destination path (for the Move rule) or the Operation path (for the Advanced setting). Design Studio must retain the depth setting of the element in order to track its XPath.

A Select rule has no effect or the entire page is clipped.

You might need to select a larger area of the page and then clip elements from it as needed. If the transformed page is blank, the Select rule may be based on an attribute that dynamically changes or the Select rule may be dead.

I added a new rule and a previously added rule no longer is in effect.

In general, the last rule added has the highest priority. The exception is the Select rule, which always takes precedence.

When one rule causes another rule to not work, the two rules conflict. Conflicting rules display in red in the list of rules. Right-click a red rule name and choose Rule Conflicts to view the name of the conflicting rule.

The configuration file I just saved is not what I intended. Can I revert to the previous version?

When you save a configuration file, Design Studio keeps a backup of the previous version in a file named filename~.

If you are doing a lot of experimenting, consider saving each version of a configuration file to a different name so you can return to older versions.

Unexpected Transformation Results

HTML/XML pages viewed in a simulator or on a device are not transformed.

Verify the page Identifier rules.
Confirm that the rules are applied to the particular device.
Verify that the rules were published to the CTE you are using to preview them. If they were published, perhaps a subsequent publish of a different configuration file overwrote them, so try publishing the configuration file again.
If the above setup is correct, contact your CTE administrator. There might be a problem with the CTE or server load balancer configuration.

ScreenTop portal pages do not appear on a device.

The CTE Administration Tool includes Default URL settings that take precedence over a ScreenTop. If the ScreenTop does not display on a device after you have published the configuration file and connected to a CTE using the device, contact your CTE administrator and verify that a Default URL is not specified in the Administration Tool.

The rules I applied to a page resulted in a correct transformation a few days ago, but now they do not work. The rules that I'm applying to a particular page are not working consistently.

This problem is probably due to dynamically generated content on the page. Determine how the content is changing and apply rules accordingly. Pay particular attention to rules that are applied based on element depth and position. The dynamically generated content may not always appear at the same depth or position.You might, for example, need to set a path element to match against a range of positions.

A page does not have the transformation results I intended.

The rules that you create must result in valid HTML. If the rules are not working as you expected, verify that you have not inadvertently instructed Design Studio to create invalid HTML. For example, verify that you have not moved a td element outside of a table element.

No images are displayed on IP phones.

If the images are not being removed as the result of transformation rules, check the Device Definition File (DDF) for IP phones and verify that images are enabled. For more information about editing a DDF, see the "Configuring Device Definitions" section.

I added a page that contains one GIF or JPEG image (and no text) and the image does not show up on a RIM device, Palm device, or phone.

This problem occurs when a web page contains a link (perhaps with a thumbnail image) that opens just an image in a separate window. Unlike desktop browsers, microbrowsers do not support pages that contain only an image. To work around this limitation, either add text to the page containing just the image, or clip the link to the image.

On a RIM device, a GIF image is not displaying correctly.

A RIM device encounters problems when attempting to display a GIF image that follows a blank GIF image (used for spacing, for example). To correct the problem, use Design Studio to clip all blank GIFs.

On a Compaq iPAQ device, a page has horizontal scrolling.

By default, the CTE limits horizontal scrolling to improve usability. However, if a page contains a pre element, the default behavior is overriden and the page might have horizontal scrolling. To disable the horizontal scrolling, use Design Studio to clip or ignore the pre element.

I imported an XSL style sheet, but it has no effect on the XML pages I added to the project.

All xsl:template elements in your style sheet must have a priority attribute set to greater than 1. Otherwise, the style sheet generated by Design Studio can conflict with your style sheet so that your styles do not apply.

Problems with Pages Containing JavaScript

I transformed a page that contains JavaScript and the form does not work on a device.

Verify that the page does not include Modify rules that change the value attributes of input fields or the name attribute of form elements.

A page that contains JavaScript has unnecessary buttons.

Design Studio adds a button labeled "Change" or "Submit" for a variety of JavaScript events. You can clip any unneeded buttons.

URL links are transformed to buttons.

If an a element has JavaScript as a part of its href or onclick event, the CTE converts the child text nodes to input type="submit" and child image nodes to input type="image". When the user clicks the button, the CTE executes the associated JavaScript.

While working in Design Studio, I needed to return to a page that contains JavaScript. The page does not behave as expected.

When you click the Browse tab and navigate to a page that you previously worked on in the same session, the state of the JavaScript may not be correct. To return to the correct state, click the

(reload) button to retrieve the page from the CTE cache. If the behavior is still not correct, replay the JavaScript session from the beginning.

Table of Contents