Tyson

This will be in v3.5 as apart of CORE-1639.
 
PauloV's patch for service renewals would actually cause an error and still not renew the domain, so you should update the Enom module to the latest version in the beta if you're currently using his patch.

This is fixed in CORE-1695 for v3.5.0-b5.

Thanks, but this has already been fixed in CORE-1690 for v3.5, currently in beta. You may want to update the module to use the latest version from that beta.

Skipping payments on the order form when nothing is due is apart of CORE-1489, which is added in Blesta v3.5.

I don't see how Firebug will help resolve this issue. The API requests don't originate from your browser.
 
As the log states, Plesk denied the API request to add a webspace due to a permission issue. So check your Plesk account for what permissions your API user has access to, as it appears to be limited.

means they are installed.. Plugins > Installed

Nothing new on this yet. Cody will need to decide what he wants to do about it.

SOAP is not working properly on the server Blesta is installed on for some reason.
 
To see a more descriptive error, update /components/modules/interworx/apis/interworx_api.php and find:
throw new Exception("soap_error2"); and change it to:
throw new Exception("soap_error2 " . $e->getMessage() . "\n" . $e->getTraceAsString()); Then try it again. When it fails, look at the log output as you did in the first post.

SOAP is not working properly on the server Blesta is installed on for some reason.
 
To see a more descriptive error, update /components/modules/interworx/apis/interworx_api.php and find:
throw new Exception("soap_error2"); and change it to:
throw new Exception("soap_error2 " . $e->getMessage() . "\n" . $e->getTraceAsString()); Then try it again. When it fails, look at the log output as you did in the first post.

To clarify, the spinning icon denotes the task is currently running. If it runs for too long than seems practical it may be stalled due to error or timeout. In that case, the task doesn't formally end, and is forced to end after the 6 hour wait period. If you continue to encounter this, you will need to try to debug the issue with the cron task or what it is running to determine why it is unable to complete successfully.

Zero quantity config options are removed in CORE-1676. However, removing $0 line items would remove all free items you have as well.

I'm not familiar with the behavior you're describing. Blesta doesn't cancel unpaid invoices. However, in v3.5, it would be possible for invoices created for queued services to be voided if not paid within a few days.
 
What happens to the invoice exactly? What status is it changed to?

I'm not sure if you were being sarcastic, but using DNA as a password would be a hacker's dream come true. You shed DNA all over the place (hair, skin, spit, etc.) and it would be trivial for anyone to get ahold of it. The general "rule" is that if something uniquely identifies you, it could be a username, but not a password.

I'm not sure if you were being sarcastic, but using DNA as a password would be a hacker's dream come true. You shed DNA all over the place (hair, skin, spit, etc.) and it would be trivial for anyone to get ahold of it. The general "rule" is that if something uniquely identifies you, it could be a username, but not a password.

This is fixed for v3.5

One person that had the OP's problem experienced it because they had multiple cron jobs setup that they forgot about after they moved Blesta to another server. I see no other explanation for this behavior other than mistakingly running multiple cron jobs.

Do you have a old cron job running providing false emails?

If we were going to add this, we would very likely use the countries list from Blesta rather than the OP's list. Would that suffice?

Blesta doesn't know what your costs are, rather only the pricing you are selling services for, so I'm unsure how you would expect the system to determine profit.
 
We've had revenue forecasts in the past, but it was met with overwhelmingly negative criticism, and therefore wasn't included in v3. I think most found it to be too "inaccurate".
 
I wouldn't mind having revenue forecasts in the future, but I think better support for determining revenue would be necessary first, e.g. CORE-1479.

Blesta doesn't know what your costs are, rather only the pricing you are selling services for, so I'm unsure how you would expect the system to determine profit.
 
We've had revenue forecasts in the past, but it was met with overwhelmingly negative criticism, and therefore wasn't included in v3. I think most found it to be too "inaccurate".
 
I wouldn't mind having revenue forecasts in the future, but I think better support for determining revenue would be necessary first, e.g. CORE-1479.

We recommend using separate Blesta installations for testing and production if you want to run tests on the system. There is no way to differentiate what invoice/payment is a test and what is real other than the fact you know you were testing it when you performed the action.

We recommend using separate Blesta installations for testing and production if you want to run tests on the system. There is no way to differentiate what invoice/payment is a test and what is real other than the fact you know you were testing it when you performed the action.

We haven't forgotten about the mass mailer, domain manager, or refactoring coupons. I'm frustrated these aren't done yet either, but if they were, then other features would be missing instead. In all likelyhood the mass mailer will be the next major new feature after v3.5, but we still have more tasks to prioritize to determine what the next version will contain.

I think that is one of the issues that will be resolved when the definitions for v3.5 are added to the translator upon its release. Some expected data is missing which accounts for that error.

GoGetSSL brought this issue up with us as well. Our module retrieves all products from their API using the API script they provide in their documentation, so I'm not sure yet what the reason is behind not being able to view all products.
 
 
You should go to edit the package so that products load. This will make an API call, and the raw input/output will be logged and shown at the top of the list under [Tools] -> [Logs]. Click on the table row for that entry, and a list of the Input/Output data will be available. Look for something that starts with "<api-username>|ssl-products".