Random HTML5 Videochat – WordPress Roulette Webcams

PaidVideochat solution now includes Random Videochat mode.

Random Viedeochat is available with a Next button in HTML5 Videochat App interface.

Enables clients to quickly move to a different performer room (without leaving chat interface).
Next room is selected from rooms recently active online, by picking a room user did not enter or entered longest time ago (for rotation).

The Next button can be used to navigate to available free or paid rooms depending on settings. Will not navigate to rooms where performer is in private show. Visitors always get free rooms (because they don’t have a balance for paid shows).

When users enter paid rooms, welcome message will contain details including group cost per minute and grace time. Also a special room icon showing paid mode.
When going to a paid room (if enabled from settings), user is not charged right away as there is a grace time (configurable). If moving to next room or closing chat before grace time ends, no charge occurs. Also paid room welcome message has a special icon showing payment.

Backend settings include selecting next room only from free/paid or online rooms. Clients can try their luck with this random matchmaking roulette feature to quickly browse different performers, without leaving the chat.

See a live demo.

 

Clients and send Tips and request Pay Per Minute Private Shows.

Are you sure you want to do this? Please try again.

Sometimes, WordPress shows an error like:

Are you sure you want to do this?

Please try again.

This if often caused by memory limitations (script runs out of memory due to multiple plugins and complex theme installed on site).

To fix this memory limits need to be increased from the default of 40M. Usually 128M fixes most setups, but 256M can be used if more is required for certain operations.  This can be done from wp-config.php :

define( 'WP_MEMORY_LIMIT', '128M' );

A plugin like WP Config File Editor can be used.

That doesn’t work? Error can also be caused by bad plugin and/or theme code that generates memory usage loops.
Disabling plugins and switching to a standard theme will fix the issue in this case. Then plugins/theme can be reactivated one by one to identify which one/combination is causing the issue.