Jump to content

Paul

Blesta Developers
  • Posts

    6,567
  • Joined

  • Last visited

  • Days Won

    817

Everything posted by Paul

  1. If you have an owned license with us directly, we can provide a dev license at no charge.
  2. Thanks for the suggestion, anyone else have any thoughts on this?
  3. To be safe, you will need to import your data into a fresh 3.0.3 install. Install with a trial key, and keep your other v3 install up and running. Then run down and compare the two after you import your data, and update the themes, email templates, and other settings with the changes you have made. Having them side by side should help.
  4. Just a note, the maxmind details should still be available via maxmind's login area under logs, even if the threshold was so high that Blesta rejected the order outright.
  5. Yes. What I meant about late notices and auto-debit is that regardless of how an invoice was created (Automatically by Blesta, manually through the interface, or via the API) the invoice is treated the same way moving forward. There is a feature that can send up to 3 late notices / payment reminders, and a feature that can automatically charge a credit card x days before an invoice is due. These features can still be utilized, if you want, even when creating an invoice via the API. I mentioned this because in your original post you asked about a reminder.. so, those reminders, if you have them set up, will still be sent when creating an invoice via the API.
  6. It's against Mastercard/Visa merchant rules to store CVV data in any way, shape, or form. The CVV data is passed along by Blesta when processed live via customer input, but never saved. This makes it impossible to send CVV data if using auto-debit. Cody or Tyson may be able to comment on sale vs preauth, however I'm not sure I see the correlation with CVV data. I wouldn't think a capture should take place if there is an issue with CVV or AVS. Don't most merchants automatically do a preauth, then capture? I guess the side affect here is that the immediate void BluePay is doing results in the funds being held up in the customers account for several days, and you are charged a processing fee?
  7. You may wish to use the API to create the invoices on the 1st of the month, each month, based on your other systems evaluation of whether they owe $5 or more. I think this is where you're headed? In this case, the client would have no services in the system, and Blesta would not invoice on its own. Any invoices you create via the API will still work similarly however, with late notices being sent how they are configured, and auto-debit running if configured as well.
  8. Invoices are sent out X days before a service renews. This value is configurable, so you can invoice someone 5 days before, 10 days, 30 days, etc etc. The due date of the invoice is always the date the service renews. Yes, virtually everything you can do in the interface, you can do via the API. Essentially all public method models are available through the API, including those for plugins. See http://docs.blesta.com/display/dev/API for information on the API. If you scroll to the bottom you'll see source code documentation which you'll need.
  9. No, Blesta will only pull from the database referenced in the config file in config/blesta.php You will need a v2.5 license. If you purchased before Aug 14th and bought an owned license you should have a v2.5 license also. Open a ticket with us with the new domain so we can re-issue it to that. If it will be installed at the same domain/subdomain as before, regardless of sub-directory it will work. If you have a backup and might need to restore it, I would copy it down just in case. Did you verify your data was imported properly initially? Were there invoices prior to Aug 1st?
  10. Paul

    Removing From Cart

    Is this still an issue, or was it related to http://www.blesta.com/forums/index.php?/topic/1102-serious-cache-issue/#entry8970 ?
  11. Paul

    Variating Pricing

    You can create a recurring coupon, and customers that apply the coupon would get that amount, or percentage off every time it renews per the coupon.
  12. It's likely we will make the delivery methods modular in the future, as there is at least 1 other method we are planning to implement. So, if you don't need interfax now, I suggest simply replacing it with your metrofax implementation. You can refactor your code later once it's modular and then have support for both.
  13. You could remove non-required fields on the order form by editing the template and setting them to style="display:none;", but modifying them, depending on what you are trying to do may be an issue. Of course, if you disable the field from displaying, and then create a custom client field to replace it with your changes, that may work out.
  14. That is odd, I wonder why it doesn't appear. Are you certain that the staff member you show with all departments assigned is your staff member? In another case, someone migrated to Blesta and they had 2 staff members with the same name. It appeared they had full access, but it was the wrong staff member and once we added the other staff member in it worked fine. I wonder if it's possible that that ticket is some how not assigned to a department.
  15. Paul

    Serious Cache Issue?

    I'd move, there's something funny going on there. Who knows what else might be affected, it's a risk I wouldn't want to take!
  16. Server specs look fine, shouldn't be an issue. If you like, I'm happy to login to your install and see if the data updates for me. If that will work, open a ticket with the login details and I'll check it out.
  17. Blesta doesn't cache any of this data, and the widget should be making a query for this each load. If you clear your browser cache, does it have any impact? Have you tried from any other computers? What web server are you running?
  18. Can the DA web install of CSF be accessed via the API similar to the cPanel version?
  19. Thanks, we'll take a look. It may not be properly converting the time from UTC.
  20. Can you provide an example of some of the elements of the widget that don't refresh. By refresh, I'm assuming that you mean when the widget reloads the data is stale. The system overview widget does not utilize ajax and automatically refresh content.
  21. I believe the original intention was for the package to simply become unavailable on the order form once the quantity has been exhausted. A predefined message indicating a package has sold out might be a good idea, but this would be more of a feature than a bug fix since it's not what was intended. We are happy to consider such an option.
  22. I think enough has been said on this, closing this thread.
  23. Paul

    Serious Cache Issue?

    Good to hear that you've isolated it to that particular VPS. Very curious what the issue is there, but awesome that it's working on a new VPS.
  24. It was good chatting with you. I have not yet attempted to replicate the issue, but Mike said he was able to confirm it so I added it to task CORE-782, tentatively scheduled for a 3.0.4 patch. I wanted to update this thread to reference it publicly and we will try to respond here once the issue is confirmed and resolved.
×
×
  • Create New...