We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 17673
    • 194 Posts
    Quote from: rthrash at Aug 11, 2009, 07:34 AM

    It had to have been an upgrade and the installer wasn’t run in upgrade mode. The installer should update all instances to MODx Carbon theme.

    Does this mean that previous themes are not available in 1.0 ?!?

    I run the install in upgrade mode, I still see MOdxGreen, MODxLight etc listed in the Interfaces&features tab of the configuration page and the corresponding folders in manager/media/style; but, if I choose any theme different from MODxCarbon and save, I get the ’Action completed succesfully’ message, then the manager reloads but stays on the MODxCarbon ’bluish’ theme.

    I also tried editing the siteCache.idx.php file with ’$c[’manager_theme’] = "MODxGreen"’, no effect either.

    ?

    ciao
      ----------------------------------------------------------
      http://www.linkedin.com/in/lucapost/
      http://www.twitter.com/lukwe/
      ----------------------------------------------------------
      • 15001
      • 697 Posts
      I folks,

      I know this thread is quite old, but I think I have the solution to most of post-setup problems that you meet: for a few languages (Spanish and others), lacks the "UTF-8" version of the language file.

      What to do in such case (if you chose UTF-8 encoding during MODx setup):
      1) Go to manager/includes/lang
      2) Check that the "UTF-8" version of your language exists.
      3) If, not duplicate the right language file and rename it to "YourLanguage"-UTF8.inc.php (e.g. spanish-UTF8.inc.php).
      4) Then, open it with Notepad or an UTF-8 editor and save it, taking care that UTF-8 encoding is chosen.

      Above procedure should solve most problems.
      Sometimes, you’ll also need to create a UTF-8 language for your snippet/module/plugin.

      All do not have two (ANSI + UTF-8) files for each language.
      In the past, I met such problem with the spForm snippet.

      This error is typical from a UTF-8 language file lacking in MODx config.
      "Error: Missing argument 2 for AjaxSearch::AjaxSearch(), ..."

      I think it would be good idea that MODx developpers refuse including a language file in the core if the equivalent UTF-8 file is not furnished.

      Regards.

      Julien
        • 38733
        • 22 Posts
        Quote from: dcorbett at Aug 09, 2009, 07:30 PM
        To get around this, I downloaded the 0.9.6.3 version and got the style from there. In fact, there are four styles (MODx, MODxGreen, MODxLight and MODxRTL) in 0.9.6.3, none of which are in 1.0.

        Thanks to this paragraph zen from three years ago, I could get an older extra (EasyPoll) to look right again by downloading 0.9.6.3 and adding these old themes to my latest Evo.

        If you have an extra that needs them and they're missing, the "try MODx" site is kind enough to still offer 0.9.6.3 and earlier to download: Older MODx Releases [ed. note: ssanders last edited this post 13 years, 9 months ago.]