Status
Not open for further replies.
That cannot be done, the vB3/vB4 version of InfoPanels is designed to only run on the Forum Home page.

The vB5 version works differently and can be deployed anywhere on any page, but that's due to the design of vBulletin 5 and cannot be easily replicated on vB4 without a performance hit.
 
That cannot be done, the vB3/vB4 version of InfoPanels is designed to only run on the Forum Home page.

The vB5 version works differently and can be deployed anywhere on any page, but that's due to the design of vBulletin 5 and cannot be easily replicated on vB4 without a performance hit.
I see ="(
I won't upgrade to vb5 until one year of being gold ="(
\\\\\\\\\\\\\\\\\\\\\\

Okay other thing, how can I make only two columns on "Top X Stats" panel =")?
 
That also cannot be done, it's been explicitly designed with 3 columns in mind.

We've talked internally about a future version of InfoPanels that features a more modular-friendly design, but there's no firm plans at this point in time.
 
That also cannot be done, it's been explicitly designed with 3 columns in mind.

We've talked internally about a future version of InfoPanels that features a more modular-friendly design, but there's no firm plans at this point in time.
I see, but I just did it by editing two templates, so does this mean putting the "top panel" on usercp will too be just by editing some template and create a hook?
if so, what do you mean by " performance hit" ? =D
 
You would have needed to put the code found in the forumhome_complete hook somewhere in the scope of UserCP too, yeah? Doing the same for the Top X Stats would work, sure.

The calculations ran for the various stats have a hit on performance, but as it stands this only happens if the user is on the forum home. In vB5, we can make the code run on-demand, but we can't do that on vB4 - we have to pre-execute the code to make the HTML available on every page.
This means the code would run on EVERY page, even if you had no intentions of putting InfoPanels there.

That is a performance detriment that we're currently not willing to impose on our users.


This performance hit does not affect your customisations, unless you moved the code to a global hook.
 
Status
Not open for further replies.

Similar threads

Legacy InfoPanels

vBulletin 3.8.x vBulletin 4.x.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
873
Customer rating
0.00 star(s) 0 ratings
Back
Top