Leaderboard

and what about the custom works ? i know there are a lot of module/plugins already done by devs but is not available for other clients . i have some that will be or other maybe for free and some PAID , but not now . when i client hire me to develop a module/plugin and tell me that the work should not be selled to others, i never never accept . i accept only if the client accept my two conditions 1 - i have the right to sell the work (module/plugin) to others after X mounth from finishing the work . 2 - i have the right to publish the work freely after X mounth from finishing the work . for my vision, the client pay for the service and not for my CODE . i can conserve the work in the background and releasing it only if a i found/feel that work is for a MADE-HOUSE custom solution . so be happy , ihave some modules/plugins will be for the community in some next mounths

I think I found the issue. Will update this post with more info once confirmed.

Lets face the fact Blesta's domain management is TOTAL CRAP.. WHMCS and Clientexec do it way better in every way. Blesta does NOT have a proper domain offering, period. seems to be that its just not a priority. Domains are totally unique to generic products and should be treaded as such. For webhosters, domains are part of hosting, the most important part. The enom module for Blesta is 10 years behind that of WHMCS..currently we have the bare minimal basics. What if one wants to only sell a domain ? Does not appear blesta support domain only products. Domain Transfers ? Renew pricing ? Allot of domain renewals cost more than the initial registration fee Name spinning ? Importing and sync of prices from enom & namecheap ? Importing and sync of TLD's and new TLD's from enom & namecheap ? What about .co.uk that requires a 90day before expire renew ? Direct managment of the domain hosted on the registrars nameserver ? Proper whois lookup or usage of dig to check if non api domains are registered/available ? A domain email module, where domain orders are emailed, still does whois checking for availability. Some tld's are still stuck in 1970. Domain availability widget ? ^^ BLESTA FAILS FOR ALL OF THE ABOVE --- I challenge Blesta to make a billing brawl using domain management and include enom's module... btw if you want a reseller enom account, or access to the enom api sandbox , contact me and ill sort you out with an account.

Version 3.5.0 is now available. You can download it in the Client Area. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Migrating to Blesta See Migrating to Blesta in the User Manual for instructions. Overview Upgrade/Downgrade Config Options SolusVM Improvements Custom Reports Much more... PHP 5.5+ Users Included in this release is a /hotfix-php5.5/ directory. Please use this directory to overwrite the default /blesta/app/app_controller.php, /blesta/app/app_model.php, and /blesta/app/models/license.php files. Release Notes See Blesta Core - Version 3.5.0-b1. See Blesta Core - Version 3.5.0-b2. See Blesta Core - Version 3.5.0-b3. See Blesta Core - Version 3.5.0-b4. See Blesta Core - Version 3.5.0-b5. See Blesta Core - Version 3.5.0. For older releases see all Change Logs.

I think it would be alright, but perhaps consider putting the gateway name in the text so it's very clear. "Check out now with PayPal/Skrill/<gateway name>" type thing.

i need to buy a cheap licence unbranded of course , anyone need to sell thier licence PM me please . best regards

I completely Agree with you @Naja7host , some of us create modules but never wan't to share worrying of a competitor getting an advantage. We do need more premium modules/plugins for Blesta, Sometimes developing modules is too expensive if you need a lof of modules like i do, but having a place to buy modules will be cheaper for me as the client and will be much profitable for the developer I believe. and will surely remove this

What do you think of generic buttons for all non-merchant gateways instead? e.g. "Buy Now", rather than gateway-specific buttons like "Checkout with PayPal", "Pay with Skrill", etc.

After receiving numerous complaints about the current buttons not being clear, we've found folks really like this one: This should definitely be updated to be more clear to folks trying to make payments via PayPal.

We've got a small list here: https://licensecart.com/community-addons

You can create negative invoices in v3.5. It won't automatically create any credits on the client's account for the negative sum, but you can add credits yourself by recording a payment for the same amount.

I have pushed CORE-1516 to the top of the backlog, this should take a couple minutes.

I believe this will do it for anyone wanting to make this change now. To change the character limit manually, edit /components/modules/cpanel/cpanel.php and look for: 'rule' => array("betweenLength", 1, 8), Change to: 'rule' => array("betweenLength", 1, 16),

We already have a task (CORE-1516) on record to update the cPanel module to allow for up to 16 character usernames. cPanel does enforce these character limits, and while I agree their username character limit scheme is absurd, it is still a requirement of their system. This is referenced in their API documentation and in a blog post regarding the version (11.44) that they introduced an increase in username length. While Blesta can normally get away with avoiding input requirements that other systems enforce, doing so would pose a large usability problem and have unnecessary performance costs in Blesta, likely to cause both clients and admins headache. Any invalid field data will not be known until the service is provisioned, at which time it will fail. If the cron is provisioning the service, you may not know why the service failed, as the error returned from the module may not be logged, or may be too obscure to determine the cause (e.g. "Error #50191") without requiring manual intervention. These failed API requests and the need for manual intervention after the service should have been provisioned can be avoided by requiring valid information to be entered from the beginning. Some might want to increase the cPanel character limit themselves until an official release is made to the module, in which case this thread may be useful in describing how to do so.