Announcement

Collapse
No announcement yet.

Problem in convert thread links to vbulletin 5 syntax links

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

  • Wayne Luke
    replied
    Then you would just need to use vBulletin 4's rewrite rules at the top of your new vBulletin 5 .htaccess file.

    Leave a comment:


  • germaninfl
    replied

    Leave a comment:


  • germaninfl
    replied
    ok, got it, so basically what I need to do is

    (example)

    rewrite
    https://mysite.com/threads/427-This-is-a-thread
    back to
    https://mysite.com/showthread.php?t=427

    Assuming I can figure this out (don't have too much knowledge with that),
    can I put the code for it at the beginning of .htaccess and after that conversion VB5 will rewrite once again to the new format?

    This is BTW not any custom mod. This rewrite option was part of VB 4.2.5 without any mods

    Edit : see attached screenshot for my setting in 4.2.5 (no custom addons used)
    Last edited by germaninfl; Sat 7 Apr '18, 7:20am. Reason: added screenshot from vb 4.2.5

    Leave a comment:


  • Wayne Luke
    replied
    We can't provide support for custom URLS such as this. The mod_rewrite addon you used previously should have the rules you need to convert them to default vBulletin 4.X links. Once they are redirected to that format, vBulletin 5 can redirect them to the new 5.X URL format.

    Leave a comment:


  • germaninfl
    replied
    I'm looking at the same issue. My site is indexed by google in the vb4 format:
    http://mysite.com/forums/31-sample-forum
    http://mysite.com/threads/16330-sample-thread

    Is there no way to rewrite these links to the new vb5 format using .htaccess ?

    Leave a comment:


  • Wayne Luke
    replied
    You would have been using rewrites to convert your custom links to ones vBulletin 4.X understood. You should be able to add those same rewrites to the vBulletin 5 configuration before:
    Code:
            # process any php scripts, not found gets redirected through routestring
            location ~ \.php$ {
                    # handles legacy scripts
                    if (!-f $request_filename) {
                            rewrite ^/(.*)$ /index.php?routestring=$1 break;
                    }
    
                    fastcgi_split_path_info ^(.+\.php)(.*)$;
                    fastcgi_pass phpfastcgi;
                    fastcgi_index index.php;
                    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                    include fastcgi_params;
                    fastcgi_param QUERY_STRING $query_string;
                    fastcgi_param REQUEST_METHOD $request_method;
                    fastcgi_param CONTENT_TYPE $content_type;
                    fastcgi_param CONTENT_LENGTH $content_length;
                    fastcgi_intercept_errors on;
                    fastcgi_ignore_client_abort off;
                    fastcgi_connect_timeout 60;
                    fastcgi_send_timeout 180;
                    fastcgi_read_timeout 180;
                    fastcgi_buffers 256 16k;
                    fastcgi_buffer_size 32k;
                    fastcgi_temp_file_write_size 256k;
            }
    vBulletin 5 already has handling to redirect old vBulletin 4 URLs using 301 redirects. If that doesn't work, you'll need to discuss this with your NGINX Server Administrator. They should be able to alter the configuration to fit your server.

    Leave a comment:


  • Problem in convert thread links to vbulletin 5 syntax links

    Hello dear friends.

    I want to move from vbulletin 4 to vbulletin 5, I install vbulletin 5 completely, my problem is that in vbulletin 4, all links are showen in the form of "http://example-site.com/forums/thread2968.html" and in vbulletin 5 syntax of links is changed completely.

    Currently all of my link's are registerd in the form of "thread2968.html" in google. To resolve this problem i want to use NGINX rewrite, so that i can convert vbulletin 4 thread post to the form of vbulletin 5, so my links dont fail in google search.

    Please help me to configure my Nginx and solve this problem.

Related Topics

Collapse

Working...
X