We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31205
    • 12 Posts
    Hello everybody!
    After moving local site to a remote server, on some pages Russian text became question marks:
    http://www.steptolove.com/modx/index.php?id=5
    but some pages are shown as they are supposed to:
    http://www.steptolove.com/modx/index.php?id=3
    I don’t know what a the problem is, but in database all text is fine and modx character setting is set correctly (to win-1251), page encording is also correct.
    I would really appreciate any help, cause I’ve killed a whole lot of time trying to figure out solution.
    Thank you in advance!

    Vadim
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Well, in the first place I would suggest never using any charset except utf-8. It has been my experience that anything else will have intermittent encoding problems. That means in the database as well.
        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
        • 31337
        • 258 Posts
        This looks like an issue with DB storage rather than browser display. If you look at the source for the broken page, you can see Russian entities in some of the code, yet others are displayed as huh

        This tells me that the data itself is not being stored properly in the DB. Can you look at the DB tables and confirm how the data is stored there please?
          • 31337
          • 258 Posts
          Quote from: sottwell at Oct 03, 2006, 04:24 AM

          Well, in the first place I would suggest never using any charset except utf-8. It has been my experience that anything else will have intermittent encoding problems. That means in the database as well.

          Unfortunately that doesn’t work right for all languages, and certainly not for Cyrillic charsets. Without going into the painful details of why this is so (and why it sucks), it’s still sometimes necessary to present the proper chartype to the browser. Although I suspect you could probably get away with just utf-8 storage on the DB side.
            • 22815
            • 1,097 Posts
            When the site was moved from a local server to a hosted server, presumably the DB was exported and imported as well. Hopefully this issue came about at that stage, which would make sense because that’s a point at which the data is being saved to a text file and then loaded again. This would mean that the export/import can be repeated correctly to fix the problem.

            An essy way to confirm that this is the case would be to browse the data in phpMyAdmin both locally and remotely to compare them.

            If this is the issue, how was this import/export done in this case? Was it with MODx’s export facility or phpMyAdmin or what?
            Even though this doesn’t affect me, I’d like to know the best practice so we can add it to an FAQ.
              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!
              • 897
              • 1,620 Posts
              Aleksey Stepanov Reply #6, 20 years ago
              man! go to russian community subforum. we talk about this many times. smiley

              p.s. sorry or my english
                "Und wenn du lange in einen Abgrund blickst, blickt der Abgrund auch in dich hinein."

                Не используйте Revo для "просто сайтов". Используйте Evo

                Who can defeat the Russian bear?