Jump to content

Cody

Blesta Developers
  • Posts

    1,574
  • Joined

  • Last visited

  • Days Won

    74

Posts posted by Cody

  1. Is there a temporary workaround for this?  My business is dead in the water right now :/

     

    Try updating /app/models/clients.php (line 89):

     

                        $this->setCustomField($field->name, $client_id, isset($vars['custom']) && array_key_exists($field->name, $vars['custom']) ? $vars['custom'][$field->name] : null);

     

    to:

     

                        $this->setCustomField($field->id, $client_id, isset($vars['custom']) && array_key_exists($field->name, $vars['custom']) ? $vars['custom'][$field->name] : null);
  2. There are a number of issues with including tax in the unit prices. For example, if you set up 20 packages with 5 price points each and the tax rate changes from 19% to 35% you would have to update 100 different prices just to ensure that you're continuing to pass that extra 16% tax along to the customer instead of paying it yourself!

     

    But if you'd like to be able to enter unit prices that include tax, I encourage you to create a feature request.

     

    Closing as not a bug.

  3. sorry, I do my best, but I don't see it inclusively anywhere.

     

    step by step:

    • I created my tax rule with type "inclusive" (for Germany = "MwSt.", 19%)
    • I opened a client and clicked "create invoice"
    • I entered a description, quantity, unit price - at this step I already can see the subtotal and total.

      for example: quantity "3", unit price "8.00"

      subtotal "24.00", total "24.00" - ok so far

    • Now I click on the tax checkbox - and it changes the following:

      subtotal "24.00", tax "4.56", total "28.56"

    • it goes on with this when saving and creating invoice.

    The meaning of "inclusive" as I understand it would be:

    subtotal "20.16", tax "3.83", total "24.00"

     

    The problem is you're entering your unit price as the price including tax. The amount you enter for the unit price should not include any tax. The tax is calculated and included on the line item in the invoice.

  4. There are a few existing tasks with regard to inclusive tax:

     

    CORE-652 - Order: Need to display service prices with any tax inclusive amounts

    CORE-650 - Tax Rules: Add option to control whether tax amount is displayed as inclusive or exclusive

     

    In come countries (VAT countries in Europe, Australia, and New Zealand) line items include tax however tax rates are still calculated exclusively (like sales tax). Blesta currently handles these just fine. However, in a number of countries (Sweden, for example) line items include tax and tax rates are calculated inclusively.

     

     

    Unfortunately the inclusive tax feature doesn't work. If I set an inclusive tax and add a new invoice, the tax is always added to the price. :-(

     

    Can you provide an example of what you mean? "Inclusive" means tax is included in the price. As with any bug report we need as much information as possible. Please see How to Report a Bug.

  5.  

    Hi guys,

     

    Noticed this on a fresh 3.0.0 installation and only now decided it might be worth mentioning.

    Oh noes!
    
    Call to Model::makeDSN with invalid parameters, required array('driver'=>,'database'=>,'host'=>) on line 226 in /<site_root>/lib/model.php
    This was before I hit the /install process which makes sense as to the reasoning of the issue, it just doesn't look very intuitive when dealing with a product that is "final" (I realise that is vague).
     
    Replicating
    Move your config/blesta.php file out of the way and hit any path (other than /install) in your browser.
     
    I would think that an "Oh noes!" message would be not visible after moving to 3.0.0.
     
    Already fixed for 3.0.1 (CORE-682)
     
     
    Note:
    Just noticed that by default config/core.php still contains

    Configure::set("System.debug", true);
    Should this still be turned on at this point?

     

    Yes. The following in /config/blesta.php controls error reporting (if you upgraded from a beta version you'll need to add this line manually):

     

     

    Configure::errorReporting(0);
  6. Although I would consider it "nice to have" if the user could authenticate with Facebook or LinkedIn, for clients and staff we need an email in the account, so email providers would serve not only as authenticators but also to gather an active and trusted email address and link the account to that, so I would focus on Google, Gmail with > 600 M users and Google Apps with > 5 M companies.

    If you are planning to add it for any OAuth service provider, I would suggest then to have settings to allow or disallow each one from a list of providers supported.

    I would personally leave it only for Google and Hotmail, in that case, maybe Yahoo! when it gets to OAuth 2.0.

     

    In all likelihood it would be completely provider agnostic. You'd simply enter the authentication URL for each of the providers you wish to support, or perhaps check boxes from a set of supported (e.g. tested) ones.

×
×
  • Create New...