evolvewh

Thank you!

Can anyone else verify this? It would be really nice to get it fixed asap so clients can use this payment option.

Choose these 2 options under the 'manage' settings for the Paypal gateway and then your customers can setup a recurring subscription: Allow users to modify current and create new subscriptions One time and subscription payments when possible

I don't think there is anything for TC Admin support in this version. You can look at the current task list for beta 4 to see approximately where they are: https://dev.blesta.com/projects/CORE/versions/11004 To me, Beta 4 is quite stable (Don't use it for production though) so I'm hoping the rest could move along nicely towards a release.

I knew that was the case. I am just testing it out for the first time and there are some 'weird things' with this module. For example, whenever settings are updated on a given page (pricing, api credentials, etc), the admin stays on that page and then has to click 'modules' on the far left of the screen and then click 'manage' for the module to get back to the other settings offered for the module. There are a few un necessary clicks here and there. I know it was written by them so you don't have much, if any control over it for the time being. Just wanted to point a few things out and maybe they'll see it while browsing the forum.

Is there a reason 'Test Credentials' are required if I just want to enter live credentials and be done? I'm just copying my live credentials from the module that Full Ambit Networks created and didn't feel it was necessary to add Test credentials as well.

I should have done this sooner but I have sample data I'm testing with v4.0 b4 and it worked just fine for me to add an ACH account. It's very possible that it was user error on the clients part. Additional Testing If the user goes and adds ACH as a payment account, it works. If they login to pay an existing invoice but they don't create a payment account and instead attempt to pay one time by ACH on https://domain.com/client/pay/method/, that's when they're unable to enter a routing number after entering an account number. I tried it by using the tab key and by using my mouse to put the cursor in the Routing # field and neither option works. I'm automatically redirected back to select 'New Payment Details' and 'Other Payment Options'. This happens on v3.6.2 and v4.0 b4

She was logged into her account trying to pay a renewal invoice. She said she couldn't get past the 'review and confirm' page because she was being sent back to the first step so there isn't anything in the logs and she never received any emails about it.

I just worked with a client to setup an ACH payment account and they ran into issues with it. They tried adding a checking account. For some reason, they had to enter their routing number before they could enter their account number. I've attached the screenshot and the first field is account number. Once they got both #'s entered and on to the review and confirm page, they were always forced back to the previous page and they weren't able to finalize the payment method. There's nothing in the error logs to report. I'm using Blesta 3.6.2

Is it something you can post here to work with the original module or is it only a fix for your Reloaded version?

I'm confused as to why you would post it here in relation to v4 Blesta when it's not a standard option for the core part of Blesta. It only relates to this 3rd party Plugin unless I'm missing something else here.

That never existed in Blesta. It's only a feature of SupportPro which is a 3rd party add on.

One other question. Can I downgrade to another version or is it not going to make a difference? I have v5.1 right now.

Thank you for doing that! Can you link to the previous version in the meantime?

Hi, I'm trying to download v5.1 and the link is returning a 404: https://github.com/CyanDarkInc/cPanel-Extended

Why should they hang around at all when there is a voided invoice to reference what they originally had? I think you figured it out now but I'm using v3.6.2 with no custom coding or plugins related to orders.

Here's the details to reproduce: 1) Place an order for a service 2) Mark the order as fraud 3) Void / Refund the transaction My only guess is that it's based on the order that I did it (step 2 and 3)

We had an order come in that I marked as Fraud and I refunded the payment (figured I'd get a chargeback if I didn't). When I went to Billing -->> Services, the service ordered showed up under 'Review'. Shouldn't this service just disappear since I 'reviewed' the order and marked it as Fraud? Maybe this has already been addressed as a task for 4.0 but I'm not sure.

You can use Github or Diff Merge (if you're using a Mac). If there are a smaller amount of changes, you can keep track of them in a document by documenting the files and line # changes. I'm sure there are other tools out there but these are the methods we use. Blesta will not detail the specific changes within files for you. If it's a patch release, the patch will only contain the modified files and not the entire set of Blesta files.

I'm not sure what needs to be done with the domain registrar modules but I see that Enom has new API information and I would guess other providers do as well: http://www.enom.com/domains/new-transfer-policy/

This is what it said: The referenced transaction does not meet the criteria for issuing a credit. I won't call it a bug but maybe the error notification can be changed a bit?

It took almost 5 or 10 minutes for the confirmation email to arrive. Check your spam folder as well.

I just wanted to create a quick post to say Thank you to the entire Blesta team and the work that you do. When we used WHM**, I remember we were constantly applying patches and modifying configurations for this module, that gateway, etc. With Blesta, once it's setup, I feel like we're spending a lot less time dealing with these types of issues. While there are features that we want and are anxiously awaiting to have available, I still feel like we've made a better choice by using Blesta for our billing system. Keep up the great work and we can't wait to start using v4.0!

I attempted to refund a transaction made today (not settled) and received the following message. Is it because it needed to be voided instead of refunded? This makes me think that I should have used void and if possible, this error message should have said that I need to void vs. refund. For now, I logged into authorize.net and voided the transaction there. This is using Blesta v3.6.2

I wanted to bring this up again and see if it can be moved up at all? I'd even be willing to put some money towards getting it implemented. For some reason, I've got support tickets from different clients that aren't very descriptive and they're very similar ('error', 'bug', etc) and it would save a lot of time if we could see the clients name and/or email address (if they aren't a current client) within the list of tickets.