We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16183
    • 1,390 Posts
    Quote from: sottwell at Aug 19, 2009, 03:11 PM

    When you’ve selected a property set to edit, the default properties will show in the grid in the color gray. Properties in gray are not in the property set, but show up there for easier editing. Properties in green are properties that have been overridden from the default. Properties in purple are new properties in the custom set that are not in the default properties.
    what huh huh I hate this; it makes no sense to me whatsoever! It might as well be in Elbonian! I have a lot of work ahead of me, I see.

    Been there smiley

    e.g. wayfinder => default property for &lastClass = last; "last" should be in gray
    if you override that in your property set, e.g. &lastClass = end, "end" will appear in green
    if you add a custom property to wayfinder, e.g. &paginate = true, "true" will appear in purple

    cheers/k
      • 16183
      • 1,390 Posts
      OK,

      I can confirm no prefixes are pre-pended to the tables created by Revo SVN 5677 in my install.

      cheers/k
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Ah, so this corresponds to the Configuration tab in snippets and plugins for Evo, only they can be applied to all elements. Hmmm. I do wonder what kind of "properties" templates and chunks would have.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 28215
          • 4,149 Posts
          Quote from: kongondo at Aug 19, 2009, 03:21 PM

          I can confirm no prefixes are pre-pended to the tables created by Revo SVN 5677 in my install.

          We’re looking into the issue currently. It’s not happening on our server environments, so we’re doing some debugging. We should eventually figure it out.

          if you can provide us with any relevant error.log or setup logs information, that’d be great.
            shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
            • 28215
            • 4,149 Posts
            Quote from: sottwell at Aug 19, 2009, 03:30 PM

            Ah, so this corresponds to the Configuration tab in snippets and plugins for Evo, only they can be applied to all elements. Hmmm. I do wonder what kind of "properties" templates and chunks would have.

            Anything you want. Say in a template with a property "title":

            <html><head><title>[[+title]]</title></head><body>[[*content]]</body></html>
            


            Not as useful as chunks, though, where you could use the same concept to create default property values for one chunk. Say you had a chunk named "likeColors" with the content:

            I like [[+color]]!


            ...and a property called "color". You could then create Property sets "Red" and "Blue", and set the color property to red and blue, to where the following tags would produce:

            [[$likeColors@Red? ]] -> I like Red!
            [[$likeColors@Blue? ]] -> I like Blue!
            


            Obviously this could be used in a more useful way; such as forms, dynamic releases, etc. modxcms.com’s Download section is actually powered by Chunks and Property Sets.
              shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
              • 16183
              • 1,390 Posts
              Quote from: splittingred at Aug 19, 2009, 03:31 PM

              Quote from: kongondo at Aug 19, 2009, 03:21 PM

              I can confirm no prefixes are pre-pended to the tables created by Revo SVN 5677 in my install.

              We’re looking into the issue currently. It’s not happening on our server environments, so we’re doing some debugging. We should eventually figure it out.

              if you can provide us with any relevant error.log or setup logs information, that’d be great.

              Thx.

              The error log is same as posted in the OP (these are from core/cache/logs). Are there any other logs? Thx.

              The first log is:

              [2009-08-19 21:10:37] (ERROR @ /setup/index.php) Error SQLER executing statement: 
              Array
              (
                  [0] => SQLER
                  [1] => 1146
                  [2] => Table 'revosvn.access_permissions' doesn't exist
              )
              


              Subsequent logs have:

              [2009-08-19 21:11:20] (FATAL) Could not load core MODx configuration!


              Screen below shows where it stops..

              cheers/k
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                Hm. I got this one...
                [2009-08-19 23:40:36] (ERROR @ /2.0-5677/setup/index.php) Package /Applications/MAMP/htdocs/2.0-5677/core/packages/core.transport.zip not found. SIG:
                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 28215
                  • 4,149 Posts
                  Thanks guys, we’re looking into it.

                  Susan, I’m enjoying your play-by-play experience of Revo. smiley
                    shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                    • 3749
                    • 24,544 Posts
                    Quote from: sottwell at Aug 19, 2009, 03:30 PM

                    Ah, so this corresponds to the Configuration tab in snippets and plugins for Evo, only they can be applied to all elements. Hmmm. I do wonder what kind of "properties" templates and chunks would have.

                    I’m still learning about this stuff and recently found this out:

                    In templates and chunks, Placeholders with the key names will be replaced by the values of the element’s default properties. Attached property sets can

                    Properties are just arrays of key=>value pairs so, in theory, a snippet or plugin that processes a chunk, for example, could consult the default properties of the chunk and change it’s behavior on the basis of what it finds. That would allow you to keep information about how to handle a chunk (e.g. the name of the CSS file or chunk to use with it) *in* the chunk, which might be handy.
                      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
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      So, for example, for a template I could have the default location for keeping css files in its properties. Would this now apply to all templates? So I could just use [[+styles]]mystyle.css instead of having to remember where I put them?
                        Studying MODX in the desert - http://sottwell.com
                        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                        Join the Slack Community - http://modx.org