Sponsored Content
The Lounge What is on Your Mind? New Migration Tool: Link to Discourse Community Topic from vB Thread Tools Menu Post 303046179 by Neo on Monday 27th of April 2020 08:16:08 AM
Old 04-27-2020
New Migration Tool: Link to Discourse Community Topic from vB Thread Tools Menu

Dear All,

To help with migration data integrity checks, today I spend the day working on this and created a migration tool which I hope is useful.

Basically, I mapped all the new discourse topic ids to the original forum thread id and moved all that information to the mysql DB of this forum. I think the effort was worth it.

You can now visit the corresponding topic in the new forum via the thread drop down menu:

New Migration Tool:  Link to Discourse Community Topic from vB Thread Tools Menu-screen-shot-2020-04-27-70902-pmjpg


This feature is available only to registered users (for now).

It took me all day do get these mappings done and working; so I hope our great members find this tool useful.

Also note, if the thread has not been migrated yet, or for some reason it not in the mapping, there will be no "community menu item" in the thread tools menu.

Also note, if the thread is not in a public forum (for example a jailed thread in a spam forum or a topic in the moderator forum), this quick tool will (actually may) not work. This tool is only for publicly visible discussions threads.
These 3 Users Gave Thanks to Neo For This Post:
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

OK. Like we all do, we learn a lot from tests, test migrations, and so forth. Today, I started from scratch on test migration 2, armed with a lot more knowledge, The main differences are as follows: Installed discourse plugin ruby-bbcode-to-md before starting the install Modified... (30 Replies)
Discussion started by: Neo
30 Replies

2. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily: Insuring ruby-bbcode-to-markdown is enabled. Removing line breaks from ICODE to markdown in migration script. Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies

3. What is on Your Mind?

Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations

We "completed" the migration of this vB3 site to Discourse a number of days ago. However, deeper testing by @Scrutinizer and @MadeInGermany revealed that a lot of text was mangled in the migration. We traced these bugs to two issues: A minor bug in the Ruby vbulletin.rb migration script... (19 Replies)
Discussion started by: Neo
19 Replies
PTHREAD_DETACH(3)					     Linux Programmer's Manual						 PTHREAD_DETACH(3)

NAME
pthread_detach - detach a thread SYNOPSIS
#include <pthread.h> int pthread_detach(pthread_t thread); Compile and link with -pthread. DESCRIPTION
The pthread_detach() function marks the thread identified by thread as detached. When a detached thread terminates, its resources are automatically released back to the system without the need for another thread to join with the terminated thread. Attempting to detach an already detached thread results in unspecified behavior. RETURN VALUE
On success, pthread_detach() returns 0; on error, it returns an error number. ERRORS
EINVAL thread is not a joinable thread. ESRCH No thread with the ID thread could be found. CONFORMING TO
POSIX.1-2001. NOTES
Once a thread has been detached, it can't be joined with pthread_join(3) or be made joinable again. A new thread can be created in a detached state using pthread_attr_setdetachstate(3) to set the detached attribute of the attr argument of pthread_create(3). The detached attribute merely determines the behavior of the system when the thread terminates; it does not prevent the thread from being terminated if the process terminates using exit(3) (or equivalently, if the main thread returns). Either pthread_join(3) or pthread_detach() should be called for each thread that an application creates, so that system resources for the thread can be released. (But note that the resources of all threads are freed when the process terminates.) EXAMPLE
The following statement detaches the calling thread: pthread_detach(pthread_self()); SEE ALSO
pthread_attr_setdetachstate(3), pthread_cancel(3), pthread_create(3), pthread_exit(3), pthread_join(3), pthreads(7) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2008-11-27 PTHREAD_DETACH(3)
All times are GMT -4. The time now is 04:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy