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
hyperhelp(1)							  [incr Widgets]						      hyperhelp(1)

__________________________________________________________________________________________________________________________________________________

NAME
hyperhelp - Create and manipulate a hyperhelp widget SYNOPSIS
hyperhelp pathName ?options? INHERITANCE
itk::Toplevel <- shell <- hyperhelp STANDARD OPTIONS
activeBackground background borderWidth closecmd cursor exportSelection foreground highlightColor highlightThickness insertBackground insertBorderWidth insertOffTime insertOnTime insertWidth padX padY relief repeatDelay repeatInterval selectBackground selectBorderWidth selectForeground setGrid See the "options" manual entry for details on the standard options. ASSOCIATED OPTIONS
hscrollmode vscrollmode textbackground fontname fontsize fixedfont link linkhighlight width height state wrap unknownimage See the "scrolledhtml" widget manual entry for details on the above associated options. INHERITED OPTIONS
modality title See the "shell" manual entry for details on the above inherited options. WIDGET-SPECIFIC OPTIONS Name: topics Class: Topics Command-Line Switch: -topics Specifies a list of help topics in the form {?topic? ... }. Topic may either be a topic name, in which case the document associated with the topic should be in the file helpdir/topic.html, or it may be of the form {name file}. In the latter case, name is displayed in the topic menu, and selecting the name loads file. If file has a relative path, it is assumed to be relative to helpdir. Name: helpdir Class: Directory Command-Line Switch: -helpdir Specifies the directory where help files are located. Name: closeCmd Class: CloseCmd Command-Line Switch: -closecmd Specifies the tcl command to be executed when the close option is selected from the topics menu. Name: maxHistory Class: MaxHistory Command-Line Switch: -maxhistory Specifies the maximum number of entries stored in the history list Name: beforelink Class: BeforeLink Command-Line Switch: -beforelink Specifies a command to be eval'ed before a new link is displayed. The path of the link to be displayed is appended before evaling the command. A suggested use might be to busy the widget while a new page is being displayed. Name: afterlink Class: AfterLink Command-Line Switch: -afterlink Specifies a command to be eval'ed after a new link is completely displayed. The path of the link that was displayed is appended before evaling the command. __________________________________________________________________________________________________________________________________________________ DESCRIPTION
The hyperhelp command creates a shell window with a pulldown menu showing a list of topics. The topics are displayed by importing a HTML formatted file named helpdir/topic.html. For a list of supported HTML tags, see scrolledhtml(n). METHODS
The hyperhelp command creates a new Tcl command whose name is pathName. This command may be used to invoke various operations on the wid- get. It has the following general form: pathName option ?arg arg ...? Option and the args determine the exact behavior of the command. The following commands are possible for dialog widgets: INHERITED METHODS
activate center childsite deactivate See the "shell" manual entry for details on the above inherited methods. WIDGET-SPECIFIC METHODS pathName cget option Returns the current value of the configuration option given by option. Option may have any of the values accepted by the hyperhelp command. pathName configure ?option? ?value option value ...? Query or modify the configuration options of the widget. If no option is specified, returns a list describing all of the available options for pathName (see Tk_ConfigureInfo for information on the format of this list). If option is specified with no value, then the command returns a list describing the one named option (this list will be identical to the corresponding sublist of the value returned if no option is specified). If one or more option-value pairs are specified, then the command modifies the given widget option(s) to have the given value(s); in this case the command returns an empty string. Option may have any of the values accepted by the hyperhelp command. pathName showtopic topic Display html file helpdir/topic.html. Topic may optionally be of the form topicname#anchorname. In this form, either topicname or anchorname or both may be empty. If topicname is empty, the current topic is assumed. If anchorname is empty, the top of the docu- ment is assumed pathName followlink href Display html file href. Href may be optionally be of the form filename#anchorname. In this form, either filename or anchorname or both may be empty. If filename is empty, the current document is assumed. If anchorname is empty, the top of the document is assumed. pathName forward Display html file one forward in history list, if applicable. pathName back Display html file one back in history list, if applicable. EXAMPLE
hyperhelp .h -topics { Intro Help } -helpdir ~/help .h showtopic Intro AUTHOR
Kris Raney KEYWORDS
hyperhelp, html, help, shell, widget Tk hyperhelp(1)
All times are GMT -4. The time now is 04:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy