Results 1 to 10 of 10
  1. #1
    Newbie
    Join Date
    October 19th, 2005
    Posts
    5
    WM-Records "cols" feature overrides my settings
    Is there a way to control the attributes of the WebMerge automatically-created columns?

    Problem:
    When using the "cols" feature in the WM-Records tag, a valign="top" tag is always generated. In addition, I haven't found a way to add other tags to control the table or cell attributes.

    My immediate problem is that I can't generate a multi-column table with the cell attributes I need. For example, I want the individual cells to be aligned center and vertically aligned bottom.

    Is there a way to control the tags used for the automatic columns? I'm looking for workarounds for a current project I need to finish.

    Longer-term solution?
    Would there be a way to pass table/cell attributes into the automatic column code?

    My initial idea for syntax is to allow the user to add any valid cell tags along with the "cols" and "width" tags you already support. If no other tags are found, use your current code (or consider removing the valign tag you add currently). Examples:
    [WM-Record cols=2 width=500 bgcolor="gray"]
    [WM-Record cols=2 width=500 align="center" valign="bottom"]

    I haven't thought much about how to distinguish between cell attributes and table attributes.

    Thanks in advance.

  2. #2
    Affiliate Manager
    Join Date
    January 18th, 2005
    Location
    Los Angeles, California
    Posts
    1,913
    Thanks for posting. I'm interested in allowing table attributes to be passed in as you describe, but it raises a question: Should we also allow cell attributes to be passed? and if so, how should we differentiate between the two?

    This is very much on my radar, and I appreciate your posting that. Looking forward to some guidance from our users here.
    Richard Gaskin
    Developer of WebMerge: Publish any data feed on any site
    http://www.fourthworld.com

  3. #3
    Newbie
    Join Date
    October 19th, 2005
    Posts
    5
    RE: "Should we also allow cell attributes to be passed? and if so, how should we differentiate between the two?"

    Yes, definitely allow cell attributes to be passed. I'll toss this out for a syntax option:

    [WM-Record table{cols=2 width=500 bgcolor="gray"}; cells{align=center valign=bottom}]

    or

    [WM-Record table{cols=2 width=500 class="tableformat"}; cells{class="cellformat"}]
    Last edited by abbopeters; October 19th, 2005 at 01:55 PM.

  4. #4
    The slot machine that IS paid! Billy Kay's Avatar
    Join Date
    January 18th, 2005
    Location
    Small Town in Tennessee
    Posts
    5,226
    The workaround - though inconvenient - is not hard at all

    Assuming you're talking about the category/subcat pages (not the product detail page)

    I move them all into a temp directory

    do a big search and replace

    then move the "fixed" pages back to the real directory

  5. #5
    Full Member heisje's Avatar
    Join Date
    January 18th, 2005
    Posts
    314
    .


    I was always wondering what prevented Richard from allowing full table & cell attributes to be passed - this is an absolute necessity. "nasty" work-arounds are possible, but if there is no scripting limitation preventing this, full table / cell attributes must be made available, as a priority.


    heisje

    .

  6. #6
    Affiliate Manager
    Join Date
    January 18th, 2005
    Location
    Los Angeles, California
    Posts
    1,913
    Same as I mentioned above: we should allow both cell and table attributes, and ideally the syntax for doing so should be simple. The proposed example above isn't bad, but I can't help but wonder if we can make it simpler....
    Richard Gaskin
    Developer of WebMerge: Publish any data feed on any site
    http://www.fourthworld.com

  7. #7
    Full Member heisje's Avatar
    Join Date
    January 18th, 2005
    Posts
    314
    .

    css may provide the design attributes, as mentioned before, for simplicity - if there is provision both in the table & cell WM tags for the "class" attribute.

    but is the use of css universal, or should it be made compulsory when using WM?

    maybe if one would need to use the full capabilities of WM tables they would also need to use css, but for more simple applications that would not be necessary, as is the case now. after all, WM is supposed to be a professional tool and some elementary competences should be expected.


    heisje


    .

  8. #8
    Newbie
    Join Date
    October 19th, 2005
    Posts
    5
    My intent of including two examples (one with css, the other without) was to illustrate the flexibility of the desired solution. I'd propose supporting either syntax option, rather than limiting it to one or the other.

    I understand striving for the simplest solution possible. I thought my proposed examples were simple in that they match normal HTML tag use. I'm open to other ideas as long as they follow reasonable conventions and provide the desired capabilities.

    Anyone else have some ideas?

  9. #9
    Full Member heisje's Avatar
    Join Date
    January 18th, 2005
    Posts
    314
    I'm open to other ideas as long as they follow reasonable conventions
    hello, seems somebody else has worn Richard's hat here.
    good! maybe this way we shall really get something done . . .


    heisje


    .

  10. #10
    Newbie
    Join Date
    November 26th, 2005
    Posts
    3
    Wink
    Now, I didn't have any problems keeping my table looking the way I wanted it to look. Put the WM Record tag after the table attributes tags and the ending WM Record tag right before the ending TD tag. Here's how mine looks:

    <table border="3" align="center" cellpadding="5" cellspacing="5" bordercolor="#FFFFFC" bordercolorlight="#FFFFFF" bordercolordark="#D3CFCF" bgcolor="#FFFFFF">
    <tr>
    <td align="center" valign="bottom">
    [WM-Record cols=2]<center><br>
    [WM-ImagePath: Small_Image_URL noLink]<br>
    <a href="[WM-Field: Product_URL]">[WM-Field: Product_Name]</a><br>
    [WM-Field: Brand]<br>
    [WM-Field: Description][/WM-Record] </center></td>
    </tr>
    </table>

  11. Newsletter Signup

+ Reply to Thread

Similar Threads

  1. How Do I "Verify Payment Settings" in SAS?
    By JoyUnltd in forum ShareASale - SAS
    Replies: 2
    Last Post: October 15th, 2011, 04:25 PM
  2. Replies: 12
    Last Post: June 24th, 2009, 06:39 AM
  3. "ABestWeb Book of Records" Contest - Winners Announced!
    By Geno Prussakov in forum AM Navigator
    Replies: 12
    Last Post: February 3rd, 2008, 04:04 PM
  4. Replies: 48
    Last Post: February 1st, 2008, 03:40 PM
  5. Replies: 2
    Last Post: July 29th, 2005, 01:51 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
  •