We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 24865
    • 289 Posts
    Hi all,

    Every time I try to create a system setting for my component, is fails to save it correctly. I checked out the video from Shaun (http://rtfm.modx.com/display/revolution20/System+Settings) and he does it the same way I do, but mine doesn’t work.

    When he enters "aaa_test_setting" followed by "Triple A Setting", my MODx strangly saves it double as aaa_test_setting. It also forgets the description (doesn’t save it, just empty) and I can’t load it into my component this way.

    Is my MODx version just messed up or am I doing something wrong?

    Using "MODx Revolution 2.0.0-pl rev7212"

    Thanks!
      @MarkGHErnst

      Developer at Adwise Internetmarketing, the Netherlands.
      • 28215
      • 4,149 Posts
      It’s a bug, related to issues:

      http://bugs.modx.com/browse/MODX-2192
      http://bugs.modx.com/browse/MODX-2232

      They have both been fixed in Git, and will be in the 2.0.1 patch release.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 24865
        • 289 Posts
        Ah, good. I thought I was going mad. xD

        I assume I can download it from Git (currently down over here)?

        Thanks, and if so, you can lock this one up.
          @MarkGHErnst

          Developer at Adwise Internetmarketing, the Netherlands.
          • 24865
          • 289 Posts
          Oeh, after downloading and replacing all the files on the FTP, the ONE system setting "Triple A Setting" reads like it should now, but ALL the other system settings have their default keys set.

          As you can see here:
            @MarkGHErnst

            Developer at Adwise Internetmarketing, the Netherlands.
            • 28215
            • 4,149 Posts
              shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
              • 24865
              • 289 Posts
              Yea, the one with a lot of fixes has been replaced first, and I did the second one just now - no change. Even after clearing the cache.
                @MarkGHErnst

                Developer at Adwise Internetmarketing, the Netherlands.
                • 28215
                • 4,149 Posts
                Hard to say, then; works fine for me, but I’m actually running *all* the fixes in Git, since I’m running off the Git repository.
                  shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                  • 24865
                  • 289 Posts
                  Hmm as one of the almost core developers (I asume) that would be the best way to go. I’ll try to fix it tomorrow. Haven’t tried anything besides the above. Had some company over.

                  To be continued.
                    @MarkGHErnst

                    Developer at Adwise Internetmarketing, the Netherlands.
                    • 24865
                    • 289 Posts
                    Alright, I tried both and I’ve replaced the files with the files from Git and nothing did the trick. I still see the one "Triple A Setting" and the rest seems untranslated ("setting_allow_multiple_emails")...

                    /edit
                    I just noticed that half of it is translated. Meaning: the area’s are translated perfectly. It feels like the lexicon parser has simply been disabled. If I rename:

                    $_lang['area_authentication'] = 'Authentication and Security';


                    to

                    $_lang['area_authentication'] = 'Authentication and Stuff, ye!';


                    It perfectly translates the section to what I just entered, but the same does not work for the system settings itself. It just sticks with the oldskool lexicon.
                      @MarkGHErnst

                      Developer at Adwise Internetmarketing, the Netherlands.