Jump to content

gutterboy

Members
  • Posts

    284
  • Joined

  • Last visited

Posts posted by gutterboy

  1. We removed the primary nav as it didn't work with our design we have and hence we would like to add the links for "Contact Types" and "Payment Accounts" under the "My Information" block on the client main only.

     

    I have been looking around and found this: http://docs.blesta.com/display/dev/Plugin+Actions

     

    So it seems I can't add anything there without attaching it to the primary nav with the "nav_primary_client" action? Also unsure how to get it to just show on the client main.

     

    Any help!?

     

    Thanks!

  2. Is it possible to initialize all of blesta apps/models/etc in a script completely external to Blesta?

     

    So far I've found that I need to load the following files:

     

    require_once('../lib/init.php');

    require_once('../app/app_controller.php');

    require_once('../app/app_model.php');

     

    Loader appears to be working properly also:

     

    Loader::loadModels($this, array("Clients","Accounts","Services","Packages","PackageGroups","PackageOptions","PackageOptionGroups","Companies"));

     

    If I then for example do a call to $this->Clients->getAll(); or something similar it works as expected and I can print_r the return array, but as soon as I make a call to anything needing to write data it just fails, we'll say $this->Clients->add() for example.

     

    I get no return, no errors, nothing.

     

    Have you considered using the API?

  3. I have noticed currently if you are adding a payment account for example where it provides the dropdown and shows all the available contacts you can copy information from.

     

    Currently it just shows the name of the person as the selectable text; this can be confusing for example if the primary AND billing contact both have the same name (which would usually be the case); shouldn't this show "Primary" and "Billing" instead? Having each value in the dropdown the same doesn't really make much sense.

     

    Thanks!

  4. I don't believe so, billing is for bills, contact information is for anything to get in contact with you.

     

    You can use the CSS / Admin one and find the class if there is one, and then display:none, and then make a html one and add your new one in. But I'm not sure or you could just change the language file and then replace it when it you update.

     

    But this is for bills haha....... it's adding a new payment account, not a contact type.

  5. That's right. With gateways that support tokenization, Blesta stores the last 4 encrypted and the expiry date. The last 4 are stored so the client can identify the card in the payment account, and the expiry so that the client can be notified when their card is expiring and needs to be updated. CVV data is NEVER stored in Blesta.

     

    If we implement token storage for eWay, it will then support both local and tokenized storage of card numbers. Some people prefer local storage, because it means they are not "locked" into using a particular gateway. Of course, tokens are much more secure and we recommend using token storage whenever possible.

     

    Thanks very much Paul!

  6. http://docs.blesta.com/display/user/eWay

     

    Token Storage is not currently supported (I think this is it https://www.eway.com.au/developers/api/token), but would make a good feature request. Most likely it was not available when we initially implemented eWay.

     

    Thanks. :)

     

    Ok, so basically you're saying if you use eWay then the card number will be stored locally, that is until if and when tokens are implemented?

     

    From what I can see with Stripe only the last 4 digits are stored in an encrypted state.

  7. What's your definition of non-recurring automatic payments?

     

    Any payment processed through a merchant gateway can be processed by Blesta automatically when Blesta determines the payment should be processed.

     

    Thanks Cody!

     

    My definition of non-recurring automatic payments is just a payment which only happens if necessary. For example, a recurring payment is generally the same every month and always is due; with our site, whilst we may invoice every month, the user may not owe anything or may a variable amount above $0.00. So basically we want to be able to automatically charge the user only if they have outstanding invoices; as it's possible some months they may not have them + the amount they owe will vary.

  8. Recently on my dev installation I have noticed values I have entered in for some plugins / gateways have mysteriously gone blank.

     

    For example, I have the shared login plugin installed and then I noticed we started having problems with it not working - I checked the key and it was blank.

     

    Then we were having issues with Paypal not working, went to check the settings for it and noticed everything I entered in the fields had also gone blank.

     

    I assume the values for these are stored in the database and not files that I may be overwriting?

  9. This has been fully added to my next release of "Admin Tools" plugins , now you can set wich IP to access admin area , if not authorized redirect to 404 error page .

     

    also i have implemented a new security way , to block access direct link of uninstalled plugins , now if the plugin is not installed no one can access it , i'm working now in modules too , to forbidden access if not installed .

     

    need also block access to  client side by IP :)

     

    i will finish the complete rewrite of this plugin and making some tests  and i will make it available next week .

     

    Most excellent! :)

×
×
  • Create New...