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
TM::ObjectAble(3pm)					User Contributed Perl Documentation				       TM::ObjectAble(3pm)

NAME
TM::Synchronizable - Topic Maps, trait for storing objects into backends SYNOPSIS
my $tm = .... # get a topic map from somewhere use Class::Trait; Class::Trait->apply ($tm, "TM::ObjectAble"); my %store; # find yourself a proper store, can be anything HASHish # append it to the list of stores, or .... push @{ $tm->storages }, \%store; # prepend it to the list of stores unshift @{ $tm->storages }, \%store; # store it (the proper storage will take it) $tm->objectify ('tm:some-topic', "whatever object or data"); # get it back my @objects = $tm->object ('tm:some-topic', 'tm:some-topic2'); # get rid of it $tm->deobjectify ('tm:some-topic'); DESCRIPTION
This trait implements functionality to store arbitrary data on a per-topic basis. Conceptually, the storage can be thought as one large hash, as keys being use the internal topic identifiers, as values the object data. But to allow different topics to store their object data in different places, this interface works with a list of such hashes. Each hash (native or tied to some implementation) in the list is visited (starting from the start of the list) and can take over the storage. Whether this is based on the topic id, on some other topic information, or on the MIME type of the data (if it has one), is up to the implementation to decide. INTERFACE
Methods storages $listref = $tm->storages This method returns an array reference. You can "unshift" or "push" your storage implementation onto this list. Example: my %store1; push @{ $tm->storages }, \%store1 objectify $tm->objectify ($tid => $some_data, ...); This method stores actually the data. It takes a hash, with the topic id as keys and according values and tries to find for each of the pairs an appropriate storage. If none can be found, it will raise an exception. NOTE: Yes, this is a stupid name. deobjectify $tm->deobjectify ($tid, ...) This method removes any data stored for the provided topic(s). If no data can be found in the appropriate storage, an exception will be raised. object @objects = $tm->object ($tid, ...) This method returns any data stored for the provided objects. If no data can be found for a particular topic, then "undef" will be returned. SEE ALSO
TM AUTHOR INFORMATION
Copyright 20(10), Robert Barta <drrho@cpan.org>, All rights reserved. This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. http://www.perl.com/perl/misc/Artistic.html perl v5.10.1 2010-10-27 TM::ObjectAble(3pm)
All times are GMT -4. The time now is 07:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy