Jump to content

Cody

Blesta Developers
  • Posts

    1,574
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by Cody

  1. Nice. When you guys do that, will you guys be including the functionality to update the databases as mandated by MaxMind? Or is this script the preferred way to do it?

     

    I think that's sort of a gray area, in terms of licensing. We can't distribute MaxMind DB with Blesta, and some users use a shared MaxMind DB. But we'll evaluate when we get there. If nothing else, a plugin could be created to auto update MaxMind DB.

  2. This is a DNS issue. It looks like your webserver is unable to reach your database server. Ensure the hostname is correct (in config/blesta.php). If you're running your database on a non-default port, uncomment the port field (in config/blesta.php) and enter the port for your database server.

  3. I guess you could call it a back door.  Beats having an office full of people constantly having to 2FA (yes it's not as bad as that with "keep me signed in" and stuff but still).

     

    You could just disable 2FA on those accounts. But I could see how you wouldn't want to do that if there's the possibility of logging in remotely (which my proposed white list would solve).

     

    I actually think it would be cool to have a white list per staff group.

  4.  

    Problem: Total tax, is not being saved in database on "invoice_lines" table. The value must be saved because rounding issues, this way we have to alwaes calculate tha VAT that was in that time to try to get the correct VAT/TAX total. For exemple for the Vat MOSS to work I have to make extra calculations to make it right, but there are companies that like to round value in Total of the invoice, and people that like to round in total for each line.

     

    CORE-1742 in 3.5.1

  5.  

    Problem: As I saw in webhosting talk: "the way it handles rounding for the transactions, the system stores the values to 4dp in the db so things like tax rules (as mentioned earlier in thread) and auto foreign exchange rate calculations lead to unexpected results because Blesta does the math to 4dp but Paypal for e.g. only cares about 2dp so the user could pay an invoice and suddenly end up with a 1c credit without knowing what went wrong."

     

     

    CORE-1742 in 3.5.1

  6.  

    Guys if you add routes for the Support Manager how do you make Blesta use them instead of the default ones? Do you need to edit this:

    array(
    				'action' => "nav_primary_client",
    				'uri' => "plugin/support_manager/client_main/",
    				'name' => Language::_("SupportManagerPlugin.nav_primary_client.main", true),
    				'options' => array(
    					'sub' => array(
    						array(
    							'uri' => "plugin/support_manager/client_tickets/",
    							'name' => Language::_("SupportManagerPlugin.nav_primary_client.tickets", true)
    						),
    						array(
    							'uri' => "plugin/support_manager/knowledgebase/",
    							'name' => Language::_("SupportManagerPlugin.nav_primary_client.knowledgebase", true)
    						)
    					)
    				)
    			),
    

    Routes I managed to get working but Blesta doesn't link them on the menus etc...

    Router::route("^support/tickets/(.+)", "/support_manager/client_tickets/$1");
    Router::route("^support/tickets/add/(.+)", "/support_manager/client_tickets/add/$1");
    Router::route("^support/knowledgebase/(.+)", "/support_manager/knowledgebase/$1");
    Router::route("^support/tickets/reply/(.+)", "/support_manager/client_tickets/reply/$1");
    Router::route("^support/tickets/departments/(.+)", "/support_manager/client_tickets/departments/$1");
    

     

    Kinda unrelated to this thread, but the URI in links are set in the view (.pdt) files. Routes simply control what URIs can be used to access a particular application path. So you would need to update the views to contain the format of the route you define.

    You might say, well that kind of suck, and yes, it does. The solution for that would be reverse routing, but the minPHP routing engine doesn't (currently) support it, so Blesta doesn't support it.

  7. Version 3.5.0 is now available. You can download it in the Client Area.

    Installing Blesta

    See Installing Blesta in the User Manual for instructions.

    Upgrading Blesta

    See Upgrading Blesta in the User Manual for instructions.

    Migrating to Blesta

    See Migrating to Blesta in the User Manual for instructions.

    Overview

    • Upgrade/Downgrade Config Options
    • SolusVM Improvements
    • Custom Reports
    • Much more...

    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.

    Release Notes

    See Blesta Core - Version 3.5.0-b1.

    See Blesta Core - Version 3.5.0-b2.

    See Blesta Core - Version 3.5.0-b3.

    See Blesta Core - Version 3.5.0-b4.

    See Blesta Core - Version 3.5.0-b5.

    See Blesta Core - Version 3.5.0.

    For older releases see all Change Logs.

  8. The PHP API is written in a simple way to implement (https://github.com/Yubico/php-yubico). All it needs is a couple of fields added to the admin/user settings, a couple of columns added in the database and then include the API files itself. It's not rocket science to implement so I still don't see what the problem is.

     

    Our position isn't that we don't want to implement Yubikey as a token. In fact, we plan on making some improvements to the authentication system to make it easier to extend (OAuth, LDAP come to mind). But we've got a lot of other things we want to accomplish before we consider this.

  9. Version 3.5.0-b5 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.5 beta bug forum.

    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.5.0-b5.

    For older releases see all Change Logs.

  10. Quickbooks integration is on our "We'd like to do that, but won't happen for a while" list.

     

    Hi Jonathan,

     

    Im currently also getting a quote to build a blesta <> quickbook integration module - we could split the cost if you are interested. 

     

    QuickBooks Plugin For Blesta

     

     

     

    ·      Invoices

    1.     Create Invoice (Invoices created in Blesta gets imported to QuickBooks)

    2.     Update Invoice (Any change made on the invoice would reflect to QuickBooks's Invoice)

    3.     Void/cancel invoice

     

    ·      Payment

    1.     Create Payment (transactions added in Blesta gets added to QuickBooks and get applied to an invoice if any)

    2.     Update

    3.     Refunded/Declined

     

    ·      Client/Customer

    1.     Create Customer (On Invoice importing first the plugin will check if the customer info is already recorded in QuickBooks, otherwise, it gets recorded)

     

     

    Project Turnaround time: 14 business days

    Total Cost: $275 USD

     

    If you can get it done for $275 I'd say go for it. It would cost us more than that just to plan the plugin.

     

    One thing you might want to consider with respect to accounting is the fact that an online payment (such as credit card) is not considered income until it has been deposited into your bank. So to automate your accounting, you need the ability to reconcile payments before you add them to Quickbooks.

  11. Version 3.5.0-b4 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.5 beta bug forum.

    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.5.0-b4.

    For older releases see all Change Logs.

  12. Version 3.5.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.5 beta bug forum.

    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.5.0-b3.

    For older releases see all Change Logs.

×
×
  • Create New...