vb3 Postbit Style Option v1.0

What Does This Hack Do?
--
Allows for users to choose either the vb2 style postbit or the vb3 style postbit.
Note: Makes the vb3 setting 'legacypostbit' obsolete so that users can choose which postbit they prefer.

What To Do?
--
Queries To Run ( 1 )
File Modifications ( 9 )
includes/functions.php ( 2 )
profile.php ( 3 )
showpost.php ( 2 )
showthread.php ( 2 )
Template Modifications ( 1 )
modifyoptions template ( 1 )
Phrases To Add ( 4 )
postbit_style_title
postbit_style_desc
vb2_postbit
vb3_postbit

Note: Please respect my work, do not edit, modify, or redistribute in any form unless prior consent is given.
I would appreciate that if you installed this hack that you click install.

After viewing the discussion on vb.com though it can be done with no file modifications I choose this specific way because:

1. I don't like the postbit style option showing in with the profile fields it's better laid out in the user options under thread options.
2. I find it necessary to cache the posbit_legacy template. So if you want to get technical about file mods not needed, sure, but then you'll be running an extra query each time you load the showpost.php and showthread.php files if you use the vb2 postbit.

Screenshots and zip attached below. If you have any comments, suggestions, or concerns please share them here.

The postbit.gif screen shows the difference between vb2 style and vb3 style if you didn't know the difference.

Enjoy,
g-force2k2

[Dean C]

Thanks for releasing

[g-force2k2]

Originally Posted by Breaker

yeh, this can be done with 1 template edit and a few added fields

Yes, but then you will be running uncessary queries.

Thanks for the support Mist.

Cheers,
g-force2k2

[Link14716]

I ask you, how?

Good job, but it's a little overkill. First, I have the legacy postbit setting set to '0' in the settings. I make a profile field giving the user this option, and in my phpinclude_start template, I add an if statement to check the value of the profile field, and if it is set to the vB2 style, set $vboptions['legacypostibt'] to '1'.

No hacking required, no unneeded queries, just a simple template mod.

Nice work, but it's just overkill to do 9 file edits when none are needed.

[g-force2k2]

Originally Posted by Link14716

I ask you, how?

Good job, but it's a little overkill. First, I have the legacy postbit setting set to '0' in the settings. I make a profile field giving the user this option, and in my phpinclude_start template, I add an if statement to check the value of the profile field, and if it is set to the vB2 style, set $vboptions['legacypostibt'] to '1'.

No hacking required, no unneeded queries, just a simple template mod.

Nice work, but it's just overkill to do 9 file edits when none are needed.

Okay so you don't want to do unneeded queries, but by not making two file modifications you're running unnecessary queries, I don't see how people aren't understanding.

Originally Posted by g-force2k2

2. I find it necessary to cache the posbit_legacy template. So if you want to get technical about file mods not needed, sure, but then you'll be running an extra query each time you load the showpost.php and showthread.php files if you use the vb2 postbit.

Regards,
g-force2k2

[Link14716]

And where would those unnecessary queries come from? It's a simple profile field/if statement combination.

[g-force2k2]

Originally Posted by g-force2k2

2. I find it necessary to cache the posbit_legacy template. So if you want to get technical about file mods not needed, sure, but then you'll be running an extra query each time you load the showpost.php and showthread.php files if you use the vb2 postbit.

Run the debug mode you will see the template will be uncached by both showpost.php and showthread.php.

No you're right about the profilefield and if conditional no queries are required, but simply by using the postbit_legacy template it is not a cache'd template. My hack further optimizes that simple fact

Regards,
g-force2k2

[Link14716]

Yeah, I didn't see that part of your post. Shouldn't postbit_legacy be cached by default? *goes to file a bug report*

[g-force2k2]

Originally Posted by Link14716

Yeah, I didn't see that part of your post. Shouldn't postbit_legacy be cached by default? *goes to file a bug report*

Yes it should be, but it wasn't there so I made the necessary modifications.

Regards,
g-force2k2

[Xyphen]

There is a easier way to do this if you only want to switch between postbit_legacy and postbit templates in vBulletin 3. I'm using it without any file modifications or any extra queries.

But this is nice for having multiple style postbits Good Job G-force.

[g-force2k2]

Originally Posted by Xyphen

There is a easier way to do this if you only want to switch between postbit_legacy and postbit templates in vBulletin 3. I'm using it without any file modifications or any extra queries.

But this is nice for having multiple style postbits Good Job G-force.

Are you sure? Because I know that the vbdevs did not cache the postbit_legacy, so by just using the template it requires extra queries if you did not make any file modifications. Just giving you the heads up, its modification 1 for both the showthread.php and showpost.php.

Cheers,
g-force2k2