SSy

Module version: cPanel (ver 2.3.1) Could someone please try to reproduce it and respond in here? It should take no more than 5 minutes so I'm not the only one claiming this behavior exists.

Thanks Paul - I confirmed this through testing as well. However, as stated in the other thread, on the front end, when a client cancels a pending service, it is sending a cancellation request to WHM. This is why I asked about the admin section.

Hey Paul, The steps are outlined precisely in the first post - I will reiterate: 1) Go through checkout process for domain.com 2) Do not complete payment. 3) Add duplicate service to cart, same domain.com 4) Complete payment. When you go to your account, you will now see two pending services - both have the exact same WHM username. After the invoice is paid, the associated account will be provisioned. Then go in and cancel the other, still pending account. The now active account will then be deleted in WHM. I have confirmed that when deleting a pending service from the administrative interface, it does not appear to be sending a request to WHM. However when the client does from the front end, a request is being sent. Blesta 3.6.1 WHM 56 Though the WHM version should have nothing to do with it. I can see the Blesta cancellation request in the logs. Please test this on a live server to confirm it is happening and let me know. As previously stated, this is an extremely dangerous bug, as a user that has a live site may at any point delete a pending service from a previous checkout attempt, and in doing so will purge their entire WHM account without knowing it. The only reason I discovered it to begin with is one our first sign ups did precisely this.

Please avoid responding in threads created by me - help others with your time. I do not find you to be a professional individual.

If the pending service is deleted, will Blesta try to delete it from WHM (as it does on the client side)?

No thanks - I'd rather the automated billing software I'm paying for actually work in an automated fashion.

Well, it obviously is doing it, because I just said it was. Someone else please pipe in, thanks. Edit: Wow, this is yet another nightmare related to that massively dangerous dysfunction bug. I can void invoices, but then blesta will keep trying to create the duplicate pending services. I cannot delete the duplicate pending services for fear it will also delete the active account in WHM. Just fantastic.

I'm sorry - did you just say, as a professional hosting manager that I am now paying for, I should: 1) Check every single new order and manually cancel unpaid invoices and manually cancel pending services every single day? 2) Do it before every client that explores the checkout system accidentally deletes their own WHM account through a Blesta bug? I realize you're economically bound to Blesta, but stop talking nonsense.

On our cPanel logs in Blesta, we are constantly seeing 'createacct' actions for unpaid, pending accounts. Why is this happening?

I just did a full test as explained above, and the pending account cancellation did in fact delete the WHM account that was active. This is a clear and very dangerous bug - a user that uploads content and sets up their website that tries to delete an old pending service a month later will suddenly lose all of their data in one fell swoop.

Client goes through checkout process for mydomain.com. Invoice is created, pending account is created. Doesn't pay. Client comes back, goes through checkout process for mydomain.com. Invoice is created, pending account is created. Pays. Goes back to account, applies credits to last invoice. After 5 minutes, account is provisioned. Client sees unpaid invoice and pending account from previous checkout. Keeps receiving outstanding invoice notifications. Goes in and tries to cancel pending service. Because first invoice went unpaid and account was not actually provisioned, Blesta stores same WHM username for both pending account and now active account. When user goes to cancel the pending account, Blesta instructs WHM to delete associated account from WHM, even though account was never created. But, because username is the same as the now active account, WHM deletes the now active account. The result? In Blesta, client sees one active service, one cancelled service, one closed invoice, one open invoice, and they have no active services in WHM. This is all due to the fact that Blesta is creating pending accounts and invoices for clients prior to receiving payment. It also does not allow clients to void invoices and for some reason, allows them to cancel pending accounts that haven't even been created. This is all very strange, atypical, and buggy behavior. I've now manually had to go in and hack the 'Manage' link out from non-active services to prevent this from happening. And I'm still going to have to go in and manually void outstanding invoices.

Yeah I changed the setting in WHM. Weird bugs as soon as we go live.

From logs: "Sorry, the password you selected cannot be used because it is too weak and would be too easy to guess. Please select a password with strength rating of 65 or higher." How do I prevent this issue from happening?

Thanks very much

Hi there, I looked through the guides but can't find clear information on how package upgrades work. Can you tell me what Blesta will do in the following circumstances: 1) User is on a monthly package, upgrades in the middle of the month. 2) User is on a yearly package, upgrades in the middle of the year. Please illustrate in detail what happens - when they upgrade, do they get a pro-rated invoice for the difference? Is it added as credits to their account that they then have to apply just like an initial purchase? Thanks.

Can you tell me which tables are related and how? I know there is an invoice ID - where is this referenced with regards to services?

thanks, that rectifies the terms of use problem but the email template issue persists. Any idea why that is happening?

Even the terms of use agreement link when clients are proceeding through the checkout point to the old URL

We've changed this but the old URL still remains - any idea why that would happen?

Oh no, it's not the email address that is the problem. It's the URL itself. When people are getting the link to their client area it is: olddomain.com/xxx instead of newdomain.com/xxx

Hi there, We have moved our Blesta install to the live URL and although we've changed the root directory location in Settings > System > Basic Setup and the cron job does have the correct location, the client_url variable used in email templates is still referring to the old URL. How do I update this?

Hi there - very simple question. I want to add a column to the invoices list for clients that displays the domain name the package that invoice is attached to so they know more about the invoice. I know how to add a column and what page to edit, but I don't know the proper syntax to extract that information from Blesta's backend. Right now I have an $invoices variable but it does not contain the URL of the package it is attached to. It does have invoice IDs and what not. Thanks.

Thank you very much - found it based on your instructions.

Anyone have any advice on this? Quite an important thing we need to add there.

So when a user adds a package and is going through the checkout process, there is the Configuration page with the Configurable Options section. Under there I have the 'domain' field for them to add. How can I add text under that? As I know Blesta is so object oriented rather than puzzle around the entire system if someone knows where I can add this directly that would be good, thanks.