linux4me

It looks like Blesta's documentation for developing a plugin is thorough. It's tempting to see what I can come up with.

I was just looking for a way to do this as well, but haven't found one. If you've figured out a way to do it, please share. If not, it would be a good Feature Request.

I think this means you need to activate and configure the Support Manager plugin (Settings > Plugins > Available > Support Manager) before doing the import.

I believe the Domain Manager is only available in version 5.1 and up. If you're using 5.04 like I am, you won't have it yet.

Hi Michael, Yes, I did speak to Paul, and he was very helpful. He gave me the option of redoing the import with the Import Manager linked to here or to manually add the domains as a Service. I'm not working with that many clients, so the solution was to: Set up a Package Group called "Domains". Set up Packages for each domain TLD we sell. For each client with a domain, manually add a Service for the domain with "use module" unchecked. Edit the added domain Service (click "Manage"), resetting the renewal date, making sure that "use module" and "prorate" are unchecked

I successfully completed the migration from WHMCS to Blesta 5.0.4, and didn't receive any errors. In WHMCS, all of my clients had at least one domain registered via eNom, billed annually through WHMCS, and renewed at eNom once they paid the renewal fee. In Blesta, I see the transactions for the domain renewals, but otherwise, the domains are missing from the clients' accounts and I see nowhere to manage them. I installed and configured the eNom module, then followed this tutorial to set up my "Domains" package group, packages for each TLD we sell, and an order form. My problem is figuring out how to set up the records (Services?) for the domains for each client so that they will be appropriately charged and the renewals will be sent to the registrar. I found this tutorial, but my Blesta installation doesn't have a "Domains" dropdown in the Navigation Bar, and when I look in Settings -> Company -> Plugins, there is no "Domains Manager" plugin on either the Installed or Available Tabs. How do I get the domains assigned to the correct client accounts and get domain management working in Blesta? TIA

Thanks! I'm working on the migration now.

I'm thinking about migrating from WHMCS on an Interworx server to Blesta. If I have "Force Graceful Restart" set for Apache in Interworx, is it possible to install Blesta on the same server as Interworx and still accept hosting orders/provision accounts without a problem? Will I lose any other functionaility by installing Blesta on the same server as my user accounts?

In v. 3.6.1, the eNom module lists an API key field, which actually should be relabeled to "Password" and changed to a password type input field on the form. The password should be masked on the Installed Modules -> Manage eNom screen. It seems like a really bad idea to have the user's eNom password in the clear like that.

I think you're right about the issue importing. I'm going to delete all the database tables and try installing/migrating again with a clean slate.

It's been a long day, but I don't see how that would work. There are no products listed if I go Settings -> Modules -> Installed Modules -> Universal Module. If I pick a client, then click Add Service, I can add a domain, but it still shows it billing beginning today even if I uncheck eNom.

I migrated my data into a trial version of Blesta using the Import Manager, I have the eNom module installed and configured, I've created a package group called "domains," and I've set up a package for each TLD we need in the domains group. Now I'm trying to figure out from the documentation how to get my clients' domains set up. Most of my clients in WHMCS have at least one domain registered. They didn't make it in the migration as services, so I guess I need to set them up manually; however, I don't see any way to do it and make the next invoice coincide with when the domains are due to renew. How is that done in Blesta?

Good to know, thanks. I really like the way you have things set up.

The part about exporting a theme was clear, but I was thinking that if I were to export/re-import a theme, and you updated the parent theme down the line with some code changes that would affect it's functioning, I'd be using an out-of-date theme. I was thinking I could just use one of the custom themes you have and change the colors to match the Blesta theme to avoid that problem.

Ah! I didn't select a non-default theme, and was trying to find a way to use Blesta Blue theme and change the logo. Thanks.