Jump to content

danmo

Members
  • Posts

    10
  • Joined

  • Last visited

Reputation Activity

  1. Like
    danmo reacted to velaware in Python Blesta Api   
    I made a thread on this elsewhere but since I did a bit of a major overhaul, enough to warrant basically a 2.0 of it.
     
    This differs in very, very big ways.  The biggest is that this supports ORM now.
     
    Instead of manually calling APIs via doing this:
    from blesta_api import * api = BlestaAPI(...) api.get("ApiKeys", "getList") You can do it this way:
    from blesta_api import * api = BlestaAPI(...) # Get list of API keys api.models.ApiKeys.getList() # Use my API Helper's test module api.plugins.apihelper.test(str="Returning this string") This makes the code easier and more pleasant to read.
     
    It should be noted that both methods are supported, and for ORM to work the API Helper plugin needs to be installed.  Otherwise this won't work (Blesta doesn't offer a native way to get all available API calls).
     
    All api.models calls are found in /blesta/app/models while api.plugins reads all plugins that have a public model in the /blesta/plugins directory.
     
    Source: https://github.com/anzenehansen/Blesta-Goodies/blob/master/api/blesta_api.py
    API Helper tarball: https://github.com/anzenehansen/Blesta-Goodies/raw/master/apihelper_plugin.tar.gz
     
    INSTALL
    Use as you would any other Python script.  The only thing you have to actually import is BlestaAPI, so from blesta_api import BlestaAPI is fine too.
     
    TODO
    Create a way to determine HTTP method for each API call (currently only GET is supported) CHANGE LOG
    v2.0.0 - 01/28/2014
    Initial release
  2. Like
    danmo got a reaction from Michael in Blesta Api Python Version   
    Nice work! Just to anyone looking to implement this, it looks like it needs the associated Blesta plugin installed to work.
     
    Of course I discovered your work too late, after developing my own wrapper for python. It's pretty basic but also quite battle tested. You can feed in array args as a standard python dictionary and it outputs to the API in a format Blesta likes,
     
    e.g.
    {"vars": {"type": "cc", "account_id": "48"}, "client_id": 1} becomes [('vars[type]', 'cc'), ('client_id', 1), ('vars[account_id]', u'48')] It does have one external dependency though (the wonderful requests module).
  3. Like
    danmo reacted to Darin in Option To Display Phone Number On Invoice   
    For now, I've added the phone number as an additional line on my address in the company settings. Works great for my purposes.
  4. Like
    danmo got a reaction from Blesta Addons in Option To Display Phone Number On Invoice   
    One of our more old-school clients wanted to urgently contact us this morning, and was frustrated to find our phone number was not included on our invoices. I admit I was a little surprised to confirm this.
     
    I found that under Settings > Company > Billing/Payment > Invoice Customisation, it's possible to enable Logo, Name/Address, or PAID Watermark on the invoice. Would it be difficult to add Phone Number to this list?
     
    Thanks!
  5. Like
    danmo got a reaction from iNode Cloud in Synergy Wholesale Domain/ssl Module   
    How did you go with this?
     
    I for one would be willing to chip in to support development of this plugin!
  6. Like
    danmo got a reaction from Michael in Namecheap Option For Custom Name Servers   
    Confirmed working for me in 3.3.1!  Custom nameservers are correctly set at Namecheap on service creation.
  7. Like
    danmo reacted to iNode Cloud in Synergy Wholesale Domain/ssl Module   
    hey guys,
     
    any chance of anyone trying to develop a Synergy Wholesale module, i think this will be really good for us in Australia. 
  8. Like
    danmo reacted to Tyson in Namecheap Option For Custom Name Servers   
    The Namecheap update to pass in custom nameservers on service creation will be in v3.3.1. I had an issue with the sandbox failing to create a service due to the custom nameservers, as it appears that unless those nameservers were actually added into the sandbox account, it would fail to add them. A live environment should be fine. Some feedback on your experiences would be great once v3.3.1 is out.
  9. Like
    danmo reacted to Tyson in Namecheap Option For Custom Name Servers   
    I created CORE-1456 so we can take a look into this issue.
×
×
  • Create New...