Troubleshooting Design Studio

The CTE logs informational, warning, and error messages related to the interactions between the CTE and Design Studio. You can view the Server Log from Design Studio and you can change the logging level in the CTE console so that all messages or only server version information is displayed in the log.

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 you are using the incorrect version of JRE (only version 1.2.2_008 is supported) or 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 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.

This problem can also be caused if the CTE administrator makes changes through the CTE console but does not choose the console option to commit the changes.

Simulators Do Not Work

I cannot open a URL in the simulators 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 start Design Studio and connect to a CTE. Also, verify that you are entering the URL in the correct format as shown in the following example: http:// CTE_ip_address:80/http:// page_url

Transformed pages do not display in my browser. They display in the other simulators.

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 web page appears blank in Design Studio if it is written with a JavaScript document.write() command. To verify how the page is written, open the page in Internet Explorer or Netscape, view the source, and look for a document.write() command.

I opened a URL in Design Studio and a page containing the message "This Page Contains Frames" displays.

When you browse to a page that uses frames, Design Studio gives you the option of working with the individual frames or using the noframes element content. If you prefer, you can return to the page that contains the link to the page with frames and use the Modify rule to change the destination of the link so that it bypasses the page with frames.

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 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 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 tried to apply a rule to several device types and a Conflicting Rules dialog box appeared. What happened?

At least one of the device types you attempted to apply a rule to already had a rule applied to that same element. For example, suppose you applied an Ignore rule to a font element for the WAP and Palm device types. Next, you selected the RIM device type and tried to apply a modify rule to the font element for RIM and WAP devices. Because the WAP device already has a rule applied to the font element, you cannot add another rule to the same element for this device.

The Conflicting Rules dialog box allows you to choose between removing the device type from the current rule or the previous rule.

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

If the selection includes an input or select element, you must also apply a Select rule to the corresponding formbegin and formend elements. Alternatively, you might need to select a larger area of the page and then clip elements from it as needed.

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 to this is the Select rule, which always takes precedence.

Suppose you want to transform a table so that the last row is clipped and all other rows are modified. If you clip the last row and then modify the first row, applying the Modify rule to all rows, the clipped row reappears. To achieve the desired transformation in this case, apply the Modify rule first and then clip the last row.

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 wireless 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.

The JavaScript in transformed HTML/XML pages is not working.

I selected an input element or select element, but it does not appear in the transformed page.

When Design Studio detects input and select elements, it adds to the XHTML corresponding formbegin and formend elements. When you apply a Select rule to an input or select element, you must also apply a Select rule to the corresponding formbegin and formend elements.

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.

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.

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.

Table of Contents