Announcement

Collapse
No announcement yet.

Fancy URLs and special characters, ,, don't work

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

  • [Forum] Fancy URLs and special characters, ,, don't work

    When creating a thread in forum with special chatacters the characters are not replaced at all!

    That results in invalid links to the threads, breaks the site.

    What to do?

    ---

    In blog and CMS they are just removed in the URL

    --> ''
    --> ''
    --> ''

    ---

    They should be replaced with in all; forum/cms/blog

    --> a
    --> a
    --> o

  • #2
    Check out the following post Friendly URLs and Character
    The ono utf-8/ascii characters are stripped for now. later updates will fix this problem.
    I have already found the solution for this issue, if we don't get it sorted out in the next release, I will post a guide to how display non utf-8/ascii urls correctly
    while(true){
    if(
    $someone->needsHelp() && $i->canHelp()) $post->help();
    if(
    $i->findBug()) $post->bug();
    }

    Comment


    • #3
      Thanks Dody.

      No they are not stripped in forum at all. Only in CMS and blog. That's the problem. My forum is broken this way.

      Can't believe honestly that such problems excist in a gold release. It is a simple characters replacement in one of the functions.

      Comment


      • #4
        The problem is harder than you think, however we are promised to get it fixed in the upcoming updates.
        while(true){
        if(
        $someone->needsHelp() && $i->canHelp()) $post->help();
        if(
        $i->findBug()) $post->bug();
        }

        Comment


        • #5
          I understand, but until then vB is useless, since it can't be used. Creating threads with ,, in the title breaks the forum completely.

          Comment


          • #6
            You can disable the friendly urls until this is fixed.
            while(true){
            if(
            $someone->needsHelp() && $i->canHelp()) $post->help();
            if(
            $i->findBug()) $post->bug();
            }

            Comment


            • #7
              That was an upgrade, I have nor reinstalled GOld and I get the same behaviour of forum, blog and CMS: basically stripped characters. If somebody have a fix to replace characters before the stripping takes part, please advise.

              --> a
              --> a
              --> o

              Comment


              • #8
                hi,

                this is gold not a alpha. this must work now. the time of emty words is now over

                Comment


                • #9
                  This is a known issue and will be fixed in future versions - http://www.vbulletin.com/forum/entry...-and-Character

                  Comment


                  • #10
                    I can understand that Andreas, but this a GOLD release, so it is interesting to know how long we have to wait for a basic thing that should have been fixed before releasing a major update like this. I also get that this is more coplex issue for languages like chinese, korean and so on, but in this case it is about simple characters replace.

                    I mainly looking for a quick fix at this time, since it is just really bad that we have to wait for a fix, not defined when it is comming.

                    Comment


                    • #11
                      terabyte, I told you they are working on a fix that will be released in the upcoming updates.
                      A temporary solution will require modifying php codes, you can read about it here http://www.vbulletin.com/forum/proje...?issueid=33951
                      while(true){
                      if(
                      $someone->needsHelp() && $i->canHelp()) $post->help();
                      if(
                      $i->findBug()) $post->bug();
                      }

                      Comment


                      • #12
                        I'm not sure what the problem is here.

                        This is a known problem. After all, it's not as if vBulletin are denying there's a problem or just burying their head in the sand.

                        If you knew this was going to be a problem for you, why on earth did you upgrade from version 3.x?

                        Wouldn't it have been more sensible to wait until the vBulletin staff had found a fix?

                        Comment


                        • #13
                          Is not Gold something with all architectural bugs fixed? This one is well known and discussed here for months!

                          Comment


                          • #14
                            Originally posted by smudgersmiffy View Post
                            I'm not sure what the problem is here.

                            This is a known problem. After all, it's not as if vBulletin are denying there's a problem or just burying their head in the sand.

                            If you knew this was going to be a problem for you, why on earth did you upgrade from version 3.x?

                            Wouldn't it have been more sensible to wait until the vBulletin staff had found a fix?
                            Have I said that I was aware of the problem? I didn't upgrade a live site, but I don't want to pay for a product (three licenses) that has gone gold, where basic stuff don't work.

                            Comment


                            • #15
                              Originally posted by Dody View Post
                              terabyte, I told you they are working on a fix that will be released in the upcoming updates.
                              A temporary solution will require modifying php codes, you can read about it here http://www.vbulletin.com/forum/proje...?issueid=33951
                              Could you just point me to the right php file with the clean-function and I will take a look at it myself. Thanks.

                              Comment

                              widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
                              Working...
                              X