Dang, did you guys have your fingers on the trigger or what?
Sorry I've been out of touch.
Why not convert nothing. It's 2023, dump the data into a database, then replicate.
Text is easy, images and gifs will be a pain, but the text should be an easy drop kick.
of course I'm speaking at sales pitch 45k altitude and haven't ever dug into the sausage factory that this web forum is for certain.
my $0.02
Go with the KISS principle:
Keep
It
Simple
Stupid
Wendell,
Make it easy for yourself. I vote option #2.
As long as we can search the old database and create a new thread based upon it, that will be fine.
Besides, option #2 will prevent a 6 year old thread from popping up on top of the list when someone feels it is appropriate to comment on that old thread. Bugs the hell out of me!
I will deal with not having RPLS available for a day or two. It will be tough, but I think that I can make it. Fingers crossed.
JA, PLS, SoCal
Whichever works best for you, master.
Besides, option #2 will prevent a 6 year old thread from popping up on top of the list when someone feels it is appropriate to comment on that old thread. Bugs the hell out of me!
I wholeheartedly agree.
Wendell,
Make it easy for yourself. I vote option #2.
As long as we can search the old database and create a new thread based upon it, that will be fine.
Besides, option #2 will prevent a 6 year old thread from popping up on top of the list when someone feels it is appropriate to comment on that old thread. Bugs the hell out of me!
I will deal with not having RPLS available for a day or two. It will be tough, but I think that I can make it. Fingers crossed.
JA, PLS, SoCal
...AND GET OFF HIS LAWN TOO!!!!
JK
Of course, shortly after posting this, the developer had a breakthrough that is looking very promising. We'll see how it goes.
To address the old thread resurfacing issue, many of the forums would be placed in an archival location anyway, even if in the new system. That would reduce some of the phenomenon you describe from happening. I might also be able to find a way to lock threads after a specified amount of time.... like maybe a year or something like that. It is definitely something to consider, regardless of which way this thing goes.
Also, the generosity of this developer has been amazing. Despite all these crazy issues, he works through them to find a solution without charging for his time and to stay in budget. He's a super cool guy and we had a nice Zoom discussion this morning about everything. It's looking like he'll be ready by early next week. If the stars align, perhaps we can make the switch (no matter which option ends up being chosen) late next week.
If we have to get away from this perfect forum to begin with, I would prefer a clean slate of threads/topics with the option to view/reference them from their archived home. Option 2 is my vote.
Option 2 sounds like it would work quite well enough.
Go for Option 2. Life is to short for major headaches that aren't necessary.
Question, Can you link to the old, locked thread from within a new post if your were to execute option 2?
Do number 2 no questions asked.
Question, Can you link to the old, locked thread from within a new post if your were to execute option 2?
Yes. It would be available to view and grab a link, but not to reply directly.
So... a little backstory/reminder...
The reason I didn't originally consider Option #2 at all is basically because it's EXACTLY what POB did when they converted rpls.com to a new system -- which, as many of you will recall, is when beerleg.com was born. It makes me nervous, because I don't want to make the same mistake.
