Leaderboard

we have talked about this subject so many times ago and we think is the time to talk about it now . i have made a plan to make something special for my need and provide it to the cmmunity , but i have stack with some limitation and some lock of professional advanced skill and lock of time . so what i have do , first i have decided to make the domain manager as a module , and add the registrar as a components inside the module . the registrar wil have a : - json file to identify the name ,description, version ect ... - folder for API class - module.php (that file has the fields that will be used in the addrow in module + the rules validation ) - manager.php (that file will have the available functions for this registrar ) - package.php (that file will include the fields that will be shown in the package creation ) - maybe we can add more files for other uses . in the module manager , we add registrar as a row (addrow) , in the add row , it list all the registrar exist in components folder as a list , when we select a registrar it load the returned fields in module.php . in the package creation , when we select domain manager , it list the available registrar , when selecting the chosed registrar it can load the required fields by package.php (optional ) . in the client/admin side , we will have a standard function like , name-server, contacts, dns, forwarding , emails ... ect ... the tabs has a relation with the actions available in the registrar or simply if not available show a message of unavailability . so the idea is simple clients/admins tabs --- communicate with the module , the module forward the call to the registrar module . the registrar module return the response , the module show the response (success or errors) . with this way we have a centralized domain management, and we can maintain 1 module rather than multiple modules .we can add the registrars as we want and we can improves them without touching the module it self . the logic is nearly the same used in the gateways , we laod the gateway class inside the gateway model .

is a bad news, but if mujahed need help in anything we are here . what i suggest is blesta staff negoce with mujahed to get the source code of their plugins, as others can fix/update the code if needed like the cpanel extended . but why is closing ? is the blesta market is not rentable anymore ? or there are some new road of business ? @sixwishlist , the real lesson here if for blesta team , no dev can support blesta for long term if they not change the target market . the HOSTING industry is the only market that can help blesta grow and grow , for so months ago we request blesta team to take care about hosting market like the domain management , the order form for hosting also . competitor has grow not by the core software , but the module/plugins they have by them or third party , another example is PauloV, it was so happy with the core code and has and still providing plugins/modules for free , like me , just to provide more option to the clients and encourage them switching/using blesta , now is less active , because the main feature he/and me and so others need it not exist after so many months , a better domain management and a good order form for hosting industry . i'm not against blesta , but blesta should learn what other say about them , and do what the people need (other can call it cloning functions from others , i call it add the defaults futures ) .

Hello everyone, I am so sorry for the bad news, Some people said that since they're not developers having the source code isn't useful for them. The original plan is to provide the source code to the license holders only so they can at least be able to improve them as they need, however, if there are many requests for open sourcing them so other developers can support it and improve it further, well, i have no problem with that.

Found a bug... If I add a client, and create a recurring invoice, then subscriptions do not work. Only one-time payment can be made. If I go through the hassle of making a module (what is that for, anyway?), then create a service, then add a client to the service, only then does it allow subscriptions. For a custom customer -- let's say somebody that hired you for 3 months of special coding -- you'd have to go through the nuisance of creating all this extra stuff. Furthermore, would it be visible on a front-end via the order form? It's supposed to be a "billing panel". At the base level, it should do at least that, and extra steps should not be needed.

you should edit the order conroller and add $this->requireLogin(); now only the logged in client will be able to view the order form content .

and also, clear blesta cache + clear internet browser cache

Yeah mate definitely will ignore. Moaning not only here but also many other threads. Cheers mate. Will keep you updated about more stuff

Yep that's a bug for recurring invoices, there's no left button. http://screencast.com/t/dfR4HN4UD6

We wish you the best with your new opportunity. If you are considering releasing your cPanel or other Blesta modules as open source, I think that'd be great. In fact, if you want to sign over the rights to us, we'll release it/them as free open source on Github, and consider implementing some of the extra management features into our native cPanel module.

The subscription option will only appear if all items on the invoice being paid are recurring, and recur on the same interval. What you experienced can happen if this is not the case, and the only option allowed for PayPal is "Subscription payments only". I'd recommend selecting "One time and subscription payments when possible", but I wonder if it might be possible to detect this in advance and not allow PayPal to be selected at all.

Any professional designer would have no issue implementing a really nice theme into Blesta. I guess the question is whether you are looking for something pre-built or something custom.

If you are cloning the gateway you need to rename everything in that folder including the folder itself.

I totally agree with this comment, blesta as billing and support platform for hosting providers need to focus more in develop tools that can be useful for us like having a robust cPanel module and a good domain management module at least. Not depending on third party modules or plugins that others developers offer for free will be a key point. Off course I really appreciate the hard work that others developers do and the time they spent to share with us their work but sometimes is not enough. We have to be aware that their contribution is free and depends of how much free time they have to work on that. I will be happy and I think most of the people will agree with me, that we prefer to pay a monthly fee to blesta knowing that they can provide us these tools that we need instead of breaking our head trying to figure out how to find a solution for our needs. I also think they will need to promote their platform with more developers around the world that want to code additional features for their system, because right now is very hard to find developers that knows the platform. I love blesta and I migrate from whmcs to them a couple of years ago, but having this lack of modules, plugin is not god. Sometime I hate to think that I have to go back to whmcs because blesta don't have at least the basic tools that a hosting providers need. Hoping they hear our petitions and try to work on that.

Yep. Read the drama here: https://en.wikipedia.org/wiki/Voat#History The OP's link now shows:

I've never liked OpenVZ. It has always handled RAM poorly, and is not really true VM isolation. Xen is better if you want templates.

Full time job so no time… but i'm hoping if LC picks up more and I can go limited, I can hire Mujahed for more money

Nevermind. "template", not theme. I left this in case somebody else makes the same dumb mistake. ___________ I copied the default bootstrap client theme. Inside "config.json", I added a few characters to the name. "name": "Bootstrap", is now "name": "123 Bootstrap", Zipped it up, uploaded it. The error is "Please enter a theme name. Please enter a valid 6-character hex code for each color." So what's wrong here?

Ignore him mate, he's moaning about thin air would like to see him do it.

Thanks guys!

1. Write a query to fetch client credit amounts. Credits are determined as transaction amounts received that have not been applied. 2. The system requires certain fields, like a last name. If you want to remove it, you can update the Clients model to ignore the rules. 3. Update the Emails model, send method, to fetch the client's phone number and set it as a tag in all email templates. Similarly, fetch the credits from the Transactions model, getCredits method. 4. Staff have access to companies and particular pages as defined in staff group permissions. You would have to add another layer of restriction to filter based on client groups and enforce that rule on all client pages.

Hi We run Blesta behind haproxy, with haproxy handling the SSL and setting X-Forwarded-For header. No issues. Hope this helps. -Barry

Languages follow the ISO standards for country and language codes, and are formatted in Blesta as ISO639-1_ISO3166-1, e.g. "en_us", "en_gb", "fr_fr", etc. Other languages translated by the community are available from the translator. There are several directories of language definitions in Blesta, including the core files, plugins, modules, gateways, components, helpers, etc. Creating them manually can be a pain. If you download one of the translations from the Translator you can get an idea of all of the directories and files involved. More info on translating Blesta is described in the documentation.