.................................................. .................................................. .......................
Hello friend!
Did you build this script?
Why don't you post the source code without selling it?
I'm asking you in a friendly way!
I can offer my site xcamadult.com archive for FREE to anyone who wants to have a site like mine.
My site accepts Chaturbate white label!
The archive can be downloaded from HERE

Because of the way the script works anyone can download the source code very easily - I have already addressed that in another thread.....

The reason it's worth paying for, aside from the quality is having access to updates and maybe some input into it's ongoing improvements.

The latest version at https://yourhotsite.com/ looks amazing !!! :thumbsup:thumbsup:thumbsup

I set it up yesterday, and for a client side script it's amazing. I went and disabled the Safari detection because you don't need it if your white label is on the same domain.

The big problem that needs to be resolved is rooms past the first 90 or so not showing.

Thanks for the feedback!..

I was in two minds what to do with the 90 rooms only issue - I decided to be an optimist and hope CB fixes it - It would help if you and anyone else emailed support about the issue.....

Thanks again...

I am certain these performers are online. I have Mechbunny sites that will show hundreds of rooms.

Whether or not the problem can be fixed client side I couldn't say.

CB will not fix it.. its on your end.
Limit and Offset params are your friend.

It is a CB issue they don't show the iframes for models above the 90 limit - I will try to limit it to 90 and use the offset and see if that works - Thanks for the help...

Unless you are showing 90 per page.... you should not be pulling 90 cams.

if you want 500 rooms... Lets make the math easy cause im a math retard.

So you want 500 rooms... you have 50 per page.
Your home page pull should be limit 50, offset 0

Then you tie your pagination to the room limit.

So page 2 becomes pull Limit 50, offset 50

THe other problem you could be having is you're possibly pulling 500 and storing to database without respecting geo restrictions, which would become nearly impossible to diagnose.

as a secondary hint, any attempt to "cache" the API calls, has caused major issues for me...similar to what we see here... check you caching layer if you have one.

God speed man!

Thanks for the input - I am not using pages on the sites - I am using lazy loading and calling 80 at a time and then using offsets and pagination in the api to get the next 80 etc. - That should work but I still get the issue - I will go and sit on the loo for a while and have a good think about it - :1orglaugh...

Thats where I do my best thinking too! :1orglaugh

very cool script I think I need something like this soon