galaxy

So that is the "old" way. As of 5.1 there is now Domain Manager. Don't even bother importing packages via the module. You don't use the old packages anymore. Just install the module and use Domain Manager. In Domain Manager, which is Packages -> Domain Options. You can "Import Packages" on that tab, but note that it makes copies of all the packages you made that will work with Domain Manager so that you'll have both packages it appears. This is mainly for existing installations to migrate to Domain Manager. But once you do that you shouldn't use the NameSilo module to manage packages anymore. If you click on Configuration at the left. There you can select "Spotlight TLDs", and select the ones you want.

The Universal Module is exactly what I was looking for. I had selected the "None" module not realizing the Universal one existed and wondered how I can get custom fields. Thanks!

Yes, but the problem is that plugins don't appear to have configurable settings. So the plugin is hard-coded with the parameters of hostname, username, password to contact the master PDNS server. But it works well and is configured to come up on any domain registration services. I have a cron ob on the master pdns server that reads the domains from plesk servers and the current billing system (OBAS) and is a slave/secondary for control panel servers, primary/master for OBAS and anything else. But the plugin allows you to change all that (for admins), and clients either get readonly (for slaves), or read-write for primary domains.

That looks like its would be easy to add a tab view & function for admins to create those records. When I get there, I'll write one and let you know if you're interested. I'm finally starting my migration, but needed to wait on DomainManager and wrote a registrar module for SRSPlus/Register.com and a plugin for PowerDNS. I'm finishing up my import_manager to migrate from Odin Business Automation and I'll be set. Then I'll hack the module to add the ability to create the records. It would be nice if they had the button just go in and download all existing orders and set it up.

Sounds like a feature request. I'm not sure where it goes, either Blesta or TheSSLStore directly. I like it and that would be a great benefit.

Good idea, I'll give that a shot. I know that thesslstore wrote the module themselves, so it would be up to them to add the extra features. The existing import would be a great feature, but now that certificates need to be recreated annually, not as much a big deal.

I would like to create a package for services that require a username & password. For example, a mailbox. What is the correct method to create service fields to hold things like email_address, username, password, etc. ? Would that be configurable options? I want to make sure its not an "option" but something that is required, and be able to do validation on it.

Being that you're evaluating that, do you know how to import say 4 or 5 of their products? Or do you have to import hundreds and weed them out?

I do see this module in GitHub and it doesn't use the updated API. The module needs to extend the RegistrarModule class and not just Module. You'll probably need to contact the author if you're not a programmer. https://github.com/hexonet/blesta-ispapi-registrar

Is it possible to use thesslstore module to import just 5 of the packages? Or do you have to install all of them and just pick the ones you want to use? There's way too many and I'd rather not create a hundred packages that will never be used.

In case anyone else runs into this, I figured I'd post the solution. There's a setting in currencies: Use Package Pricing for New Services Only that needs to be unchecked. There's also an issue with the admin interface and safari that doesn't show the currency checkbox(es) on the order form so no currency can be selected. So you cannot choose any currency on the order form while using safari. You need to use chrome or firefox as an administrator. There's an issue with CSS handling with safari.

I'm at a loss here... I've been digging through the documentation for days and days... Is there some logic with the domain terms related to the plesk terms? What can make the domain terms not populate? Actually, this used to work in version 5.0.2 when I tested it, but I'm now working with 5.0.4 and I wondering if that may have something to do with it. I see name silo patches going into 5.0.5.

I'm using NameSilo and Plesk. I've created 2 order forms, one domain only, and another domain and other. The domain only form works fine. The domain and other form allows you to check availability, returns the list/table, but doesn't fill in the "Term" field and returns to start if you submit it. Is there something special you need to get it to fill in the order form? What am I missing? The domains have annual terms, the plesk has an annual term too. But I would like to be able to do domains by year(s), and hosting by months or years.

I have an Order Form for purchasing domains. The form worked fine until I add a Plugin to the packages (one per TLD) to enable DNS zone management. Now the plugin works, but the order form doesn't. The TLD's are removed from the form, and anything you try give the error "That domain name is not supported". Even if I remove the plugin from the package, the order form doesn't work. I need to go to the registrar module and re-create the packages (essentially just save packages), then the order form works again, but the plugin is removed. How can I have both domain registration packages and have a DNS plugin enabled?

