XSLfast

DTD: Please check out the Layout from the customer

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: Version 2.0.3
  • Fix Version/s: Version 2.0.3
  • Component/s: None
  • Labels:
    None
  • Request Controller:
    Please Select
  • External Supervisor:
    Please select
  • Executing Programmer:
    Please select

Description

Please check the layout file from the customer according:
1. the Index (OEM) some Products are displayed twice I'm not sure why this is the case
2. Also the Keep with next and previous doesn't work correctly

  1. actros26052006.zip
    02/Jun/06 5:13 PM
    860 kB
    Packianathan, Anton
  2. Test31dm_index.rar
    06/Jun/06 2:36 PM
    11 kB
    Nemchaninov, Sergei
  3. Test31dm_index.zip
    02/Jun/06 5:11 PM
    57 kB
    Packianathan, Anton

Activity

Hide
Nemchaninov, Sergei added a comment - 06/Jun/06 2:36 PM

See the attached layout.

Table in Tail page shouldn't be placed in header.
Use {CompetitiveInformation/CompetitorProductID} XPath instead of {../ProductGroup/ProductGroup/Product/CompetitiveInformation/CompetitorProductID} when setting 'descedant::Product' filtering.
TextFlow object in 'Application' table column in index page shouldn't overlap CallTemplate and Index objects.

1. Some Products are displayed twice because of a Product that contains several CompetitiveInformation nodes and
2. Keep with next and Keep with previous properties do work correctly. What was the problem?

Show
Nemchaninov, Sergei added a comment - 06/Jun/06 2:36 PM See the attached layout. Table in Tail page shouldn't be placed in header. Use {CompetitiveInformation/CompetitorProductID} XPath instead of {../ProductGroup/ProductGroup/Product/CompetitiveInformation/CompetitorProductID} when setting 'descedant::Product' filtering. TextFlow object in 'Application' table column in index page shouldn't overlap CallTemplate and Index objects. 1. Some Products are displayed twice because of a Product that contains several CompetitiveInformation nodes and 2. Keep with next and Keep with previous properties do work correctly. What was the problem?

People

Vote (0)
Watch (0)

Dates

  • Created:
    02/Jun/06 5:10 PM
    Updated:
    09/May/07 12:26 AM
    Resolved:
    07/Jun/06 10:02 AM