Yes it does..perfectly even :D

thanks again for your contribution :)

bandersen;
1. There's a fix somewhere in this thread.
2. I'll fix this tomorrow:)
3. Thats the mini-rating system. When a tutorial gets a certain amount of votes, it'll be classified as a good tutorial. I'll make a better one soon.

I tried the below... but code didn't match for 1.3:
I changed the numbers in the following string with no html success (line 267 in tutorial.php):

$tut['text'] = bbcodeparse2($tut['tutpagetext'],1,1,1,1);



[QUOTE=assassingod]iceman-x, Areku;


Areku;
1. https://vborg.vbsupport.ru/showpost....3&postcount=53


But use this as the replacement:

[QUOTE=bandersen]I tried the below... but code didn't match for 1.3:
I changed the numbers in the following string with no html success (line 267 in tutorial.php):

$tut['text'] = bbcodeparse2($tut['tutpagetext'],1,1,1,1);



I'll redo this for you tonight:)

Is it me or we get just the THUMBS DOWN icon on every tutorial?

Also, where do I allow HTML posting?

Thanks!

Until it gets a certain ammount of votes, it'll stay with thumbs down. 1.4 will have a better system that the current one.

I don't think this is a nice way to display it... I mean, there may be old well known and good tutorials ported to your system which require thumbs up ;)

What about the HTML? ;)

Err... something weird has happened...

I upgraded from old hack version to 1.3 and now all the tutorials miss the NEW LINE codes, ie instead of reading:

This is line1
This is line2
This is line3

I get

This is line1This is line2This is line3

Ideas?

UPDATE: Well, actually no VB code is being converted at all!

Edit:
I don't understand what you did. Did you upgrade?

I:

1) Downloaded
"// Tutorial Hack
// Coded By: assassingod

// Version: 1.3
"

from the first thread.

2) Ran the queries missing in the version I installed earlier

3) Added the new templates, updated the old ones with the new codes

4) Made the required changes on the files

5) Moderated old tutorials to appear on the new v1.3

Now, no BB code is parsed, although is stored correctly in the DB.

Ideas?