Jump to content

Rob T

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

657 profile views

Rob T's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Is there a link for documentation?
  2. I can confirm that this bug still exists in Blesta 3.6.1 also. Thanks
  3. Blesta Version: 3.6.1 SolusVM Module Version: 3.4.2 SolusVM Version: 1.18.01 (latest) Problem: When processing an automated upgrade, Blesta is changing the RAM, bandwidth, and CPU core attributes for the new plan, but is not properly updating the HDD space attribute. This is affecting VM's with KVM virtualization. Unknown if other types are affected. SolusVM API Log Output: status => successnvserverid => 112nmsg => Virtual server plan changed (appears to be successful) Steps to Recreate: 1 - Create new KVM VPS using Blesta via API 2 - Process upgrade order to higher package with more disk space than original plan In our particular case, our basic plan includes 1GB RAM, 1TB bandwidth, 1CPU core, and 15GB HDD Space. We noticed that several users who were attempting to process an upgrade order would get partically upgraded to our next plan properly (2GB RAM, 2TB bandwidth, 2 CPU Cores), but that the disk space reported in SolusVM would remain at 15GB. Screen shot attached is the resulting resource information for an upgraded VM.
  4. Hello, My apologies for omitting the important info. That's what I get for submitting bug reports at 2AM. Blesta Version - 3.6.0 Paypal Payments Standard Version - 1.2.2 Step by step: Create coupon configured with option Apply when a service is added only Place order with coupon (in our case, the service cost is $18/yr, which after a 30% coupon for the first year should be $12.60/yr) Select Paypal Subscription as payment option When forwarded to Paypal, subscription is pre-populated with $18/yr rather than $12.60 for the first year and $18 per year thereafter
  5. I've noticed a bug that occurs when a customer places an order using a coupon and Paypal subscription for payment. We have a coupon code that applies for the first year of service only, leaving subsequent years to be billed at the normal rate for that service. When the customer pays using a non-subscription paypal payment, the proper invoice amount is shown when the customer is forwarded to paypal. When they choose payment via paypal subscription, when they are forwarded to paypal, the total shown to establish the subscription is the full amount, rather than the discounted amount. If the customer proceeds with setting up the subscription, the difference is credited to the customer's account as a credit, but that's not the proper behavior. What should be happening is that paypal should be instructed to create a subscription with payment of X for the first year, followed by Y each following year. Paypal certainly has the ability to create subscriptions in this manner, as other billing platforms we use handle this situation quite commonly.
×
×
  • Create New...