Jump to content

linux4me

Members
 View Profile  See their activity

  • Posts

    17

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Posts posted by linux4me

  5. Migration from WHMCS 8.x, How to Set Up Domains

    in Support

    Posted

    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:

    1. Set up a Package Group called "Domains".
    2. Set up Packages for each domain TLD we sell.
    3. For each client with a domain, manually add a Service for the domain with "use module" unchecked.
    4. Edit the added domain Service (click "Manage"), resetting the renewal date, making sure that "use module" and "prorate" are unchecked

  6. Migration from WHMCS 8.x, How to Set Up Domains

    in Support

    Posted

    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

  8. Blesta on the Same Server as Interworx

    in Pre-Sales Questions

    Posted

    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?

  12. Migration From WHMCS and Setting Up Domains In eNom Module

    in Pre-Sales Questions

    Posted

    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?

  13. Replace the Blesta Logo with Company Logo On Client Area Pages?

    in Pre-Sales Questions

    Posted

    22 minutes ago, Paul said:

    Themes are different than templates, so you wouldn't be missing any content/code by using an exported theme. We do sometimes add options to themes, like we have done in the upcoming v4.0. v4 has a new theme called FOUR, for both the client and admin interfaces, but it won't overwrite any existing themes and all themes use the same templates, they mainly just specify colors.

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

  14. Replace the Blesta Logo with Company Logo On Client Area Pages?

    in Pre-Sales Questions

    Posted

    39 minutes ago, Paul said:

    There is an "Export" option, you can export the theme to a file, re-import it with a different name and then edit it to add your logo. We could probably make that more clear. :blesta: 

    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.

  17. Methods To Convert Whmcs Knowledgebase Articles?

    in Support

    Posted

    I realize this is an old post, but in case you can still use it to add to the importer, the database structure for the knowledgebase in v. 6.x of WHMCS is: 

    --
-- Table structure for table `tblknowledgebase`
--

CREATE TABLE IF NOT EXISTS `tblknowledgebase` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `title` text NOT NULL,
  `article` text NOT NULL,
  `views` int(10) NOT NULL DEFAULT '0',
  `useful` int(10) NOT NULL DEFAULT '0',
  `votes` int(10) NOT NULL DEFAULT '0',
  `private` text NOT NULL,
  `order` int(3) NOT NULL,
  `parentid` int(10) NOT NULL,
  `language` text NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblknowledgebasecats`
--

CREATE TABLE IF NOT EXISTS `tblknowledgebasecats` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `parentid` int(10) NOT NULL DEFAULT '0',
  `name` text NOT NULL,
  `description` text NOT NULL,
  `hidden` text NOT NULL,
  `catid` int(10) NOT NULL,
  `language` text NOT NULL,
  PRIMARY KEY (`id`),
  KEY `parentid` (`parentid`),
  KEY `name` (`name`(64))
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 ;

-- --------------------------------------------------------

--
-- Table structure for table `tblknowledgebaselinks`
--

CREATE TABLE IF NOT EXISTS `tblknowledgebaselinks` (
  `categoryid` int(10) NOT NULL,
  `articleid` int(10) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

-- --------------------------------------------------------

--
-- Table structure for table `tblknowledgebasetags`
--

CREATE TABLE IF NOT EXISTS `tblknowledgebasetags` (
  `id` int(10) NOT NULL AUTO_INCREMENT,
  `articleid` int(10) NOT NULL,
  `tag` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 ;

     

×
×
  • Create New...