Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 03/23/2017 in all areas

  1. Welcome! There's not a cPanel account importer unfortunately, it's something that I'd love to build at some point. You can add existing cPanel accounts to Blesta manually by doing the following: On a client profile page, click "Create Service" Select your cPanel Package and uncheck the "Use Module" option. You probably want to select NOT to invoice as well. Once it's added, go back and click the Manage link, enter the cPanel domain name (uncheck "Use Module" again). You may also need to set the next renew date under Manage with the "Change Renew Date" option Then, just repeat for each one. So, it's some work if you have a lot of accounts, but you could move people gradually as there is time.
    2 points
  2. Paul

    Theme cannot set all colors

    For everyone else who might stumble on this thread. We recommend creating an overrides css file, call it something like overrides.css and load it in /app/views/client/bootstrap/structure.pdt after all the other styles. Then, add the style you want to overwrite, like the one above, changing the colors or other attributes.
    1 point
  3. Thanks, Paul. Yes, I could see this being a useful one for sure! This looks great. We're hoping to look at the possibility of developing some modules as well. First thing we have to tackle is some code modifications to enable the ability to exempt one, the other, or both taxes on invoices and by user. That's a deal breaking requirement for some of the Canadian provinces in handling sales taxes. Cheers!
    1 point
  4. Paul

    Upgrade from 3.4 to 4.0

    There are some files you may wish to delete after you perform the upgrade. See https://docs.blesta.com/display/user/Upgrading+Blesta (Click the link in the yellow box)
    1 point
  5. So, here is what I think happened..... Since the upgrade I've been having to run crons manually in Blesta. The mail was working great, but no automation. Today I learned that I need to add ionCube to /etc/php/7.0/cli/conf.d to get the automation to work. Anyone interested, can relive those moments here.... So after that automation started working, but it couldn't complete the mail task... so it was hung. The solution to fix the mail task was to to copy mailparse.ini into /etc/php/7.0/clic/conf.d that same way I had done above. /etc/php/7.0/cli/conf.d# cp ../../cli/conf.d/20-mailparse.ini . That fixed the broken task, but as you said, I still need to add an end time to the open process in log_cron. What a day.....
    1 point
  6. I don't know what "$this->parent" is. You can use "$this->requireLogin()" You should be extending your plugin's parent controller that extends AppController and implements the preAction method. The dispatcher throws an exception when attempting to load controllers that do not implement the preAction.
    1 point
  7. Paul

    Module gogetssl

    Looks like it sent the authentication information but received no reply from GoGetSSL.
    1 point
  8. Alright, I don't normally do this but I'm going to close this thread. No offence to the @jassdesi, and I hope my response was informative. I hope everyone has a good week.
    1 point
  9. We're about to start development on the new Domain Manager system. To be perfectly honest, v4 took way longer than we expected. It was much more involved than we thought it would be, and it pushed off domains. We're taking a hard look right now at all of the discussions about domains, and it looks like we're going to stick with the KISS principle. (Keep It Simple Stupid). Even so, improving domain support is a big deal and we're not going to let it prevent us from coming out with other releases while we work on it. It's likely that the domain system will be implemented almost entirely as a plugin, though there are some core changes that are necessary like packages being able to defer their pricing to plugins. Aside from any core dependencies, the domain plugin may be able to be released as a beta on its own where we look forward to getting more feedback from the community. Since there are also other important things that need to be done as well, we are going to work on those things simultaneously and reduce the time to release. Domains will be included when it is ready, but we aren't going to hold back releases as a result. I hope that makes sense, and I understand how frustrating it is not to already have better support for domains. Just know that we're working on it, alongside other things, and will release it to the community when we have something ready to test.
    1 point
  10. That's a big task and won't be done until the domain manager you can blame people like the above moaning
    1 point
×
×
  • Create New...