I'd like to make sure what I'm doing is supported. I would like to do a phased migration to a new domain registrar. So I wrote a plugin for SRSPlus/Register.com that works, does registrations, renewals, transfers, etc. I would like to be able to migrate one or more TLD from that to a new registrar. This should not affect any current services. I would create new packages and order form(s) for the new registrar and disable the old order forms and enable the new ones. This would change so new registrations and transfers to use the new registrar, however current services should continue to renew with the old one. As needed I can then do domain transfers to the new registrar. So there would be multiple registrars for the same TLD, but depending on the order form used to determine which registrar is used. Will this work (as it currently does with my current billing system), or is this a problem for Blesta?

I did do the transfer, with a successful response, however it is set to pending in Blesta. So you're saying it should be active after a transfer initiated request? I checked the logs in the module (from processResponse()) and see the successful initiation. I also see in the cron logs that: The pending service #2 from client #5500 could not be made active. Where can I look to see why it could not be made active. This is where I assumed the cron job would go in, see if it succeeded or failed and set it to active or failed. I just don't see how/where to do so. But if its supposed to set it active before the cron jobs run, where would I find the reason?

I found that after you initiate a transfer that if you go in as admin, click on pending services and open it I see under "Basic Options" an Activate button. I see that when I click it, it tries to initiate the transfer again, which generates an error from the registrar. So I'm trying to find out how the service is supposed to poll the registrar and activate the service once the transfer is complete. Also what is that Activate button in the UI supposed to do?

I'm almost done the the registrar module, but one thing I don't see/understand yet. When you initiate a transfer of a domain, the service is initially set to "pending". Per the registrar I'm to poll them to check the status to find if/when it succeeded or failed. I've created a module cron job and can poll them for the update and either mark it failed or activate the service. I don't see how to activate the service or mark it as failed. I looked at other domain modules like enom and namesilo but don't see how they're doing it either. I don't see any cron job. Am I doing this wrong since neither of those modules do any polling? What is the correct way to implement this within the blesta framework?

You will need to install a domain registrar module for the reseller account you have and it will fetch and build the grid for you.

That's correct, domains are in years. I'm in settings: Invoice and Charge Options and trying to set the "Invoice Days Before Renewal" drop-down. The drop-down goes from same day to 60 days. So did you mean change "date renews" in the database? That just occurred to me that's probably what you meant... or is there a place in the GUI where I can adjust the renewal date?

It looks like the largest # of days is 60, but its a year registration. How do I change that to 364 ? 60 just isn't enough to force a domain renewal... I like the idea of the "add years", assuming it creates a renewal invoice based on quantity of packages added (i.e. 3 years at the 1 year pkg price). It would also be nice to allow package upgrade/downgrade so they can go from a 1yr to a 5yr at the next renewal time. Those are both on my current billing system that clients use.

I need to test a domain registration module "renew" functionality. How can I force Blesta to renew a domain? I'm OK with hacking the database to make it happen as I know its not yet supported from the GUI (which should be a priority anyway).

So one of my developers reset the database (so he could continue working, I get it), so I won't be able to get screenshots. The steps involved were: - add namesilo regular account - create packages - create order form - add namesilo sandbox account (note that it has the same username, different key) - try to delete regular account (can't, need to delete packages) - delete packages - now delete regular account - try to add packages for sandbox, nothing there So that was the use-case anyway. I'm assuming it has something to do with both accounts having the same username possibly stepping on each other.

I've contacted NameSilo and have both a production and sandbox API credentials. The production API key works fine, populates the available TLD's and I can create packages. With the Sandbox API key no packages are found or loaded. So there is no way to test. (I just read the "read first" and will get some screen shots, etc.)

I'm trying to test the flow of a service lifetime. I created a client, ordered service. Approved the service. Paid by check. I'm waiting for the service to be provisioned. Currently the service is "pending". I have the cron job running. What is supposed to happen next? The only option I have is to schedule termination.