Tyson

Fixed in CORE-817 for v3.0.5.

After patching, always run the upgrade. It should be the first thing you do after each patch.

Did you ever happen to uninstall the cPanel module? I wonder if packages that were using it are no longer referencing the same module row. Have you tried to re-save the module settings, and the package(s) you're using for that module to see if that resolves the issue?

Testing the settings only checks whether the credentials are valid for connecting to the server. You can check the cron logs under [Tools] -> [Logs] -> [Cron] for the backup log to see if any information is available that describes why it failed to backup.

I don't think there any other tables to consider, however, if it were me, I'd use the API SDK and make a call to Coupons::add() to handle everything. Manually updating table data is prone to mistakes, especially for constraints that are not discernible from the database schema alone.

Cron tasks can fail for any number of reasons, including fatal errors, timeouts, infinite or continuous loops, etc., in which no data exists for Blesta to log. Blesta already logs what data it can. We plan to create a page of somesort to list out failed cron tasks so you can see what task is stalling and clear it, but additional information is not always available to explain why it stalled.

If you have a business PayPal account, the business name set in PayPal is used on the PayPal payment page. I'm not aware of any settings available via the API for setting this, so you'll need to re-check your PayPal settings or contact PayPal support for help setting this up.

Does this occur only with coupons with a 100% discount? When are you using the coupon in the system? When adding a service to a customer in the admin interface, as a client on the order form..?

Yeah, I think we'll need more information to help you debug. The used_qty is set to coupons.used_qty+1 when the service is added, so I'm not sure how it could have the value "=". You can try to dump the $vars data before the service is created to see if something is amiss.

Since client_main.php is apart of the patch, if you did not merge your custom changes with the patched file, then they were overwritten. Based on your code excerpt, $field_values is undefined: 'customfield' => $field_values[0]->value

As the error states, the gateway does not support authorizations.

There was a slight delay in getting the zip up for download. Should be up momentarily.

Twins were that bad this year? I know the Angels were terrible..

This is fixed in v3.0.4.

Fixed in CORE-805 for v3.0.4 of Blesta.

mailto links in the Support Manager Ticket Updated email templates have been fixed in CORE-804 for v3.0.4 of Blesta.

Are you using the API SDK to handle this, or are you calling models directly? Validation errors are set when input fails validation, and you can access them by calling the errors() method, e.g. <?php ... // Set input vars $vars = array(); // Attempt to create the client $client_id = $this->Clients->add($vars); // Show any validation errors if (($errors = $this->Clients->errors()) { print_r($errors); die; } ... ?> You may want to also take a look at the source docs if you haven't already.

Can you provide more information as described in How to Report a Bug? What is in the logs related to the failed Amazon S3 backup, if anything? Amazon has a number of bucket naming restrictions that you may have triggered.

I don't watch them often, but when I do, it's because it's even more boring to do something else!

I find scrolling results incredibly annoying, especially when looking for things that I know are 10 pages away. I find it much easier to click a pagination link to go to page 10, and look around page 9/10/11 than scroll down and search. But of course, that's just me. This idea is still pagination though. Your scrolling just acts as the event to fetch more results. It's the 90s with a twist.

Only my biceps find curling entertaining. But I can find any sport interesting so long as I'm physically participating in it. Watching is boring.

Yes, the mailto link should not have the protocol prepended to it. and the second issue of using http instead of https is a non-issue. If you need to use secure http, you should specify it in the email template. But both of these are very minor issues are easily resolvable by editing the email template.

Glad you got it fixed. I guess the universal module will be v1.0.10 for v3.0.4 of Blesta then.

I believe the latest version of the module is 1.0.8 for v3.0.3. There is a 1.0.9 for v3.0.4 of Blesta, but CubicWebs may have downloaded an update to 1.0.9 posted on the forums sometime afterward (I'm not sure).

Have you taken a look at this thread? It may be that the ticket exists, but the ticket reply (that contains the email) does not, possibly due to an error experienced when Blesta received the email. If you can confirm whether that's the case, it'd be useful for us in pursuing the issue further. FYI, I primarily use Thunderbird, and emails are handled just fine.