Paul

If you email me (sales@) and reference this thread, I'll get you set up with 4.0.0 beta 5. cPanel extended and Blesta CMS are not included extensions, so I'm assuming you're planning to source those separately?

All that means is now you have to do it.

It may not be validating all the fields at once. If you fill in a username and password only it'll probably still complain, just about something else. It could probably be improved, sure. Honestly, I'd like to show errors next to their fields, but that's a lot more work.

The task is missing so many details.

Are you all happy with what's described in CORE-2056? I'm going to bump it into consideration for 4.1. While it's assigned to that version, there's no guarantee anything in that version will be included. Speaking of fraud checks though, we also need to modularize this so it's easy for people to build others and drop them in. I'd love to be able to run fraud checks through multiple different APIs at once too. More advanced options like text or phone verifications would be great. Someday.

4.1 is likely to consist largely of us mopping up a bunch of little tiny things, fixes/tweaks/improvements that have been on hold while we finished 4.0. We want to get 4.1 out fairly quickly, while also working on some more advanced features (domains) in the background. However, domains are not going to hold up any releases.

Was this resolved in another thread? If not, try enabling error reporting in your /config/blesta.php config file.

At a minimum there would need to be some confirmation. I like the idea of a self-deleting trash bin. You can recover a mistake, but then not much effort beyond that. It's a little bit simpler than what was originally in the task. Feel free to nudge us on this again a little later.

I have updated CORE-1589 to simplify it a bit, please take a look and let me know what you think. The idea is that tickets can be deleted, and are processed after a period of time so that if it's accidental it can be recovered before it's gone.

Yeah, I think that's what it comes down to and there are several areas we need to make similar changes to.

To be honest, I'm not sure. I'd suggest testing with beta 5. If it's not, it'll be easier to implement with the new item pricing.

No immediate plans for this, but we're open to the idea. Why do you want to delete tickets? We see deleting tickets as something that generally shouldn't happen, except under unusual circumstances. Which is probably why it has thus far not been implemented.

It looks like Tyson created a task, CORE-2337 to look at this. If you have STRICT_TRANS_TABLES you may try disabling that to see if it makes any difference.

Great success! Thanks for the heads up, and glad no gunshots were necessary.

To move them into Blesta you would create a service as an admin, and uncheck the "Use Module" option, then edit the service and make sure the username is correct. They should then be linked up. You may also want to uncheck the "Create Invoice" option, and modify the renew date to match their next renewal date.

CORE-2338

That solved it for this customer? Or you have to check the box, and modify the database each time for this customer?

I believe we disable the payment button in v4 after it's clicked once. I'm not sure if this would solve the issue with refreshing the page vs double clicking the button though. Still, the confirmation page shouldn't charge the card again if refreshed. Can anyone else confirm? Also, what version of Blesta?

Are you using cloud linux? See this post

Does the customer have a tax exempt status that is different from customers that work? I'm assuming that recurring invoices for some customers work without error, is that right?

Is this just a recurring invoice, unattached to a package? Look in the database in the invoice_recur_lines table for the column "taxable". Look at the data, what are the values there for this recurring invoice that you get the error with?

That's a database error. Have you made any manual changes to the database? Do you have taxes configured? You could try re-saving all your tax information.

You can also enable error reporting to see if any more information is displayed: To enable error reporting, edit /config/blesta.php and change Configure::errorReporting(0); to Configure::errorReporting(-1);

Awesome, glad to hear! Thanks for the update

Yes! v4 buttons. Looks nice and clean.