Leaderboard

You're welcome to start one, now is a good time to start a conversation about the domain manager. The goal is to get 3.4 out pretty quickly, and focus on the domain manager for 3.5. A discussion about features and functionality would be good.

Out of curiosity, how do they compute their passwords?

yah, i've been working on an internal HB importer for myself on and off for the past few months and thats picking and choosing the parts I really need. had fun dealing with decoding the passwords too

If you are in the US, you might look at e-onlinedata. We're actually partnered with them, see http://e-onlinedata.com/blesta/ for details and costs.

Stripe is secure, safe and amazing.

I don't think any current gateway implementations can allow credit card reuse without storing the data yourself (tokenised storage). You should do some research into the PCI-DSS standard - if you transmit or store credit card data you will be required to fill out a PCI-DSS SAQ D form. Even if you are only redirecting to a third party like PayPal which accepts the credit card details you are still supposed to fill out an SAQ A-EP form but I think most gateways won't require that. Have a read of this document: https://www.pcisecuritystandards.org/documents/Understanding_SAQs_PCI_DSS_v3.pdf This is a good checklist with all the details of each requirement: https://www.pcisecuritystandards.org/documents/Prioritized_Approach_v3.xlsx

Ok guys -- I think this has received enough +1's, thanks! Please see CORE-1428

Module::arrayToModuleFields is intended to be a general helper method for converting an array to module fields for all field types. It's not intended to support the use of every parameter that could be passed to every other module field call, such as option_attributes for select fields. You may also notice that it does not support attributes for labels, or to allow label tags to be preserved. Likewise, multi-select fields are not supported. If you needed to set those specific fields or attributes, you could create those as individual ModuleFields separately and pass them in the second parameter to Module::arrayToModuleFields. Otherwise, you could write a specific helper method for your module to aid in module field construction. As I mentioned in my earlier post, the currently-selected value for a field should be set in the third parameter ($vars) passed into ModuleFields::arrayToModuleFields, and field attributes set via key "attributes" in $arr. e.g. // Fields $arr = array( 'country' => array( 'label' => Language::_("Webdrive.whois.Country", true), 'type' => "select", 'options' => array( 'NZ' => "New Zealand" ), 'attributes' => array( 'placeholder' => Language::_("Webdrive.whois.Country", true) ) ), ); // Selected values $vars = (object)array( 'country' => "NZ" ); $fields = $this->arrayToModuleFields($arr, null, $vars);

Using a Kanban board is one of the easiest way to manage issues. It gives you a clear overview of what's going on. Try this demo to see it in action http://demo.kanboard.net/?controller=user&action=login demo / demo123 It wouldn't need to be as compex in Blesta, here is a very basic WP comopnent http://wedevs.com/plugin/wp-project-manager/kanban-board/

We do have data traffic graphs that can be viewed by the customer in our (commercial) module. It doesn't actually bill the overage though. Be aware that combining ports is not that trivial when using the 95% billing method. You cannot pull already computed numbers out of a monitoring program, and add them up. If the monitoring program says port A did 10 mbit this month, and port B did 5 mbit, that does not mean you can bill 10+5 = 15 mbit. No, the data traffic on the ports could have peaks at different times, and the real figure is somewhere between 10 and 15 mbit... You would need to create a new graph combining all the individual data points from the RRD of port A and the RRD of port B, and use that to recalculate. Tends to be easier to create combined graphs when collecting the data, instead of doing it afterwards...