AdamDG

I think that using "to" instead of "-" might be slightly clearer, however, for my client base, I think that the most clear and least confusing way to specify the term would be to use "through" and specify the last day of the term as the end date. Ideally, this would be a configurable option, since preferences obviously differ.

Is there a way to define the end date of the service terms to be the last day of the service term, rather than the first day of the next term? Some of our clients find it confusing that invoices show terms of, for example, Jan. 1 - Feb. 1 and Feb. 1 - Mar. 1., rather than Jan. 1 - Jan. 31 and Feb. 1 - Feb. 28. The way that it is now seems to imply that the first day of every month is actually part of 2 terms. This is not a major problem, but does cause some confusion and it would be nice to be able to change it to the format I noted, which is more customary to our clients.

Yes, using the ID Protect feature for a domain is an additional charge. In our case, we register all domains that way be default and consider the cost in the pricing of our domain registration service. It would be optimal, however, to be able to set different pricing based on whether or not the option was selected. It does not appear to be very difficult to control this feature via the enom API. I may modify the module to include this functionality.

The whois tab was not able to load because the enom module code encountered an error when trying to process the "address line 2" field of the whois data for the domain that I was dealing with, which happened to contain no data. The module code expects string data to be returned for every whois field and the script crashes (indirectly, via helpers/html/html.php) if that is not the case. I fixed this by adding if(is_string($value)) at line 1043 of components/modules/enom/enom.php which effectively ignores empty values.

Any updates on this? This seems like an essential function for any sort of hosting management system...

When managing a domain name registration service that was created using the eNom module, nothing happens when I click on the Whois tab. The other three tabs (Basic Options, Name Servers and Settings) all seem to work fine. Any ideas? I need to be able to turn on the eNom ID Protect feature to mask client contact details when registering domain names. Is this supported? I assume that if it is, it would be in the Whois tab that currently does not seem to work. In any case, I would like this to be the default setting when registering new domain names. Is that possible?

Anybody?

Do you have a time estimate on implementation of the feature CORE-1593?

I also have a related, but much more general question about e-mail template tags. We are interested in creating some tags that can be included in any client e-mail template that contain information specific to our application, that would come from our own database queries. How practical is this? What would be the suggested method of implementing this? We are OK with making modifications to the core of our Blesta installation, although we try to limit doing so as much as possible.

Thanks Paul! That will be a big help. For now your suggestion should work just fine.

Maybe it's an "e-cigarette"

Yes, I tried the {% debug %} tag. The output does not appear to contain the action. It does contain the values of the service options fields that I have defined for the product, which is great. I also does not contain the product name, which although not essential, would be convenient. Here's an example of what I see ("****" censoring domain names): Array( [h2o] => H2o_Info Object ( [h2o_safe] => Array ( [0] => filters [1] => extensions [2] => tags ) [name] => H2o Template engine [description] => Django inspired template system [version] => 0.3 ) [base_uri] => ****/ [admin_uri] => ****/admin/ [client_uri] => ****/client/ [email_address] => billme@adamtestcompany.com [emailfilterlevel] => disabled [password] => asdf [_other] => )

That is exactly what I am trying to do. The problem is that when the notification is sent to me, I have no way to know what action is to be taken, because the body of the e-mail is exactly the same regardless of the action being taken.

I am trying to use the Universal Module to facilitate automated billing, including suspension and unsuspension, of services that need to be manually provisioned / maintained. If the system can't tell me what action to take when it notifies me that an action needs to be taken, how would I accomplish this?

We ran into a similar problem where logos were always showing up on our invoices if the invoices were generated "on demand" by clicking on something within Blesta, but they would not show up in automatically generated invoices. The component of Blesta that generates the PDF files appears to be expecting an absolute path to the logo file, however it is only actually receiving a relative path. So, unless the working directory of the cron job is the directory in which the Blesta install resides, the problem will occur. In our hosting environment, the working directory of a cron job is, by default, one level higher than the directory where Blesta (or any other website) would reside. We fixed this by wrapping the cron job in our own shell script that does a cd to the proper working directory just prior to executing the cron job script.