End-User Options - Default Postbit Selectable By Members

Please click Mark as Installed if you are using this hack.


What Does This Hack Do?[hr]hr[/hr]
This is an update to my 3.7.x version of this hack.

This is a hack that lets your members select the type of postbit they want displayed for themselves, just like here at vBulletin.org.

vBulletin now uses a horizontal postbit as default, but it used to display the postbit vertically in two columns (see screenshots) and some long time members prefer the old school postbit over the new one, and this hack gives them the option. You can leave the forum wide setting as the new postbit, and members can choose themselves if they want this or the old one.

Show single posts are also be affected by this setting.

You can choose to display the member's default postbit in posts or threads.

You do not have to refresh the page if you do a quick reply, as there is now an redirect back to the new post in place. Adding AJAX would require editing of core vBulletin files, so, it will not be done via AJAX to keep this hack file edit free. This can be switched off in the AdminCP.

DEMO: You can see how this works by testing the function out right here at vBulletin.org, all you need to do is tick the Yes, I prefer old-style postbit checkbox in the Thread Display Options of User CP -> Edit Options. Then check a few threads to see what it does.

IMPORTANT NOTE: This hack will only work if you use the horizontal postbit display site-wide.
I have no plans in making it work with the postbit legacy site-wide. I have looked into it, and it would require code changes to vBulletin's core files to make it work.

So, under the Style & Language Settings section of vBulletin Options in the AdminCP:

• Ensure Use Legacy (Vertical) Postbit Template is set to No.

Limitation with this hack[hr]hr[/hr]
People keep asking for usergroup permissions for this hack.

While this would easy to implement, what people fail to realise is that User Profile Fields are not controlled by usergroup permissions at all, and even if usergroup permissions were added to this hack, the User Profile Fields would still be viewable by members even if they do not have permissions to use them.

User Profile Fields are either viewable by all or viewable by none, this is how they were implemented in vBulletin by design, there is no in between with User Profile Fields.

So, I will not be adding usergroup permissions to this hack.


vBulletin Version Compatibility[hr]hr[/hr]
This hack can be used with vBulletin versions 3.6.0 - 3.8.8.

NOTE: I will not be upgrading this hack to vBulletin v4.0.x, as I prefer the legacy postbit in vBulletin v4.0.x and can not be asked to update this hack to give my users a choice (they will just be getting the legacy postbit from now on).


Hack Support/Feature Requests[hr]hr[/hr]
IMPORTANT: This hack is no longer supported.


Install/Uninstall Instructions[hr]hr[/hr]
The Default Postbit Installation Instructions 3.8.002.pdf instructions file is included in attached .zip.


Version History[hr]hr[/hr]
v3.8.002 - Thursday 19th February 2009
-- Changed: Default Postbit (5) plugin
-- Changed: Instructions (now has uninstall instructions)
-- Changed: Screenshoots
-- Added: AdminCP Option to turn on/off re-direct

v3.8.001 - Wednesday 7th January 2009
-- Added: Default Postbit (5) plugin, to re-direct for Quick Reply when user has Legacy Postbit selected
-- Initial vBulletin v3.8.x Release


Show Your Appreciation [hr]hr[/hr]
Although not required, if you have enjoyed the benefits of this hack, and would like show your appreciation for my efforts, then please feel free to click on the Support Developer link and donate any amount you feel is appropriate.

[EagleNick]

Thanks for the update.

Upgrading to this version has caused an issue; when posting using the Quick Reply, it seems that it cannot use AJAX and therefore the standard redirection page (Thank you for posting! You will now be taken to your post. If you opted to post a poll, you will now be allowed to do so.) comes into play.

When I disable this product, this issue goes away.

So obviously, your product seems to be at fault.

I really hope it can be fixed

[Vaupell]

Excelent installed. / uninstalled didnt work for me
great idea though

[jboyd]

yes i am also having issue with this working with the cheif first post hack. when i want a poll thread i have to edit the thread to add a poll.

Nice idea and i wish it could work for me but
INstalled and uninstalled

[Mosh]

Originally Posted by EagleNick

Thanks for the update.

Upgrading to this version has caused an issue; when posting using the Quick Reply, it seems that it cannot use AJAX and therefore the standard redirection page (Thank you for posting! You will now be taken to your post. If you opted to post a poll, you will now be allowed to do so.) comes into play.

When I disable this product, this issue goes away.

So obviously, your product seems to be at fault.

I really hope it can be fixed

It is not a fault, it is designed that way, the re-direct is there due to the fact that if you have the legacy postbit selected, then a quick reply would show as the new postbit (as updated via ajax) and the rest of the posts would be in legacy postbit.

To change it back to the legacy postbit would require one of the following:

1. A manual page refresh (ie browser refresh at users end)
2. File edits to refresh the page via ajax (I am not up on ajax, so, at the moment, this is not a possibility)
3. Automatic page refresh (ie a redirect)

I selected the lesser of evils and used a re-direct, and it only does it when the user chooses to use the legacy postbit and answering via quick reply.

When I eventually get around to learning ajax, I should be change this to a file edit instead and get rid of the redirect. There is no time-frame for when this will happen.

[EagleNick]

Originally Posted by Mosh

It is not a fault, it is designed that way, the re-direct is there due to the fact that if you have the legacy postbit selected, then a quick reply would show as the new postbit (as updated via ajax) and the rest of the posts would be in legacy postbit.

To change it back to the legacy postbit would require one of the following:

1. A manual page refresh (ie browser refresh at users end)
2. File edits to refresh the page via ajax (I am not up on ajax, so, at the moment, this is not a possibility)
3. Automatic page refresh (ie a redirect)

I selected the lesser of evils and used a re-direct, and it only does it when the user chooses to use the legacy postbit and answering via quick reply.

When I eventually get around to learning ajax, I should be change this to a file edit instead and get rid of the redirect. There is no time-frame for when this will happen.

Well this didn't used to happen before I upgraded, and I was perfectly fine with the quick reply being the odd-one out and using the horizontal postbit (until the browser was refreshed).

Is there any way I could modify the code to disable the behavior and revert it to it's old way?

Thanks.

[Mosh]

Originally Posted by EagleNick

Well this didn't used to happen before I upgraded, and I was perfectly fine with the quick reply being the odd-one out and using the horizontal postbit (until the browser was refreshed).

I added that in this version, the v3.7.x version did not have it.

Originally Posted by EagleNick

Is there any way I could modify the code to disable the behavior and revert it to it's old way?

Thanks.

It should not be too much of a drama, so I will release an update in the next day or so

[Mosh]

Update: v3.8.002 - Thursday 19th February 2009
-- Changed: Default Postbit (5) plugin
-- Changed: Instructions (now has uninstall instructions)
-- Changed: Screenshoots
-- Added: AdminCP Option to turn on/off re-direct

[EagleNick]

Originally Posted by Mosh

Update: v3.8.002 - Thursday 19th February 2009
-- Changed: Default Postbit (5) plugin
-- Changed: Instructions (now has uninstall instructions)
-- Changed: Screenshoots
-- Added: AdminCP Option to turn on/off re-direct

Thanks, you're awesome!

[newmasalaboard]

Thanks for the Update !!

The postbit looks awesome now

"Marked as Installed"