RC1 - import from xenforo to Woltlab -- Watched threads

  • Affected App
    WoltLab Suite Forum

    I believe this happened when importing attachment. I recall it importing the forums without issue and post and users and avatars all without issue. The last thing I recall was it was on attachments, I stepped out of the room and found this upon my return.


    edit: I was wrong. It got stuck on "Watched Threads" (made it to 76%)

    Edited once, last by Aslan (February 17, 2015 at 1:15 AM).

  • Hi

    could you please execute the following query in your database and attach / post the result:

    SQL
    SELECT   user_id, thread_id, COUNT(*) AS count
    FROM     xf_thread_watch
    GROUP BY user_id, thread_id
    HAVING   count > 1


    MySQL returned an empty result set (i.e. zero rows). (Query took 0.0001 seconds.)

  • Hi

    do you import from a live board or from a database dump? Both the code and the database export you attached look fine. I suspect that a member added a subscription to a thread, thus shifting all the later subscriptions dpwn by one, leading to a duplicate import of one subscription.

    Edit: Technical correction

  • Hi

    do you import from a live board or from a database dump? Both the code and the database export you attached look fine. I suspect that a member removed their subscription to a thread, thus shifting all the later subscriptions up by one, leading to a duplicate import of one subscription.

    It was indeed a live site... So perhaps the fault is my own. Don't mark this as "not a bug" just yet... Tonight when its not busy, I'll either do a dump and use that OR close the live site temporarily.

  • Well unfortunately, this does appear to be a bug. I could repeat more than once. Had both sites closed too this time. Always at 76% on Watched Threads.


  • Concerning threads, there are the following tables

    • xf_thread
    • xf_thread_prefix
    • xf_thread_prefix_group
    • xf_thread_read
    • xf_thread_redirect
    • xf_thread_reply_ban
    • xf_thread_user_post
    • xf_thread_view
    • xf_thread_watch

    One of those is loaded into memory (xf_thread_view). But I don't think that would be an issue.

    What I think is perhaps xf_thread_watch would have an association with xf_thread_read because it would seem logical (I believe) for you to keep an eye on what you're watching and haven't yet read would be xf_thread_read (obviously).

    So just for good measure I'm attaching that as well.

  • I finally got around to testing RC2 import. Same result.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!