They will rotate randomly and they do ;)

You may check this if you disable the ones you have already seen. If they don't show you probably haven't setup the right rule.

You may need to use refresh on yourself, but on a life site the banners rotate very well and almost evenly.

It was answered in the way that each single location can be reused for N banners and rarely you would find enough occasions to use all 10 banner locations together ;)

Yeah, I understand that for 99% of sites out there. I'm putting together a site where I need many more. Would adding more locations be hard to incorporate?

Pretty much ... it will need several additions in many places and in the end it will slow down the process of parsing the banners into the pages.

You are free to do these changes for your own ... I don't like to sound cynical but 10 locations are really enough if you use them together with all other imaginable filters (usergroups, sections, date/time) :) I agree with you, if you skip these settings and make it a location based setup. But you can reuse one location, for example, to show in each of your forum sections a different and dedicated banner set. Most banner software is location based, and this means you have to create for each banner a location. Here, you can use one location for many different banners and the scope can be different.

Thanks for your reply. If it requires that many changes to the code, then I won't worry about it. The reason I need so many is I planned to use this mod for an additional use alongside advertizing while using custom placement via the code tag.

Maybe creating additional locations can be an additional future in the future? :)

I see that you would need at most 2 locations. 1 location for the site advertising and another for the code tag. Since you can define a different banner for each forum section and still use the same location (tag code), each code tag would require just as many banners of that section in the database as you probably may show on a single page. Say you have 10 posts and 5 code tags per page, you may use location 0 five times on the same page and setup 5 different (or same) banners for that forum section, and you are done. If you need the same scheme on another section but different banners, you just filter that section with another 5 banners. And in the same time you have still 9 locations to fit your site advertising much the same way :)

Ohhh, that makes sense, I didn't know you could use the same code tag with the same ID multiple times on the same page. In that case, 9 locations should be plenty! Thanks for your help on this one

Hi Giovanni,

I am trying to have my banners (for guests only) between the first and second post of my threads. However it is not showing the banners at all

Here is the code I am using on postbit_legacy:

I have the same custom code/ placeholder (#reklama:2#) working just fine in navbar template, but it is showing blank in postbit_legacy.

Any hints how to make this work ?

Thanks for your time.

Maybe:

($post[postcount] % $vboptions[maxposts]) == 1

makes the difference? I believe without extra parentesis it operates as if:

$post[postcount] % ($vboptions[maxposts] == 1)

The expression may fail due to a division by 0 and thus never execute ...

The conditional statement which I posted works in every other case. It is working for rotating banners through a simpler mt_rand () plugin. Though I like your solution better, due to tracking capabilities and better banners management.

Here's a sample link with banner (through mt_rand() plugin) between first and second post.

http://www.insurance-forums.net/foru...-t30355-3.html

Note the banner, on navbar is produced by your product but the one between first and second posts is the other plugin. If you have time to check, in that link, I left the placeholder between the banner and the Quick Register form. You will notice it is returning a blank.


I may be wrong so please correct if I am doing so, but my assumption is that the limitation that it should only be run on global_complete hook is maybe causing to stop displaying in postbit_legacy.


Thanks,
Val.