Sponsored Content
The Lounge What is on Your Mind? Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations Post 303045699 by Neo on Thursday 9th of April 2020 08:55:45 AM
Old 04-09-2020
It has been a few days since my last status update, so here is a new, quick one:

@Scrutiziner and @Neo continue to work on the migration and are getting closer. The migration script provided OOTB by Discourse (the various BBCODE converters) mangled a lot of text; and @Scrutinzer has been leading the effort to get the various bbcode conversions as error free as practical. So far, so good.

Today, after more discussions with @Scrutinzer, I modified a Discourse theme component and added four new editor / composer buttons:

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


This was my first Discourse theme component modification, and frankly speaking, it was really easy (orders of magnitude easier, and infinitely faster debugging, than Discourse plugin development and testing).

That modified theme component is available on GitHub as md-composer-extras-neo

Code:
https://github.com/unixneo/md-composer-extras-neo

Frankly, we don't want to get too much into editor / composer button modifications until people use it more; so this will probably be the only changes to the composer before going live (sooner than later). We can look for better icons on FontAwesome and get input from the people who matter the most, all of you!

@Scruitizer informs that he is getting closer to have his new Ruby preprocessing script ready for testing against the database, and he says he has been having a lot of fun with Ruby as well!

More later.....
These 2 Users Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script migration issues

Hi All, We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view. I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
Discussion started by: arvindcgi
4 Replies

2. HP-UX

Migration - Compiler Issues.

All, We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers. HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800) HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Discussion started by: helper
2 Replies

3. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

Dear Team I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update ) Scenario We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies

4. What is on Your Mind?

Status of Migration of Moderation Systems

First a bit of history .... A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
Discussion started by: Neo
1 Replies

5. 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

6. 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
ALSEARCH(1)						User Contributed Perl Documentation					       ALSEARCH(1)

NAME
alsearch - Search the AudioLink database for music SYNOPSIS
alsearch [OPTION]... search_option... --td=/some/path/to/create/links/ alsearch [OPTION]... search_option... -s DESCRIPTION
You can use this script to search for songs in the AudioLink database. You can specify one or several options for the artist, composer, lyricist, album, etc., as the search criteria. You can specify several search_option options to search for particular music files. See the section on "search options" for the list of options. The search is not case sensitive. alsearch looks for strings as well as sub-strings in the fields being searched. See the "examples" section for more information. Specifying the --td (target directory) option is mandatory for creating links to the actual files. This directory will contain the symbolic links to the actual audio files. The directory will be created if it doesn't exist. Creating symbolic links to the actual files is analogous to creating playlists in audio-playing software. Symbolic links are actually just point to the actual files on the hard disk. This way of creating and storing playlists is very useful in several ways, some of which are: 1. Compatible across various audio players Since the "playlists" are actually files represented on your hard disk, you can add whole directories generated by the alsearch program in the playlist of your audio software. If you switch to another music player for whatever reason, you still have your playlists. You don't have to bother about compatibility between the playlist formats of the two players. 2. Can be seen and operated upon in a file browser As the symbolic links are present on a file-system, your playlist collection can be viewed by using normal file operations in the shell or using a GUI-based file browsing program. If the file browsing program is supports file traversals and symlinks, it'll show you the information of the actual song. OPTIONS
--help Brief usage information --host=xxx Connects to the MySQL server on the target host. Default is localhost. --pass=xxx Password for the database -s, --na Just displays the search results, doesn't create links (simulation mode) --td=xxx Target-directory in which to create links --user=xxx Username for the database -v, --verbose Displays some extra information. Useful for spotting errors and sending debug information. SEARCH OPTIONS
--album=xxx Search in the "album" field --artist=xxx Search in the artist/band/performers fields. You can give this option multiple times, for example: "alsearch --artist=kishore --artist=asha --td=/songs/asha_kishore" --comment=xxx Search in the "comment" field -c, --composer=xxx Search in the "composer" field --genre=xxx Search in the "genre" field -l, --lyricist=xxx Search in the "lyricist" field --title=xxx Search in the "title" field EXAMPLES
The options that take arguments can be specified in two ways: "alsearch --artist="kishore kumar" --td=/songs/kishore" "alsearch --artist "kishore kumar" --td /songs/kishore" That is, the option and the argument can be separated with a ' ' (space) or an '=' (equal) sign. In case you want to search for a string that has spaces, enclose the string in " ". "alsearch --artist=kishore --composer=burman --lyricist=bakshi" Will search for songs sung by *Kishore*, composed by *Burman* and written by *Bakshi*. Any name in the composer field which have "burman" in them will be matched. This means, it'll find songs composed by RD Burman, SD Burman, etc. This is true for all search fields. SEE ALSO
L<audiolink(1)>, L<alfilldb(1)> The current version of this man page is available on the AudioLink website at <http://audiolink.sourceforge.net/>. BUGS
Report bugs related to the AudioLink software or the man pages to the audiolink-devel mailing list <audiolink-devel@lists.sourceforge.net>. AUTHOR
This manual page is written and maintained by Amit Shah <amitshah@gmx.net> COPYRIGHT
The AudioLink package is Copyright (C) 2003, Amit Shah <amitshah@gmx.net>. All the programs and the documentation that come as part of AudioLink are licensed by the GNU General Public License v2 (GPLv2). perl v5.14.2 2003-12-06 ALSEARCH(1)
All times are GMT -4. The time now is 08:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy