Leaderboard

Hey, Braintree Payment Gateway version 1.0.1. (Also affects 3rd Party Braintree version 1.0). Currently the 'merchantAccountId' is not being passed to 'Braintree_Transaction::sale' (or even saved anywhere) so will only charge in the default currency set in braintree. https://developers.braintreepayments.com/reference/response/transaction/php#merchant_account_id I personally use the 3rd party module so have made the changes myself for it to work, if anyone needs help with getting it to work before a fix is in place just send me a message.

Ideally, an import/reversion script would be necessary to ease the switch back from the other module. Such a script should map the module_row_id and service fields over for every service. A somewhat generic script could be written to handle this transition. It's good to hear you were able to handle that manually, though. If you update the service from the admin UI, the "cpanel_confirm_password" will be saved again, and the password fields encrypted if they weren't already from the other module.

The service will only be activated under the following conditions: Your cron is setup to run automatically at a certain interval, or you run the cron manually The automation task "Provision Paid Pending Services" is enabled The invoice, if any, associated with the service is paid in full The service is in "Pending" status. If it is "In Review", then the order form you ordered it from is set to "Require Manual Review and Approval of All Orders". This requires an admin to accept the order before it can be changed to Pending status, and this can be done on the [billing] -> [Overview] page in the Orders widget. If you don't see the orders widget on this page, you can add it using the link on the left to "Manage Widgets". I would recommend checking the Module logs under [Tools] -> [Logs] to see if any requests were made to Multicraft. There may be an error preventing Multicraft from adding the server, and you will be able to find more details by looking at the raw Input/Output when clicking on the table row.

I can't see this happening. We're talking about backing up a database. It's a critical process that should be executed as fast and as efficient as possible. Someone could create a plugin that uses this slow, and not very well written, library if they wanted to avoid using exec commands. But the penalty is not worth the gain in my opinion.

Thanks its fixed now

If I remember correctly default cPanel does use cpanel_confirm_password, but it's not important as you discovered. I think it's used for password changes. I moved from tasty to extended in a similar way a couple days ago. Good thing about extended is it uses the same keys as default so if it does go tits up you'd only need to swap out module_row_id

I feel your pain and while I don't have the answer to get back to the stock configuration, I did see that cyandark is working on a way to merge Tasty cPanel to his version of cpanel Extended. This may be an option for you?? http://www.blesta.com/forums/index.php?/topic/5552-module-cpanel-extended-v41/?p=39797 Otherwise, I'm not sure what you can do. I've done the same and I'm not installing any more 3rd party plugins or modules either. I wish Blesta could grow a bit faster and get more of these great features integrated into the core. Hopefully some day soon.

Definitions Translated: 249 of 8296 (3%)

4.0 is next, no ETA yet still very much in development

Hidden tasks, we'll open it up as we get closer.

The plan is 4.1 will be for domains. 4.0 is next, in development.

Upgraded captain. Still waiting for affiliates plugin? :3

Correct you need the uploads file permissions and then this set-up (this would be done if the uploads folder was set-up when a plugin is installed). - uploads --- system --- 1 ----- client_documents ----- download_files ----- invoices ----- support_manager_files Remember depending on your plugins you might not need some. PS: Your uploads file should be out of public_html or html folders for security.

So I purchased a Blesta license before v3 was released. Was very excited and was ready to move my entire business over, but then found out that a lot of the features we use were missing that made me change my mind. So I thought I'll try again sometime in the future after Blesta matures a bit more. The recent price increase by a competitor software was a push to reconsider Blesta again. But I am very disappointed at the progress! In recent times I've found our domain business is doing really well and now accounts for almost 40% of all sales. But the Blesta module for eNom has not been touched in years. I remember this being the main reason why we didn't switch. Fast forward a year +, and this is again the deal breaker for us. The eNom module is very limited and lacks very basic domain registration and management features, not enough for a business that has a growing domains division that accounts for 40% of all sales. Being a UK based company that manages a lot of .UK domains it still lacks more specific API field requirement options as well. It has already been raised and feature request submitted by another user over a year ago: http://www.blesta.com/forums/index.php?/topic/1990-enom-couk-registrations/ http://www.blesta.com/forums/index.php?/topic/2626-orguk-domains/ As you can see, no official reply posted and feature request has not been acknowledged. In the meantime, a competitor is really improving their domain / eNom module because they have already identified that domains are becoming big especially with hundreds of new gTDLs already released and more in the pipeline. Furthermore, they are adding NEW features. Features such as "Claim Your .UK" addon, domain name spinner, etc. etc. But Blesta development seems to have other plans and priorities lie elsewhere. This post isn't meant to be a complaint but rather the main reason why we are not using Blesta. It's competitor seems to be one step ahead. I keep on reading on other forums how Blesta is the best software and has ALL the features now but really we shouldn't kid ourself, it still is lacking some basic stuff, especially domain registrar modules. I'll come back again in a years time and see whats changed and if theres any new developments. /end

Well you are right here, I turned to Blesta following the latest v6.0 release. I've got a dev license setup and the hype is not living up to expectations. I am a prime example of this. I ended up just renewing my support and updates with WHMCS early to lock in the lower price only because Blest doesn't offer what I need right now while WHMCS offers pretty much all the features I need out-of-the-box. I will visit again before the next renewal to see the progress of this in Blesta, fingers crossed this is the final year of us using WHMCS.