All threads marked UNREAD after new installation

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • chrismk
    Member
    • Aug 2006
    • 44
    • 3.6.x

    All threads marked UNREAD after new installation

    I have installed 4.2.5 on a new server.
    The previous location was running 3.8.8.
    I backed this up and then installed 3.8.11 on the new server and imported the database.
    I then upgraded to 4.2.5

    All seems to have gone well.
    I notice that all my threads are marked as unread.
    The new server isn't live yet but I can imagine users might be a bit peeved.
    Can I resolve this?

    Thanks.
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24286
    • 6.0.X

    #2
    Originally posted by chrismk
    I have installed 4.2.5 on a new server.
    The previous location was running 3.8.8.
    I backed this up and then installed 3.8.11 on the new server and imported the database.
    I then upgraded to 4.2.5

    All seems to have gone well.
    I notice that all my threads are marked as unread.
    The new server isn't live yet but I can imagine users might be a bit peeved.
    Can I resolve this?

    Thanks.
    Unless you were already using database-based thread marking (now the only option in 4.2.5), then this is expected behaviour since it will have been donwe with cookies.
    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

    • stingray27
      Member
      • Aug 2006
      • 49
      • 3.6.x

      #3
      Thats expected if you previously used cookie read marking, which was removed in 4.2.5 & 3.8.11 (both use the newer database marking).
      This is my signature.

      Comment

      • chrismk
        Member
        • Aug 2006
        • 44
        • 3.6.x

        #4
        OK, thanks.
        Presumably users can mark the forum read which would solve the issue if they found it a problem.

        Are there any ramifications for changing the thread marking to option 3 on the existing 3.8.8 database before backing up and moving it in a couple of weeks?

        Comment

        • Mark.B
          vBulletin Support
          • Feb 2004
          • 24286
          • 6.0.X

          #5
          Originally posted by chrismk
          OK, thanks.
          Presumably users can mark the forum read which would solve the issue if they found it a problem.

          Are there any ramifications for changing the thread marking to option 3 on the existing 3.8.8 database before backing up and moving it in a couple of weeks?
          That wouldn't cause any issues, no.
          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

          • chrismk
            Member
            • Aug 2006
            • 44
            • 3.6.x

            #6
            Thank you!

            Comment

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