Earlier this month we were working on a problem which never got =
My system is not properly handling the default billing expiration date =
*extensions* or *limit* extensions.
You sent back a listing of the Configuration Table items and values, =
which does not seem to reflect what is actually in the tables.
*I am having customers being cut-off without my knowledge or desire =
because of this problem*
1) The *Limit* feature does not seem to function at all. As I =
understand it, this is a *permanent* period of time which can be added =
to an account to permit continued access after the expiration date.
The Configurations Table listing you sent me indicated that item 5 was a =
Default Limit value in days. My Configurations Table has a value of =
7200 in it. That would equate to 5 days if this value is measured in =
seconds. However, changing it does not change anything in a new test =
MBR. The limit still defaults to 0 days.
Is the value of item 5 in the configurations table the correct one, and =
what are the units (seconds, days, etc.).
What is necessary to make the default limit value be applied to the MBR?
2) The *Default Extend* does not function either. As I understand it, =
this is a default value which will extend access to an account beyond =
expiration date, and that it is refreshed each time an Renewal Invoice =
Your listing of the Configurations Table shows item 9 as the Default =
Extend value. The Emerald Administrator does change this value, but it =
never affects the MBR billing information. When I create a test =
account, and create an invoice, the Extend value still defaults to 0.
What is necessary to get the default *Extend* value to be applied when =
Your previous replies indicated that Emerald version 2.2 may be =
necessary. I never received a reply on how I get version 2.2. I am =
using version 2.1.11.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">