Author Topic: Daily ticket for visitor  (Read 2694 times)

Offline khcheung

  • Jr. Member
  • **
  • Posts: 4
Daily ticket for visitor
« on: September 17, 2009, 10:42:29 am »
Hi Admin and all forum users,

I bought 9 credits and using unlimited ticket plan now.

However, I can't see any way to make daily visitor ticket to be set up.

Any idea ?

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: Daily ticket for visitor
« Reply #1 on: September 17, 2009, 12:25:22 pm »
Hi

What do you mean by "daily visitor ticket"

Offline khcheung

  • Jr. Member
  • **
  • Posts: 4
Re: Daily ticket for visitor
« Reply #2 on: September 18, 2009, 02:19:53 am »
I would like to limit visitors to use the hotspot by 8.5 hours (office hour) on daily basis.
After 8.5 hours usage, the ticket will be expired.

Normally visitors may not use up 8.5 hours every day. They may continue to use the same ticket on other day. But it is not desirable to me. It is our policy that visitors should use a new ticket for every single day.

Any idea on how to implement on worldspot.net ??

Thanks for your input.

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: Daily ticket for visitor
« Reply #3 on: September 18, 2009, 07:25:56 am »
Simply create an access profile with 8.5h total connection time.
Then create tickets with it.

If you want your tickets to automatically renew everyday, set a renew time to 24h.

Offline khcheung

  • Jr. Member
  • **
  • Posts: 4
Re: Daily ticket for visitor
« Reply #4 on: September 18, 2009, 08:06:17 am »
Hi Admin,

For auto daily renewal, is it simply put 24h in the below box ?

"Expiration time after first connection
Does not depend on connections
(empty for infinite)"

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: Daily ticket for visitor
« Reply #5 on: September 18, 2009, 08:27:38 am »

Time to wait to reset limitations.
After this time, users are able to reconnect
with all limitations reseted.
(empty for never renew)

Offline khcheung

  • Jr. Member
  • **
  • Posts: 4
Re: Daily ticket for visitor
« Reply #6 on: September 18, 2009, 09:08:37 am »
Hi Admin,

Thanks for your prompt reply. How about making the ticket (8.5 hours access) expired per day ?

I tested it out and found that users can use total 8.5 hours ticket across several days.

Any setting to make the ticket only valid for 1 day use ? (1 day per 8.5 hours)

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: Daily ticket for visitor
« Reply #7 on: September 18, 2009, 11:29:45 am »
Yes, it is the total connection time that is reset everyday. This mean the user won't be able to connect more than 8.5h per day.
You can't set an expiration time everyday.
The expiration time is one time only a final expiration.
This means that you can setup for example 8.5h per day during 1 week.

If you want 8.5h valid during one single day, set the expiration time to 1day and total connection time to 8.5h. No need for renew time...

Offline chys

  • Jr. Member
  • **
  • Posts: 1
Re: Daily ticket for visitor
« Reply #8 on: November 04, 2009, 04:22:36 am »
hi, i want to know where is to set total connection time ??
it is same with (Time to wait to reset limitations.
After this time, users are able to reconnect
with all limitations reseted.
(empty for never renew) ) or not ?? If not then where it is, because i have search it in "manage access profile" but i cannot find it. Thx

Offline WorldSpot

  • Administrator
  • Hero Member
  • *****
  • Posts: 1849
Re: Daily ticket for visitor
« Reply #9 on: November 04, 2009, 03:04:17 pm »
hi
Quote
hi, i want to know where is to set total connection time ??
In manage access profile:
Total allowed connection time in second. (the third entry)
Quote
it is same with (Time to wait to reset limitations.
After this time, users are able to reconnect
with all limitations reseted.
(empty for never renew) )
No it is not. This is why there are 2 distinct entries.
This one resets the total connection time and volume.

This should be explained in the documentation