We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28215
    • 4,149 Posts
    Quote from: rthrash at Oct 02, 2006, 04:18 PM

    Quote from: splittingred at Oct 02, 2006, 04:04 PM

    - Heirarchical User/Document Groups (i.e., subgroups of user groups would be nice)
    - A better UI for managing user Groups
    Those should come after the next release (0.9.5 in late beta now)

    Awesome.
    Quote from: rthrash at Oct 02, 2006, 04:18 PM

    - Ability to assign a chunk as a template var without having to snippet hack it
    - OR Subtemplates (templates within templates)
    Why will using chunks not work for this now?
    I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.

    For example, if I’ve got a header that has different HTML elements (say, extra divs or LIs or something) depending on what department it loads, it’d be much easier to specify to "include" a certain file, or (sub)template in each file. Kind of like how in Smarty you can use conditionals and the "include" statement to include separate files.

    Right now I have to do a TV that references a Document ID number, and then use a snippet to "include" that document into the page based upon the TV number. Maybe there’s a better way of doing this, but I haven’t found one yet. Do you have any ideas?
    Quote from: rthrash at Oct 02, 2006, 04:18 PM

    - Mass Document group/TV/variable changing (if i want to change 3000 pages to a different document group...and i shouldnt have to download a plugin to do this)
    The 095 Doc Manager will do this quite nicely.

    I’ll check that out when it comes. Thanks for your prompt responses!
      shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
      • 25663 MODX Staff
      • 12,272 Posts
      I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.

      For example, if I’ve got a header that has different HTML elements (say, extra divs or LIs or something) depending on what department it loads, it’d be much easier to specify to "include" a certain file, or (sub)template in each file. Kind of like how in Smarty you can use conditionals and the "include" statement to include separate files.

      Right now I have to do a TV that references a Document ID number, and then use a snippet to "include" that document into the page based upon the TV number. Maybe there’s a better way of doing this, but I haven’t found one yet. Do you have any ideas?
      Make a single TV that is a dropdown list selector. Use the dropdown list selector to tell it which "section" you’re in. For good measure, have it’s default value be @INHERIT so you only have to set it for the top level of each section. The value of the options would be the chunks you use as your subtemplates, like:

      products=={{productsSection}}||news=={{newsSection}}...


      Make sense?
        Ryan Thrash, MODX Co-Founder
        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
        • 28215
        • 4,149 Posts
        Quote from: rthrash at Oct 03, 2006, 09:14 AM

        I might have phrased that wrong. I guess the issue is this - If I’ve got a large site with one main template style, but some variation in it according to different departments (which are subdirs in the site), it might be helpful to have a subtemplate within that.

        For example, if I’ve got a header that has different HTML elements (say, extra divs or LIs or something) depending on what department it loads, it’d be much easier to specify to "include" a certain file, or (sub)template in each file. Kind of like how in Smarty you can use conditionals and the "include" statement to include separate files.

        Right now I have to do a TV that references a Document ID number, and then use a snippet to "include" that document into the page based upon the TV number. Maybe there’s a better way of doing this, but I haven’t found one yet. Do you have any ideas?
        Make a single TV that is a dropdown list selector. Use the dropdown list selector to tell it which "section" you’re in. For good measure, have it’s default value be @INHERIT so you only have to set it for the top level of each section. The value of the options would be the chunks you use as your subtemplates, like:

        products=={{productsSection}}||news=={{newsSection}}...


        Make sense?

        Yep, perfect sense. I had noticed someone doing something similar, but wasn’t sure how that worked completely. That’ll work perfectly. Thanks so much!
          shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
          • 17815
          • 50 Posts
          document types
            • 6726
            • 7,075 Posts
            What do you mean by it ?

            You can define usual document types already for MODx documents : text/html sure but also text/css or any kind of mime type for that matter...

            Would you care to elaborate ?
              .: COO - Commerce Guys - Community Driven Innovation :.


              MODx est l'outil id
              • 24719
              • 194 Posts
              i’m still looking forward to hosting subsites and sites on different domains. the subsites hack is ok, but doesn’t work well across different domains...
                • 23478
                • 133 Posts
                Quote from: redman at Jan 31, 2007, 05:35 AM

                i’m still looking forward to hosting subsites and sites on different domains. the subsites hack is ok, but doesn’t work well across different domains...
                much more simpler ... MODx parser lacks of a basedir variable for implementing absolute inner site links.

                I mean when you try to use MODx as a framework, you will call pieces of modx from subdir ....
                each every snippet is coded with [~id~] which are translated as
                <a href="mydir/mypage">
                even if you call it from the forum subdir (for exemple)
                with a single basedir linking to where modx is installed, it could solve many tears i’ve dropped
                <a href="/basedir/mydir/mypage">

                  • 25663 MODX Staff
                  • 12,272 Posts
                  piwaille, simply add a base href to the head of your pages and all your problems magically go away.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 14575
                    • 21 Posts
                    Forum integration with IPB!
                      • 4971
                      • 964 Posts
                      Integrate with an Issue Tracking package, like eTicket or the like... (not a bug tracking package!)
                        Website: www.mercologia.com
                        MODX Revo Tutorials:  www.modxperience.com

                        MODX Professional Partner