Existing internal links 404 after upgrade from 4 to 5.5.1

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sassyronin
    New Member
    • Apr 2013
    • 9
    • 5.0.0

    Existing internal links 404 after upgrade from 4 to 5.5.1

    After upgrading our vB4 to 5.5.1, none of the existing internal links (ones members posted to point to a different post) work. ("Invalid Page URL. If this is an error and the page should exist, please contact the system administrator and tell them how you got this message.")

    The thread and post numbers are completely different now, so I am at a loss regarding how to go about redirecting them. I believe I've read in here that vBulletin somehow tracks the relationship between old links and new ones, but that isn't working for me. Did I mess something up during the upgrade, perhaps? I ran most of the General Update Tools (excepting "Rebuild Statistics") after upgrading.

    Example old link: https://roninarmy.com/threads/149-Ja...ll=1#post51431

    Same link now: https://roninarmy.com/forum/atomic-t...7632#post77632

    Thanks!
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24287
    • 6.0.X

    #2
    Were you using vBSEO? Or similar?
    Only vB4 URLs from one of the default URL schemes will redirect. URLs from a third party system won’t.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • sassyronin
      New Member
      • Apr 2013
      • 9
      • 5.0.0

      #3
      Nope. Straight-up vBulletin. Do the topic and post IDs change by design during upgrade?

      Comment

      • sassyronin
        New Member
        • Apr 2013
        • 9
        • 5.0.0

        #4
        In my [prefix]_node table I see that nodeid and oldid for that post I referenced upthread are listed correctly as 204 and 149 respectively, which matches the same in the old broken link and the new working link I posted. It looks like the redirection is done using [prefix]_routenew. It might be a kludge, but I wonder if fixing those existing links would be as simple as (backing up and then) manually creating a row in routenew matching the broken link and routing them to the new path? Whatever the solution turns out to be, I'm glad that the database does seem to have the old and new ids stored.
        Last edited by sassyronin; Wed 1 May '19, 5:32pm. Reason: Fixing typo

        Comment

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

          #5
          You need to add your vBulletin mod_rewrite rules to the .htaccess. Particularly these lines:

          Code:
          # Forum
          RewriteRule ^threads/.* showthread.php [QSA]
          RewriteRule ^forums/.* forumdisplay.php [QSA]
          RewriteRule ^members/.* member.php [QSA]
          RewriteRule ^blogs/.* blog.php [QSA]
          RewriteRule ^entries/.* entry.php [QSA]
          Make sure these are under the RewriteBase directive and above the "Main Redirect Block".

          You should not change anything in the database. Doing so will render your site inoperable.
          Translations provided by Google.

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

          Comment

          • sassyronin
            New Member
            • Apr 2013
            • 9
            • 5.0.0

            #6
            Ahhhhhhh! That did the trick! I had pasted below said Main Redirect Block.

            Thank you!

            Comment

            Related Topics

            Collapse

            Working...