Results 1 to 7 of 7
  1. #1
    Web Ho - Design B!tch ~Michelle's Avatar
    Join Date
    January 18th, 2005
    Location
    Michigan
    Posts
    2,040
    In my index template, I am using nested tables to match the rest of my site layout.

    My index0001.html file displays perfectly, but every index0002.html etc. does not.

    There should be one big table then a smaller table of 3 columns nested within that one.

    On all the other index pages there is a huge gap between the 1st and 2nd columns of pictures.

    When I look at the HTML that WebMerge has output I find that the 3 column table is missing it's closing table tag. Once I insert that manually it displays correctly.

    Here is the code I am using on the 3 column table. Is it correct?

    [WM-RECORD cols=3 width=600]
    [WM-IMAGEPATH: Thumbnail]
    [WM-FIELD: Name]</B>
    [WM-FIELD: Price]</font></CENTER>
    [/WM-RECORD]

    I want the whole table to be 600 wide with 3 columns.

    TIA!

    ~Michelle
    "All I ask is a chance to prove that money can't make me happy."
    "Work to become, not to acquire." -- Confucius

  2. #2
    Full Member
    Join Date
    January 18th, 2005
    Posts
    413
    Michelle;

    Very Interesting.

    Now that you mention this, I have encountered a similar problem. However, I thought that it was simply an HTML coding error that I had made in setting up the parent table to enclose the nested table.

    I just created a template similar to your nested table and reproduced the same problem that you are seeing. This sounds like a bit of a WM glitch.

    The work-around solution that I found was to add an extra set of HTML codes in the template to close the table. In other words, the codes for closing the parent table become </td></tr></table></td></tr></table> instead of just </td></tr></table>. It's not pretty, but it solved the problem for me.

    Have a Creative Day!
    FRANK, Baertracks
    Be More Creative

  3. #3
    Web Ho - Design B!tch ~Michelle's Avatar
    Join Date
    January 18th, 2005
    Location
    Michigan
    Posts
    2,040
    Adding that in worked.

    Actually this whole thing is acting weird with tables.

    As before, the main index page output is correct and displays correct, all other index pages are messed up.

    This time I created a table using regular HTML.

    Instead of nesting another table inside that one, I used horizontal rules to divide my sections.

    I placed the same code mentioned above within this table.

    On the secondary index pages that do not display properly, it has take the horizontal rules and doubled them up in places with spaces between them.

    This has to be a bug in the way Webmerge is outputting the code for the secondary index pages.

    ~Michelle
    "All I ask is a chance to prove that money can't make me happy."
    "Work to become, not to acquire." -- Confucius

  4. #4
    Web Ho - Design B!tch ~Michelle's Avatar
    Join Date
    January 18th, 2005
    Location
    Michigan
    Posts
    2,040
    Ok, I have confirmed the WebMerge is not closing the table tag in this bit of code.

    [WM-RECORD cols=3 width=600]
    [WM-IMAGEPATH: Thumbnail]
    [WM-FIELD: Name]</B>
    [WM-FIELD: Price]</font></CENTER>
    [/WM-RECORD]

    Looking at the code some more on the secondary index pages, I see that becuase it is not closing the table tag, it is adding a row and a cell to the table.

    Can't figure out why though.

    If I add a closing table tag to my template after the code, then the output is correct on the secondary index pages.

    Like this:

    [WM-RECORD cols=3 width=600]
    [WM-IMAGEPATH: Thumbnail]
    [WM-FIELD: Name]</B>
    [WM-FIELD: Price]</font></CENTER>
    [/WM-RECORD]
    <*/table>


    ~Michelle
    "All I ask is a chance to prove that money can't make me happy."
    "Work to become, not to acquire." -- Confucius

  5. #5
    http and a telephoto
    Join Date
    January 18th, 2005
    Location
    NYC
    Posts
    17,708
    I haven't tried this yet, but am excited that it is available and to know about the bug before I try! My question is, does WM write the records down or across? I assume down, but how does it know where to break the columns? So maybe across... See how easy it is to confuse me? LOL

    Deborah Carney
    Link up!
    Submit your sites, if you fit the criteria
    http://coolcraftsites.com/directory
    http://coolpetsites.com/petlinks

  6. #6
    Full Member
    Join Date
    January 18th, 2005
    Posts
    413
    ACROSS it is.

    Have a Creative Day!
    FRANK, Baertracks
    Be More Creative

  7. #7
    http and a telephoto
    Join Date
    January 18th, 2005
    Location
    NYC
    Posts
    17,708
    Thanks Frank, that makes sense actually, otherwise how would it know where to break the columns

    Deborah Carney
    Link up!
    Submit your sites, if you fit the criteria
    http://coolcraftsites.com/directory
    http://coolpetsites.com/petlinks

  8. Newsletter Signup

+ Reply to Thread

Similar Threads

  1. Nested Tag Replacement...????
    By AddHandler in forum Programming / Datafeeds / Tools
    Replies: 3
    Last Post: August 13th, 2006, 06:36 PM
  2. Is there a way to make nested tables stop floating?
    By HumbleFish in forum Programming / Datafeeds / Tools
    Replies: 4
    Last Post: May 13th, 2005, 11:34 AM
  3. Frank - question on nested tutorial
    By zimmy in forum WebMerge (Fourthworld.com)
    Replies: 7
    Last Post: May 19th, 2004, 03:50 PM
  4. Nested Query??? Is it possible
    By Doug247 in forum Programming / Datafeeds / Tools
    Replies: 4
    Last Post: April 25th, 2004, 08:04 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •