the MRH Forum

Forum move status as of Dec 2, 2021 MRH forum help
Reply
MRH Founder 17,437 posts joef MRH Founder 17,437 posts
joef
Just wanted to let you know the new forum conversion bugs have been fixed and we're trying a new load. However, I did not yet run my forum resequence fix. I'm mainly interested in seeing that the developers have fixed all their bugs. At this point I'm pretty confident my forum resequencing fix will nail the out-of-sequence problem. The fix algorithm is pretty straightforward and simple, so I'm confident it will do the job. But we're going to miss doing a conversion this weekend, Dec 4th. Not enough time to do a test reload and then check it. At this point, we're targeting the weekend of December 18th for the new go-live. Assuming the developers have fixed all the nasty bugs we've asked them to fix, then we will do the resequencing fix and then lock this forum and go live on the new forum the weekend of Dec 18. So that's the plan at this point. Unless something really ugly in new bugs crops up, we're going live on Dec 18th come you-know-what or high water.

Joe Fugate​
Publisher, Model Railroad Hobbyist magazine

[siskiyouBtn]

Read my blog
Reply 0
joef MRH Founder 17,437 posts
joef

How my resequencing fix works

My resequencing fix involves exporting all the thread ids, post ids, and timestamps to a spreadsheet.

Then I sort the spreadsheet by thread id and within that by post id. That's the sequencing that drupal uses.

Then I make a copy of the spreadsheet on a new tab and sort that one by thread id and within that by timestamp. That's the sequencing the new forum uses.

Then I copy the resorted timestamp column and paste it into the first spreadsheet as a new column.

Finally, I compare my resorted timestamp column to the original timestamp column that was sorted by post id. If I find any timestamp difference, I generate a database update statement for that post id that changes the timestamp to the resorted timestamp value.

The result is I do not generate any "fake" timestamps. I simply take all the timestamps in the current thread and resort them top to bottom and if they're out-of-whack at all, I replace them with the resorted timestamp value for that post.

This process seems pretty solid and should do the job.

Joe Fugate​
Publisher, Model Railroad Hobbyist magazine

[siskiyouBtn]

Read my blog
Reply 0
kleaverjr Prolific poster 2,858 posts
kleaverjr

Seems rather simple...

It reminds me of something similar where my dad had a Spreadsheet that listed all of the "jobs" (he was working for a gear manufacturer that had several pieces of equipment running  and they had several different orders to deal with, each with their own priority).  But as time went on the priorities would change and my dad would have to manually re-sequence them in excel, and it would take 2-3 hours.  Once I understood what needed to be done, I went and wrote a VBA macro.  It did the job in under 10 seconds! His boss at work, when I met him, thanked me for writing that program!  If there are a huge number of these posts that needed to be fixed, I wonder if a VBA would go faster than having to do it manually as you described.

FWIW.

Ken L
Reply 0
Mustangok Frequent poster 964 posts
Mustangok

Forward and don't look back

As the self appointed spokesman for any other MRH subscribers who have no idea what you're talking about, I say rock on brother. We're behind you all the way.

Kent B
Reply 0
glenng6 Regular poster 319 posts
glenng6

The Light at the...

Don't want to say it out loud. I am sure you could use a vacation and some sleep. Glenn
Reply 0
Reply