Leaderboard

Yes mate for blestar

Blesta is Open Code, not Open Source. Encrypt the paid modules is necessary to protect the license system.

Welcome blesta 4 Lutfi Theme 100% free. Written more than 300 element and write with love Its clean design & powerful premium functionality allows you to creating profesional hosting site. Designed for starup hosting, small hosting company to save expenses Easy to change colors of elements, modify the parameters of elements, also you can add more shortcode from basic bootstrap element up to 100+ combination. Free But Premium Features? Completed HTML Demo File Powerful, Minimal and Clean Design Include features for hosting site Bootstrap 3.3.7 Super Responsive User-friendly & 100% validate Code Sticky Header Mega Menu Font Awesome icons Flat icons Themefy icons Fully customization Minimum Blesta 3.6.2 Download Lutfi Demo Main Site | Blesta Demo Ony Image More functionality & active support? This theme is free version from Kit Material Theme Note: Element not same with kit Need integration, customization or rebuild theme? please don't hesitate to contact us hendra@jawanet.com Or Submit Ticket

In an ideal world, it would be great if everything was open and audited with our seal of approval. Because Blesta is extensible, 3rd-party developers can create their own extensions. Those extensions are therefor their own intellectual property. So, they can choose to license it how they wish, encode it or not, have it audited or not, etc etc. If we were to put strict rules on 3rd-party extensions, it would result in fewer such extensions being available and still be no guarantee that the ones available, and audited, with our seal of approval could never be exploited. There is some risk with any software, so it's up to people to assess that risk and make decisions on what to use. I like the idea of an optional, paid "Certified by Blesta" process for extensions, because it's voluntary and ensures people that the code was reviewed by Blesta developers and meets our standards for security or code styling. This can add value to 3rd-party extensions by creating a level of trust with users, but there would be a cost associated and it wouldn't make sense for obscure or open source extensions. "Certified by Blesta" is not something we would require though, because it would have a negative impact on the availability of extensions. We want to make it as easy as possible for 3rd parties to create more extensions, not less.

"Deliver Invoices" and "Create Invoices" are different. The Create Invoices task actually generates the invoice, via recurring services or recurring invoices. Deliver Invoices actually sends it, as is the one that runs every 5 minutes. Create Invoices runs once per day. I hope that makes sense and glad that it seems to be working for you now!

RESOLVED Awesome. Looks like RE-issuing the license via my Account resolved ALL my issues : Dashboard --> Services --> Manage --> Manage License --> Reissue License --> Update License Status Such as with the URL looping in the browser. Thanks.

Tanks naja, added now

Ok yeah, something seems to be stuck because "deliver invoices" is set to every 5 minutes. I just deleted both of these and recreated them, just confirmed the cron sent them. Not sure what happened but we are good now! I will keep an eye on them moving forward.

nice theme . don't forget to add it to the marketplace .

The option to configure within the gateway settings would be nice. If I had my choice, I would simply put 'Credit Card' or list out 'Visa, MC, etc' or have 'Paypal' instead of the actual Paypal version. I think a majority of people could care less which gateway is being used as long as they know it's 'credit cards' or 'Bitcoin' or 'Paypal'.

I think the client double clicked the submit button. The first one went through with approval and then they clicked 2 more times getting the message 'A valid amount is required' My guess is that CORE-2250 will take care of it.

Blesta version 4.0.0-b3 (BETA 3) is now available. You can download it from right here (Client Area Login Required). If you haven't seen the blog post announcement for 4.0.0 BETA 1, you can read it here. This is a BETA release. Beta releases are not considered stable enough for production use, and are UNSUPPORTED. DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. Please report any bugs you find in the v4 beta bug forum. Installing Blesta See Installing Blesta in the User Manual for instructions. Upgrading Blesta See Upgrading Blesta in the User Manual for instructions. Release Notes See Blesta Core - Version 4.0.0-b1-b3. SEE BETA3 ONLY For older releases see all Change Logs. What to Test! 1. Test everything! Version 4 is a major release. This release primarily fixes an issue with Package creation.

Yes, thanks for the update. I'm not sure I understand the OPs issue with services, that sounds unusual and we would need more details to be able to replicate that. Upgrading from 3.x to 4.0 should work pretty much exactly the same as before.. but yeah, don't forget to run ~/admin/upgrade, there's some important database changes in there.