We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16942
    • 33 Posts
    I’ve got a bunch of product pages on a site I’m working on.

    For each page, I need to be able to attach a bunch of properties which will be parsed on the ordering page.

    For example, for an item which can be customised, I want to set a flag which determines that, so that on the order form I know to show a text field next to that item to harvest customisation information.

    The way I was going to do it was for each per-product setting, I could just have a bunch of TV’s. But is this the best way? Perhaps propertysets are a better way forward but there’s not a lot of low-level documentation about them.

    I’d be interested to see how everyone would approach it?
      • 3749
      • 24,544 Posts
      The ideal way would be to create a product object that represents a row in a custom DB table. Then you just have one resource that displays any product using a snippet to get the data. It’s a major operation to set up and create a UI for, but it’s by far the most efficient.

      To answer your question, though, there are no property sets for resources, so TVs is probably the way to go if you don’t want to set up a custom table.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting