Announcement

Collapse
No announcement yet.

Encoding problem when merging posts, after upgrade

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Wayne Luke
    replied
    Has your host installed the Greek Locale at the server level? I cannot do this for you.

    Has your host converted the database to UTF-8? I cannot do this for you.

    I also cannot fix bugs in vBulletin 4. I can only support the system as it is written.

    Leave a comment:


  • dimitrios
    replied
    Hi Wayne.

    The thing is: I set up vBulletin following the exact instructions. Your instructions. To the dot! Then it was working perfectly. Then an update messed up things.
    • I install vB following your instructions
    • I update often, through the years, when a new update is out, following your instructions
    • Everything works great
    • Then yet another update (following your instructions) and suddently I have an encoding problem
    • I open a ticket
    • You ask for database access, I give it to you.
    • Then after months of mostly inactivity and a sporadic trying this and trying that and telling me you cannot solve the problem, you tell me it's my problem.

    But, it's the vB update that messed up things!

    And if you cannot solve the problem, how am I ever going to be able to solve it?


    I never did anything else than following your instructions to the dot.

    And btw I am not the only greek forum to use vB and suffer from it the exact same way.

    So, instead of keep telling me it's my problem, why not accept it for what it really is: a huge problem caused by vB itself

    I know about the refrain that keeps coming back, that my database should be this and that encoding but please, allow me to repeat: The first time I ever created my database for the first vBulletin installation, was following your instructions! So the whatever encoding was set using your instructions.Then it was working perfectly for years. Then after a vB update, following your instructions again, I suddenly had encoding problems.

    I am not the only forum that's unhappy with running on vB, for the exact same reason. vB is buggy! Instead of helping fix the mess the software has caused, you keep repeating that it's not your fault and that it's our problem. But how can that be when we use your software following your exact instructions and the mess is caused after your update?

    I cannot tell you, Wayne, how let down I am by all this.

    I implore you, please fix my problem.

    I am enough outdated using non-responsive vB4 (instead of say free phpBB). Now I am outdated and buggy.

    Leave a comment:


  • Wayne Luke
    replied
    As said before you cannot use ISO-8859-7 if you want to use any kind of extended characters. By extended I mean anything not in the basic Latin Alphabet. You have to use UTF-8 and a UTF-8 Locale in the system. You must have mbstring and iconv installed in PHP. Your database must use a UTF-8 character set and collation.

    Leave a comment:


  • dimitrios
    replied
    Thanks Saeed.

    In the meanwhile, the problem is unbearable. Check here.

    vBulletin has grown into a very buggy software and you are left alone to deal with it.

    Leave a comment:


  • Saeed Fazlollahzadeh
    replied
    I do proceed certainly.
    Even if you weren't able to do such things, you can send me your sensitive data so that I can help you (if you wish, since I'm not the staff)

    Leave a comment:


  • dimitrios
    replied
    Dear Saeed, I am so pissed off by vBulletin, I cannot tell you.

    I wish I had used some other software back then. I have paid for it twice (v. 3 and v. 4) and I'm stuck with buggy software, with no real support about those bugs, and it's not even responsive! To get a responsive version I need to buy it again (v. 5) which I might have done already if I didn't know another Greek forum that is practically dying because of the v.5 bugs. It's been two years now and they are still fighting with the bugs.

    And all that when my other phpBB forum has costed me nothing, works perfectly fine, has none of all these encoding bugs and troubles, and is responsive (!) and all that... for free.

    I have weighted migrating to other software but that's a major operation by itself and I'm also afraid about how google is going to react to the change of the thread URLs. Of course, the migration option remains on the table since my forum looks out of date and it is problematic. Members keep complaining about not being able to register and we cannot even write properly in posts.

    Anyway. Since, I am practically left alone by the staff, I will proceed with your instructions. Please, do check for my progress here, now and then.

    Thanks a lot for trying to help. I appreciate it.
    Last edited by dimitrios; Mon 19th Feb '18, 8:55am.

    Leave a comment:


  • Saeed Fazlollahzadeh
    replied
    I understand you dimitrios. I'm not the staff here, but I'm the staff of some Persian and Iranian forums in my country Iran, and what I told you is my experience of some situations in such matters.
    You may submit a ticket at vbulletin.com or re-open the current one, but what I told is the thing that have been worked in some forums and have not been worked in some other forums (because the solution of theirs was something else).
    Please do this, if it didn't work, I'll tell you the other way.

    Leave a comment:


  • dimitrios
    replied
    Hi Saeed and thanks for trying to help. Usually I am very reluctant to follow any other's instructions that the staff's. Of course, now that I am practically left alone, in a problem caused by the software itself (other greek forum's suffer by such problems, too) I suppose I might have to reconsider.

    Would you mind telling me why you are proposing these instructions? What do you think this is going to work for me?

    Leave a comment:


  • Saeed Fazlollahzadeh
    replied
    Create backup.
    Go to AdminCP / Language and Phrases / Download/Upload Languages
    Download your current Greek language with all products (you may download multiple files, one for whole only vbulletin, one for post thanks, one for another one, ...).
    Again go to AdminCP / Languages and Phrases / Language Manager
    Delete Greek Language.
    Rebuild all languages in this part.
    If you're using Suite version (Blog+CMS), deactivate them before upgrading (or if you do not use them, delete them)
    Now run upgrade.
    You may still have problem with languages and phrases after upgrade.
    Add
    Code:
    define('DISABLE_HOOKS', true);
    after
    Code:
    <?php
    in /includes/config.php, now it should be like this
    Code:
    <?php
    define('DISABLE_HOOKS', true);
    If everything is now fine, now go AdminCP / Products and Plugins / Product Manager, and disable CMS and Blog.
    Change DISABLE_HOOKS like this
    Code:
    //define('DISABLE_HOOKS', true);
    Now see if everything works fine. If yes, Now again add Greek language you've downloaded before.

    Leave a comment:


  • dimitrios
    replied
    But why has it been working well and got messed after an update, all by itself?

    I've been following the instructions you give, from day 0. When I installed vB, 10 years back, and before every update, ever since. Checking requirements, too.

    And this is my biggest reservation. vB messes things, that becomes a major problem to me, my members and the overall performance, but then I'm left alone with a general instruction that bears no practical value.

    Leave a comment:


  • Wayne Luke
    replied
    In your version, UTF-8 characters are stored as HTML Entities. This is the same in vBulletin 4.2.2 and vBulletin 4.2.5. The only way to fix the issue is to make sure that every aspect of your server from the operating system to vBulletin is running UTF-8 and that you're using PHP 7 with mbstring and iconv as already stated to you multiple times. We cannot provide a different answer.

    Operating System: UTF-8
    Database: UTF-8
    EVERY TABLE: UTF-8
    Every Field in every table: UTF-8
    PHP using iconv and MBString
    vBulletin Language using a UTF-8 Locale.
    Every date override filled in to fit your needs.

    This is the same solution that we've been promoting for UTF-8 issues for years.

    Leave a comment:


  • dimitrios
    replied
    So, what next?

    Even if we suppose that you cannot replicate the one symptom (when merging posts; which btw is something we experience on a constant basis) the other half is always there for everyone to see: when you enter extended latin: etc. it appears in html codes: &#225; &#243; &#253; &#237; &#241; &#252; etc. (check this thread)

    It's been months since I mentioned the problem, since I opened a ticket, since I started checking on a very constant basis to see how we are progressing. But it seems that nothing much happens.

    This problem is connected to registration issues, too, and I'm missing registrations month after month.

    I mean, I wonder, what do you expect of me? That I will drop the issue and let it slip into oblivion? Or that I will keep checking while growing old? We have to live with the gibberish texts every day.

    It was October 2017, November came by, then December, then January, it's February 2018 now. The way things are going (they are not) I'm sure that we are going to reach summer, then winter, then yet another year.

    What next?

    ( I apologize if I seem to have an attitude. If you scroll up you will notice that I have always tried to be polite and understanding. But now I start to wonder, who is going to show understanding towards my troubles caused by the vB update? )

    Thanks for your attention.

    Leave a comment:


  • dimitrios
    replied
    But why did the vB update messed the database so bad and now I am charged with such a heavy load?

    This cannot be the proper way to do things, can it?

    Anyway, I am willing to follow instructions how to solve all this mess. Can anyone direct me?

    Leave a comment:


  • Wayne Luke
    replied
    You will need to make sure all tables and all fields within each table have the same character set and collation. It is the only fix for mixed collation errors.

    Leave a comment:


  • dimitrios
    replied
    anyone?

    Leave a comment:

Related Topics

Collapse

Working...
X