Encoding problem when merging posts, after upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dimitrios
    Senior Member
    • Oct 2008
    • 302
    • 4.1.x

    [Forum] Encoding problem when merging posts, after upgrade

    Hi,
    A couple days back I've upgraded my greek forum from v 4.2.2. to v 4.2.5

    Now, we realize that when we merge posts, the resulted post appears gibberish.

    Why is that? What can I do to fix it?

    Thanks

  • Wayne Luke
    vBulletin Technical Support Lead
    • Aug 2000
    • 73981

    #2
    What is the encoding and character set of your language?

    AdminCP -> Languages & Phrases -> Language Manager. Edit your language's settings.
    Translations provided by Google.

    Wayne Luke
    The Rabid Badger - a vBulletin Cloud demonstration site.
    vBulletin 5 API

    Comment

    • dimitrios
      Senior Member
      • Oct 2008
      • 302
      • 4.1.x

      #3
      Hi, Wayne.

      It's ISO-8859-7

      Comment

      • Wayne Luke
        vBulletin Technical Support Lead
        • Aug 2000
        • 73981

        #4
        You should use UTF-8 with your site. If you have a backup, I suggest restoring it as a test installation and working with UTF-8 to see if the results improve.
        Translations provided by Google.

        Wayne Luke
        The Rabid Badger - a vBulletin Cloud demonstration site.
        vBulletin 5 API

        Comment

        • dimitrios
          Senior Member
          • Oct 2008
          • 302
          • 4.1.x

          #5
          This might be connected with an old problem of my forum, not showing extended latin correctly. (It's been 6 years, now, bearing this burden.) Here's a test thread, concerning my encoding problems.

          I've visited the db and I see it set as utf8_general_ci

          Like I've already said, in the AdminCP I see ISO-8859-7

          If I change that to UTF-8 the forum appears like in the picture shown.

          Is that it? Maybe putting the right encoding in the admincp would solve all my problems? And what would that be?Click image for larger version  Name:	encoding prob.jpg Views:	1 Size:	95.6 KB ID:	4379290

          Thanks

          Comment

          • Wayne Luke
            vBulletin Technical Support Lead
            • Aug 2000
            • 73981

            #6
            ISO-8859-7 is a subset of UTF-8. It is targetted for Greek. The Greek characters most likely replace the extended Latin characters. Switching the character encoding to UTF-8 should fix that. This is only what is sent to the browser. How it is stored in the database isn't relevant at this point.

            The question marks indicate that it doesn't know those characters which shouldn't happen in UTF-8. Some other issue is causing the problem. What are all of your language settings?
            Translations provided by Google.

            Wayne Luke
            The Rabid Badger - a vBulletin Cloud demonstration site.
            vBulletin 5 API

            Comment

            • dimitrios
              Senior Member
              • Oct 2008
              • 302
              • 4.1.x

              #7
              language code: el
              HTML Character Set: ISO-8859-7
              Locale: el_GR


              btw, when I edit the text, in the plain editor, the extended latin characters appear correctly.

              (That's not the case with the after-merging-gibberish, though)

              Click image for larger version

Name:	encoding problem 02.jpg
Views:	116
Size:	167.5 KB
ID:	4379311
              Last edited by dimitrios; Tue 17 Oct '17, 8:43pm.

              Comment

              • dimitrios
                Senior Member
                • Oct 2008
                • 302
                • 4.1.x

                #8
                Anyone?

                Comment

                • Wayne Luke
                  vBulletin Technical Support Lead
                  • Aug 2000
                  • 73981

                  #9
                  For the issue in post #5, you need to use a locale set to UTF-8. This is 'el_GR.UTF-8'. You need to verify with your host that this locale is installed at the operating system level.

                  Remove the troublesome characters and type them again. Then save. Do you have the same problem? If they were previously converted to HTML Entities, they will stay that way forever. HTML Entities is how older versions of vBulletin dealt with non-latin characters.

                  Translations provided by Google.

                  Wayne Luke
                  The Rabid Badger - a vBulletin Cloud demonstration site.
                  vBulletin 5 API

                  Comment

                  • dimitrios
                    Senior Member
                    • Oct 2008
                    • 302
                    • 4.1.x

                    #10
                    I asked the host and they say local el_GR.UTF-8 is installed.

                    Then I changed the locale in AdminCP > Languages and Phrases > Language Manager > Language Settings > Locale to el_GR.UTF-8

                    So, now I've got:
                    language code: el
                    HTML Character Set: ISO-8859-7
                    Locale: el_GR.UTF-8

                    Then I made a fresh post, using latin extended characters but they still appear in html code.

                    Comment

                    • alfreema
                      Senior Member
                      • Sep 2017
                      • 144
                      • 5.3.x

                      #11
                      Originally posted by dimitrios
                      Then I made a fresh post, using latin extended characters but they still appear in html code.

                      In Firefox, I am seeing two content-type headers being sent, which is odd.


                      Click image for larger version

Name:	Capture.PNG
Views:	95
Size:	152.7 KB
ID:	4379554

                      Comment

                      • Wayne Luke
                        vBulletin Technical Support Lead
                        • Aug 2000
                        • 73981

                        #12
                        We would need a copy of your database to have a developer look at the issue. Preferably one before the posts were merged so we can recreate the issue and revert back as needed.
                        Translations provided by Google.

                        Wayne Luke
                        The Rabid Badger - a vBulletin Cloud demonstration site.
                        vBulletin 5 API

                        Comment

                        • dimitrios
                          Senior Member
                          • Oct 2008
                          • 302
                          • 4.1.x

                          #13
                          It's easy. Where should I place the db for you to check? Should I open a ticket?

                          Thanks a lot for trying to help, btw
                          Last edited by dimitrios; Tue 24 Oct '17, 1:00pm.

                          Comment

                          • dimitrios
                            Senior Member
                            • Oct 2008
                            • 302
                            • 4.1.x

                            #14
                            Any direction as to this one?

                            thnx

                            Comment

                            • Wayne Luke
                              vBulletin Technical Support Lead
                              • Aug 2000
                              • 73981

                              #15
                              A ticket is the only way we can get the database information.
                              Translations provided by Google.

                              Wayne Luke
                              The Rabid Badger - a vBulletin Cloud demonstration site.
                              vBulletin 5 API

                              Comment

                              Related Topics

                              Collapse

                              Working...