Jump to content

Tyson

Blesta Developers
  • Content count

    3,196
  • Joined

  • Last visited

  • Days Won

    173

Tyson last won the day on June 29

Tyson had the most liked content!

About Tyson

  • Rank
    Staff

Profile Information

  • Gender
    Male
  • Location
    Anaheim, CA

Recent Profile Visitors

1,880 profile views
  1. Tyson

    Prorate Calculation with renew date

    When I was referring to the expiration date calculation, I meant the service the module is integrating with, not the module code you wrote for Blesta. From your module source, yes, you are simply setting the years to the number of years for the term from the package pricing, i.e.: $vars['years'] = $vars['years']."y"; That is totally fine. What I was wondering is that once that API request is made, how does their service handle the expiration date? If "$vars['years'] = 2;", you will send 2 years to the API, but will they interpret that as adding 2 years from today, July 19, 2018, or will they add 2 years onto the current domain expiry date? If the current expiry date is February 1, 2020, will setting 2 years make it February 1, 2022 or July 19, 2020?
  2. Tyson

    Prorate Calculation with renew date

    Does your module set the new domain expiration date as a number of years from today or from the current expiration date? For example, if there are 2 years remaining, and you are renewing for 3 years, does it set the expiration dato to (3 years - 2 years remaining = 1) one year or (3 years + 2 years remaining = 5) five years from now? From your example, it seems like the latter since they renewed it to expire in 1 year but then upgraded to 2 years and the result was (1 year from now + 2 years = 3) three years from now (2018 to 2021). If that is indeed the case, I would think your domain module would need to set $vars['years'] to the difference of the years remaining and the years added.
  3. Tyson

    Prorate Calculation with renew date

    This sounds like 2 potential issues: The invoice renewed for 3 years instead of 2 (this may be an issue with the module?) The amount due on the invoice for the renewal was prorated to a smaller amount than expected for the service length Can you duplicate this behavior with other services? How about duplicating the issue just for the renewal pricing? If you can provide steps to duplicate the issue in Blesta, perhaps with services using the None module, I may be able to see if this is an issue with prorating service upgrades.
  4. Tyson

    Automated NET_30 Payments

    Yes, take a look at Invoices::add, which you can call via the API.
  5. Tyson

    Add credit via API

    You should create a new custom payment type if you haven't already, under Settings > System > Payment Types. Then when you create the transaction by calling Transactions::add over the API, include in $vars the keys type and transaction_type_id. type would be set to "other" and transaction_type_id would be set to the integer ID representing the payment type you created under Settings > System > Payment Types.
  6. Tyson

    Add credit via API

    Credits are just transactions that are not applied to an invoice, so you can simply create a transaction.
  7. Tyson

    Invoice Date and Due Date missing on invoices and views

    I think any update we would integrate for this would be to simply require a non-empty format to be set on the settings page.
  8. Tyson

    Paypal Recurring Payments

    Oh, so you had changed the location of your Blesta installation a while back? I can see why Blesta never receives the IPN then. It's unfortunate that PayPal does not allow you to update existing subscriptions to change the IPN URL.. are you able to have the old URL forward to the new URL? By default, the URL should be https://domain.com/PATH_TO_BLESTA/callback/gw/COMPANY_ID/paypal_payments_standard/ where PATH_TO_BLESTA is your Blesta web directory and COMPANY_ID is your company ID. GET and POST data will need to be passed along.
  9. In v4.3 you can delete a client and all of it's related information, including services. Packages can be deleted so long as no services exist that use it. So in v4.3, if you delete your test client that has test services, you can then delete the test package afterward.
  10. Tyson

    Paypal Recurring Payments

    You may want to check with your PayPal account to be sure that the IPN request is set up to be made for the recurring payment. Sometimes, particularly if the IPN request had continuously failed, PayPal will disable it and no longer send IPN requests. It might be referencing the wrong URL (for example, if you moved your Blesta installation to a new location), or if the server hosting Blesta does not support TLS 1.2, PayPal will not be able to negotiate a handshake with the server in attempt to send the IPN. The latter doesn't seem like the issue since you receive manual payments, but still worth double-checking. If either of those is the problem, you'll need to resolve them first and then re-enable the recurring IPN in PayPal.
  11. I've created a task for us to look into this in the future, CORE-2736
  12. Tyson

    Directadmin module Bug

    This is updated in v4.3.0 as apart of CORE-2637.
  13. Tyson

    validateService $vars "configoptions" keys inconsistent

    Just FYI this is assigned CORE-2735.
  14. Tyson

    Sessions table not emptied

    Did the garbage collector ever run to purge your old session data or do you think this is still an issue with Blesta?
  15. Tyson

    Sign Up Bug

    I'm unable to duplicate the OP's original issue. There may be something else going on there. As for the other issue with the "Title" field not appearing on order forms, CORE-2734
×