Jump to content

Cody

Blesta Developers
  • Posts

    1,574
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by Cody

  1. Version 3.2.0-b3 is now available. You can download it in the Client Area.

    This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.2 beta bug forum.

    PHP 5.5 Users

    Included in this release is a /hotfix-php5.5/ directory. Please use this directory to overwrite the default /blesta/app/app_controller.php, /blesta/app/app_model.php, and /blesta/app/models/license.php files.
    Please let us know how this hotfix works for you.

    Installing Blesta

    See Installing Blesta in the User Manual for instructions.

    Upgrading Blesta

    See Upgrading Blesta in the User Manual for instructions.

    Release Notes

    See Blesta Core - Version 3.2.0-b3.

    For older releases see all Change Logs.

  2. You may submit any contributions you'd like to us, and if we find it useful may include it in future releases. But it would be a violation of our License Agreement to modify our intellectual property and sell it (even to us).

     

    Of course, if you create an extension that doesn't use our intellectual property you are free to sell and distribute it however you want (we may even be interested in purchasing it).

     

    We provide dozens of extensions with Blesta for free in the hopes that third party developers will do the same, but we are not against anyone charging for their hard-earned work provided it doesn't use our intellectual property.

  3. Good points, electric. You've highlighted exactly why we've designed Blesta to be so modular and customizable.

    Of course, I'm always surprised when people say Blesta is basic or simple, or otherwise lacking in features when compared to some other systems. It makes me smile, knowing we did a good job with not overwhelming the user. But it also means we may not be conveying all of the features of Blesta to users that are used to systems that have cut corners.

    Take for example service terms. Most systems support one time, monthly, bimonthly, annually, and biannually. Blesta supports hundreds of thousands of possible terms!

    Other systems supporting only email delivery of invoices. Blesta supports email, fax, and postal mail (yes, invoices that actually fit into double-windowed envelopes and can be printed through Blesta or mailed directly from Blesta)

    Other systems have a basic API that was added as an after thought. Blesta's API automatically grows with every release, and with every plugin installed.

    Multi-company,... the list goes on.

    While I can definitely see how someone used to another system might notice some things currently unavailable, the net result is Blesta is more featureful overall; and growing daily.

  4. Version 3.2.0-b2 is now available. You can download it in the Client Area.

    This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.2 beta bug forum.

     

    PHP 5.5 Users

     

    Included in this release is a /hotfix-php5.5/ directory. Please use this directory to overwrite the default /blesta/app/app_controller.php, /blesta/app/app_model.php, and /blesta/app/models/license.php files.

    Please let us know how this hotfix works for you.

    Installing Blesta

    See Installing Blesta in the User Manual for instructions.

    Upgrading Blesta

    See Upgrading Blesta in the User Manual for instructions.

    Release Notes

    See Blesta Core - Version 3.2.0-b2.

    For older releases see all Change Logs.

  5. 5.3.6

     

    I just wanted to note -- It's a bit rough when a company wants to make the jump to using Blesta when it completely folds importing the old information in its' entirety. I understand that it's a bit hard to transpose information and it does take time to get it working to its' full extent, but It's definitely something that would hold me back from making the jump from WHMCS to Blesta.

     

    In its entirety huh? We must have a different understanding of the definition of entirety. :D

     

    At any rate, considering the importer was designed for WHMCS version 5.2, I don't think it's such a surprise. They have been known to make superfluous changes in the past simply to negate our import scripts, that could very well be the case here.

  6. a just see this topic, is the licence module has it own php class to integrate with our scripts/modules ? or we need to write our own way to check the licence ?

    Yes, the license manager comes with a class and associated libraries that handles all integration. It also includes example code to show how to embed within your software.

  7. Question for stuff , is the routes system can be overrided by other class ? if yes , the door is open to use plugins to ovveride the routes/urls without changing the core files .

     

    No, because the route must be processed before any other code is executed. You could, of course, use a plugin to modify /config/routes.php when installed, though probably best to just give user instructions to do so.

  8. I'm just wondering how to get that info to show up.  I have domains registered at resell.biz already, then I imported from WHMCS and the tabs are empty.  My guess was that the cron job had to run to update but I was wrong about that.  Will only newly registered domains show that info now (ones newly registered or transferred after I start using Blesta)?

     

    If you're not seeing anything in the tabs Blesta isn't able to fetch the info from LogicBoxes. Check your module log.

  9. I am in the process of validating my migration from freeside to blesta.

     

    I've inserted credits into the transactions table and a related row in transaction_applied.

     

    When cron runs the apply routine it is applying those transactions again.

     

    How can I indicate to blesta that the transaction has already been applied?

     

    How do the records you inserted differ from those that Blesta inserted for the same transaction?

     

    Blesta will take the transactions.amount value for a particular transaction and apply transactions.amount-transaction_applied.amount (for a particular transaction) to invoices until transactions.amount-transaction_applied.amount is 0.

     

    If Blesta is indeed applying transactions that have already been applied, my guess is it's because from what Blesta can tell there are still amounts left to be applied.

  10. How do I do that?  I thought that having my module setup with my account and running cron job would do that.

     

    You don't have to do anything. The whois information comes straight from the registrar. If you update it in Blesta for the service then it will be reflected at the registrar.

    Not sure what you're expecting the cron job to do here...

×
×
  • Create New...