We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 8898
    • 181 Posts
    Quote from: splittingred at Feb 16, 2010, 09:33 PM

    Yep, already fixed. tongue
    I suspected something like this. It’s impossible to have an installation that’s up to date - I downloaded rev6373 about 45 minutes ago, and now there’s rev6375. wink I’m really happy that I chose MODx as new CMS for my customers and myself. smiley It’s so frustrating when there’s almost no development and even very good contributions from the community are ignored completely (as it was the case with the CMS I used before).

    Cheers,
    Jan
      This message has been ROT-13 encrypted twice for higher security.
      • 28215
      • 4,149 Posts
      Quote from: enigmatic_user at Feb 16, 2010, 09:50 PM

      I suspected something like this. It’s impossible to have an installation that’s up to date - I downloaded rev6373 about 45 minutes ago, and now there’s rev6375. wink I’m really happy that I chose MODx as new CMS for my customers and myself. smiley It’s so frustrating when there’s almost no development and even very good contributions from the community are ignored completely (as it was the case with the CMS I used before).

      Great! We’re glad you chose MODx.

      That said, for Revolution, we’d really like to get more developers on it - especially with regards to Extras development. Right now the core team for Revo is small, but very active. And of course, MODx development is powered pretty much by donations and community support - so the community here, and those that contribute, are the real force behind MODx; far more so than the code.
        shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
        • 8898
        • 181 Posts
        Quote from: splittingred at Feb 16, 2010, 10:15 PM

        That said, for Revolution, we’d really like to get more developers on it - especially with regards to Extras development.
        Well, an almost complete German translation is waiting to be posted (some parts of the package_builder topic and a few other phrases are missing), and I’ll see if there’s anything else I can do for MODx (apart from reporting bugs etc.). wink

        Cheers,
        Jan
          This message has been ROT-13 encrypted twice for higher security.
          • 9757
          • 82 Posts
          Hi there, I’m working on Polish translation for Revolution and I really need your component, but I’m getting an error :/

          After I choose language (no matter which one - English fails too) for Core namespace I’m getting an error:
          Fatal error: Call to a member function read() on a non-object in /home/user/domains/domain.net/public_html/modxrevolution/core/components/languagebuilder/processors/checks/full.php  on line 104
          


          Everything is fine when I select any other namespace (e.g.: languagebuilder). I’ve got green notification:
          Your language translation is complete.


          Any ideas what’s wrong?
            • 28215
            • 4,149 Posts
            Fixedmachine:

            The path it’s trying to find there is: $modx->getOption(’base_path’) . ’setup/lang/en/’

            Did you remove your setup/ directory? You’ll need it (and actually, setup/lang/en/ as well) to work with Language Builder, as LB checks to make sure you’ve translated the language files in setup/ as well.
              shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
              • 9757
              • 82 Posts
              Oh, that’s it smiley I deleted setup folder. Thnx for help smiley
                • 8898
                • 181 Posts
                Hm, as I wrote in another thread, I updated from rev6618 to rev6773. There was a little problem with the lexicons, so I emptied the lexicon_entries table and pressed the button "Revert All Core Entries" in the Lexicon Manager. If I remember correctly, in older versions this pushed the changed phrases from the lexicon files to the database. But the table stays empty. This doesn’t seem to be a big problem - the Manager UI is displayed correctly -, but by chance I saw that the Language Builder now just exports the setup language files; the core lexicons are missing (presumably because they are read from the database, not from the files).

                Is there an easy way to copy the phrases to the database again or do I have to write a little script for it? Now that the other two lexicon database tables are gone, how are the topics identified? huh By name? In older versions there were IDs of the topics table.

                Or is the Language Builder now completely obsolete? huh

                Thank you very much in advance for any hint.

                Cheers,
                Jan
                  This message has been ROT-13 encrypted twice for higher security.
                  • 28215
                  • 4,149 Posts
                  Quote from: enigmatic_user at May 07, 2010, 12:47 PM

                  Or is the Language Builder now completely obsolete? huh
                  Yes.

                  Languages can now be translated by just translating the *.inc.php files, and creating a directory in the core/lexicon with the IANA language (eg, ’fr’ for french, ’es’ for spanish, etc).

                  They can then be submitted as an SVN patch, or as a zip file on a forum post - same as Evolution - for addition into the SVN branch.

                  Basically, DB entries are now only for overrides. See this post for details: http://modxcms.com/forums/index.php/topic,49077.0.html
                    shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com
                    • 8898
                    • 181 Posts
                    Thank you very much for your reply!

                    Cheers,
                    Jan
                      This message has been ROT-13 encrypted twice for higher security.