Leaderboard

It looks like the correct way to do this is to edit the plugins/order/views/templates/*/config.json and add a new template style. { "version": "1.1.0", "name": "AJAX Template Pack", "description": "AJAX order form template pack for the Order plugin.", "authors": [ { "name": "Phillips Data, Inc.", "url": "http://www.blesta.com" } ], "styles": { "slider": { "name": "AJAX Slider", "thumbnail": "images/thumb_slider.png", "screenshot": "images/full_slider.png" }, "boxes": { "name": "AJAX Boxes", "thumbnail": "images/thumb_boxes.png", "screenshot": "images/full_boxes.png" }, "my_custom_style": { "name": "My Custom Style", "thumbnail": "images/thumb_custom.png", "screenshot": "images/full_custom.png" } } } Then inside the .pdt files you can use <?php if ($order_form->template_style == "my_custom_style") { ?> <p>My custom HTML</p> <?php } ?> Here's the change you made as a vQmod. It's really easy to learn, best time to start is now custom_order_view.xml

Quick hack to remove the Tax ID/VATIN field from the client's "Edit My Information" page, registration page and ajax, standard and wizard templates. Use with vQmod See: http://dev.blesta.com/browse/CORE-547 http://www.blesta.com/forums/index.php?/topic/3258-add-option-to-disable-client-tax-id/ http://www.blesta.com/forums/index.php?/topic/476-ask-for-tax-id/ http://www.blesta.com/forums/index.php?/topic/1523-disallow-clients-to-edit-some-fields-from-the-client-area/ Version 1.1.0 remove_client_tax_id.xml

VestaCP released a new feature voting system and the Blesta module lost all it's votes from the old bugtracker. You all might want to vote on the feature. New link is here: https://bugs.vestacp.com/responses/support-for-blesta-billing I'm not going to be using VestaCP, but I think it would be good for Blesta to be integrated with it.

This Need a custom plugin

I voted

Would personally just use a single field with the most common configurations. "2x250 GB RAID 1" "2x500 GB RAID 1" "2x750 GB RAID 1" "3x250 GB RAID 5" "3x500 GB RAID 5" "3x750 GB RAID 5"

Yes its very confusing. Plese try this: 1- You have to first activate "Orders Widget" in Billing->Overview, and click on the left in "Manage Widgets" then activate the "Order" (by default the widget is not activated) 2- Now you will see all pending orders, you Have first to "acept" the order before anything helse. Hope that helps Also I thinks this will be optimised on Blesta 3.3-b2

That's pretty necessary! When I found that problem I just did it the hard way (deleting lines and stuff). Thanks for your contribution

Thing is I just search and randomly try 3 scaners from first page from google search results and all shows site "clean" status for blesta.com ,seems OP is look hard for site which will show hacked/infected state (only because they are not whitelisted hivelogic e-mail encrypter/decoder). And main question is why woud some one bored to scan blesta.com in first place which is handled by WP not Blesta?Just to say one thing,at any other competitors forum/blog topic(and user who post it) like this woudn't last even one minute,they delete topics/post and ban users even for postive reviews....damn this just show how profesional and open these guys are.

Tyson responded while I was typing, so just to add to what he said -- We carefully consider every core feature, if it doesn't make sense to be part of the core then it's implemented as an extension. Take a look at the Order System and the Support Manager. Both very well used, often necessary major features.. but we understand that other developers may create something that people prefer to use instead. Some future features -- KB, Mass Mailer, Affiliate System.. all of these will be plugins. (The KB will actually be part of the Support Manager plugin) Some features just make sense to be part of the core and forcing them to be extensions when they shouldn't be would fragment the system and de-stabilize the most basic function of Blesta. I ask the following questions when considering a new feature - 1. How widely used will the feature be? 2. How likely is it 3rd party developers will want to roll their own? 3. How basic to billing and client management is the feature, regardless of how many people will use it? Not that we go through a checklist, but this should give you an insight into our thought process. It's usually very apparent to us when something should be part of the core or not.

The OP's approach is more or less what we're already working toward. This is the reason we have extensions. For instance, the Order plugin is not apart of the core, although we currently ship it with Blesta by default. Likewise, gateways and modules are not apart of the core either. However, there is still going to be a need for core features to some degree. Currently, there are several still pending, such as the ability to merge clients. Many other features, like a mass mailer, are better suited as plugins. We still need to expand on the event system in Blesta to allow for extensions to perform more actions. There's always going to be some users that need custom feature X, or want feature Y to be changed slightly to work better for their business. But we don't intend to add or change core features that only 1% of users will use. Plugins are better suited in those cases. In the future, you will probably see a decrease in core features, and an increase in extensions.

I don't really think this is something that we have to worry about. The Blesta team knows that they want to keep things simple and smooth. The UI Designer (Paul) prefers the less = more approach. So if they feel a feature request would add more bloat than it would be worth, I am confident that they will turn it into an optional plugin rather than a core feature. However, you also have to realize that Blesta is a billing system...and adding onto those features is going to happen and not neccesarily be added as plugins. The example you gave is a good example I think, the ability to delete a service that has been suspended for 90 days would be a main feature and directly related to the billing system...I'd see no reason at all to have that it it's own plugin, especially when all it would need is a setting in the admin panel on whether to use it or not. Blesta 3.0 is only a year old, and is not feature complete yet so I'm sure there is still plenty more "basic" features to add before we start getting into bloating the interface in my opinion.

I'm talking about expanding that concept. After the billing plugin is installed more features can be added or taken away. IOW make Blesta run more like Joomla, or Wordpress. It is remarkable how each Wordpress or Joomla site can be made different with the use of seperate plugins that are easily turned on and off, or deleted and added. Blesta is already superior, but could be made more-so with the use if individual feature plugins. Some of them can be commerical, some for free. They can be community supported or Blesta sponsored.

Please note that the AppController.structure event has been updated to use arrays instead of strings for head, body_start, body_end in 3.3.0-b2. This is a backwards incompatible change (with 3.3.0-b1). Please be prepared to update your plugins if your plugins use the AppController.structure event. See CORE-1421 for more info.

It use to display it in the field, but we changed this because passwords should be in password fields. However, it's a 2 step fix the 2nd step is to design a modal popup that allows you to see the password and possibly alter how it's generated. (length, characters, etc). We just haven't got to the 2nd step yet, so this feature at the moment is admittedly less useful.

I see. What is it's current function? Since neither the client or the admin have any way of knowing what the password is. Is it just a place holder until they do a password reset?

The way it works is intended. Previously, it was a plain text field along with some other fields in Blesta, but those needed to by made into password-type fields. We plan to come back to this to improve how passwords are generated such that you would have an option to view the generated password.