We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25663 MODX Staff
    • 12,272 Posts
    We’re now very close to a release I think. The major outstanding issues:
    [*] Finalize the Demo Content (Team)
    [*] Finalize Action Page tweaks (headers, buttons, etc.) (Ryan + Jeff)
    [*] QuickEdit appears to be Dead (Adam) mostly functioning now... Adam continuing to tweak
    [*] Implement Resource Categories Management tool (Kyle)
    [*] Clean up what’s left in the Light theme including table styles (Team)
    [*] Port any changes to the other styles as appropriate (Anyone but Ryan)
    [*] Update the language files (Team) including adding setlocale


    If you have changes in your branch that you’ve noticed are not incorporated into the manager, in the current beta 3 and definately after the next beta build, please let us know in this thread.

    As far as structure to the manager goes, I have been able to get the top 3 frames merged (scripter, menu + topbar) and also to replace the button code with a more usable implementation. However, the topbar merge does seem to break some of the "Loading..." stuff, causing it to become stuck frequenly.

    With that said though, I am pretty confident in saying nuking the webelm.js "Loading" and "Waiting" messages seems to have considerably sped up the manager, so we might want to nuke that stuff entirely. Merged topbar/nav frames opens up some interesting styling options (and get us that much closer to a frame-free manager).


    I don’t have the bandwidth to implement the buttons into the action pages on a solo basis at this point, so if we’re going to do that (nuking coolbuttons.js in the process and leading to smaller css files) I’ll need assistance.
      Ryan Thrash, MODX Co-Founder
      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
      • 17883
      • 1,039 Posts
      Update the language files (Team)

      Where to start? Is (for example) the german file complete, I mean with all strings and some not translated or should I take the english one and start from scratch (uh)?
        • 6726
        • 7,075 Posts
        Marc, I think Paul has been working on the new updated english language file, we should contact him to get down to work on our translations... I’ll do french once I have the english file !
          .: COO - Commerce Guys - Community Driven Innovation :.


          MODx est l'outil id
          • 17883
          • 1,039 Posts
          Hi David,

          okay, I´ll start the german one asap (although my visit to the munich Oktoberfest could cause some delays laugh ).
            • 2762
            • 1,198 Posts
            Nicola (Banzai) Reply #5, 20 years ago
            Ryan let me know if i can help you anyway with the manager. smiley
            Now I’ve fixed again action files with rev 1533 and icons in Green and MOdx themes http://modxcms.com/forums/index.php/topic,6533.msg52711.html#msg52711
              Free MODx Graphic resources and Templates www.tattoocms.it
              -----------------------------------------------------

              MODx IT  www.modx.it
              -----------------------------------------------------

              bubuna.com - Web & Multimedia Design
              • 22815
              • 1,097 Posts
              Language Files
              Yes, I did do some stuff on the English lang file, but there’s been a lot of different people changing that recently. I ran through commenting out lang lines that were not being used, and I think I shared that with Ryan somehow.

              Of course, with things being added and removed from MODx, the language file hasn’t been particularly stable.

              However, I have identified a methodology:
              1) Get agreement here that the final language file can be alpha-sorted, as it makes the following much much easier.
              2) I then make a copy of all the MODx files, except the lang files.
              3) I then search through for all the language references (with " and ’) and create a list of them.
              4) I comment them out from the English list.
              5) I add in any that are missing.
              6) People then test MODx using the revised English list just to double check that everything is where it should be - if anything is missing, it can be easily added back. (If this actually happens, it probably means the lang is being referenced in an odd way, so that will may looking at).
              7) I then run a script. At the top, this includes the new English list and then a foreign language - eg French. The script creates a new language file based on a list of the required references and the existing language. This will therefore be French where a translation already exists, and English where one doesn’t.
              8) This is repeated for each language, including British English.
              9) The language files are sent out to the translation teams.
              10) The translation teams then just have to go through and translate every sentence that isn’t in their language.

              It should be noted that work *can* begin on translation now, because presently all the new variables are at the bottom and thus easily copiable from the English file; basically as long as I have the latest files from the translation team I can send them back a file with whatever work they’ve already done already in there. (If it turns out that they’ve done some translations I don’t have, I can always re-run the lang-file generator script).

              The above is not quite the whole story, because there is the scenario where a language variable is misnamed in the source or the language file, and they’ll need matching up to the existing translation... but the basic plan is as above.

              The best time for me to do this would be tonight (8 hours from the datestamp of this message).

              This does depend on me having
              a) agreement that the final lang file can be alpha sorted, rather than grouped as it is now.
              b) all the latest lang files.
                No, I don't know what OpenGeek's saying half the time either.
                MODx Documentation: The Wiki | My Wiki contributions | Main MODx Documentation
                Forum: Where to post threads about add-ons | Forum Rules
                Like MODx? donate (and/or share your resources)
                Like me? See my Amazon wishlist
                MODx "Most Promising CMS" - so appropriate!
                • 6726
                • 7,075 Posts
                Great work !

                I agree about a) and b) , well, I’ll try to do it in time and send it to you. I guess I should work from the latest beta’s language file ?

                While I am here, two things I forgot to mention and I’d like to see added for the next release :
                1) Have all languages files set to utf-8 (unless not possible for some language, not a Charset expert here) : anyway, I’d like the french file to be utf-8. If not now then for the next release.
                2) Insert a proper SetLocale to get proper date formatting for everyone (Thanks to Guillaume for this)

                For instance, if I don’t insert setlocale(LC_TIME, ’fr’, ’fr_FR’, ’fr_FR.ISO8859-1’); at the top of the language file, every date generated by snippets is english only.

                What do you think ?
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l'outil id
                  • 15987
                  • 786 Posts
                  I have commited updated versions of the Category delete (so it works & has correct permissions)

                  I also commited an updated version of AjaxSearch so that needs merged as well.
                    • 25663 MODX Staff
                    • 12,272 Posts
                    Lots of tweaks and fixes in this pre-public beta 4 build:
                    [*] Categories should be able to be deleted now
                    [*] New manager users should be OK, manager-theme-wise anyway
                    [*] Textarea font-size bug in FF and jumping buttons in IE fixed
                    [*] MODx Light is getting close (buttons, double headers and radio/checkbox tweaks needed on action pages
                    [*] QuickEdit should work
                    [*] RegClient stuff should work every time now

                    Go and get it and report any issues before we release on the masses: http://modxcms.com/testbuilds/beta4-r1553.zip
                      Ryan Thrash, MODX Co-Founder
                      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                      • 25663 MODX Staff
                      • 12,272 Posts
                      Note, when the language updates happen, we should make sure to address the set locale suggestion from bug report #290
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

                      This discussion is closed to further replies. Keep calm and carry on.