Leaderboard

Version 3.5.0-b4 is now available. You can download it in the Client Area. This is a BETA feature release. This release is not considered stable enough for production use. Please report any bugs in the 3.5 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 3.5.0-b4. For older releases see all Change Logs.

3rd has my vote.

i also prefer the third markup that mike posted

i prefer the third markup that mke has posted . still in love of v2.5

I'm not a fan of the client ID position: I think it would be better like this: Or what I use now which is like the admin area (I think 2.5 did this too not sure have to get my demo site back up to see). <h3 class="panel-title">Client #<?php echo $this->Html->_($client->id_code, true);?><!--<?php $this->_("ClientMain.myinfo.boxtitle_client");?>--></h3>

They are charged a partial month and a full term depending on your cutoff day.. so it will either be: Partial month + full year *OR* Partial month only, and it will renew for a full year You can tweak with your cutoff day and narrow that window if you want. Most people use prorata with monthly terms, so it's a little different when you have a yearly term. The goal of prorata is to get peoples services to renew on a specific day of the month and so the adjustment comes with their initial order.

yeah you charge for the remaining days and then start the year from the full month (1st)

Yeah mate, in the future if it's possible to exchange rate for say letting customers convert credit or config options would be neat.

Nothing new on this yet. Cody will need to decide what he wants to do about it.

I personally would expect it mate because when you are doing accounting you'll get confused, my client topped up money and found out he couldn't use it because it was GBP and not USD.

Yep third option is best.

3rd one anyway ideas when will 3.5 release? I'm in the midst of doing a makeover for client template.

Here we go mate a video on how it works now: http://screencast.com/t/Ed8QBE9m5Mp You'll notice I ordered in GBP, activated in GBP, the config order put it in USD, the preferred currency is GBP and my blesta is set-up for USD prices and allow customers to select their own currency and uses the Google exchange to change it. PS: my mobile number is my old one no longer mine. I think the fix is what you said above mate, there's no way for it exchange rate the currency so everything stays in USD.

my feedback is to creat a seperate page for every domain registrar that use logicbox , then ad a link to the logicbox module ... and replace the logibox logo with resellerclub , and add more logos like resell.biz , NetEarthOne ... ect , that way blesta win seo links for registrar with one module in the backoffice

I agree that the positioning of the client id could be improved. I think adding hr's around it will make it take up more space than is necessary though. Having it in the panel heading seems a little better, but I prefer to keep that saying "My Information". Adding it after "My Information" may take up too much space, we don't want that to wrap. I'm torn, not sure the best placement. Anyone have any other suggestions?

Yes, and not just for domain modules, but also for all other modules. It should not be the module's task to create an user interface, unless the module has special needs. With another billing software package, modules can just inherit a common class for that product type and specify which of the common fields they use: Much less duplication than requiring each module to have its own add_row/edit_row/manage views and a language file with pretty much the same strings. class MyModule extends HostingModule{ protected $description = "My module"; protected $serverFields = [ 'ip' => true, 'username' => true, 'password' => true, 'ssl' => false, 'status_url' => false, 'hostname' => false, 'maxaccounts' => false, 'hash' => false ]; [....]}

Yep I thought of that after posting this, but I don't think that's as bad as ending up with a 4-page invoice from a one-item pro-rata change. There's gotta be a middle-ground solution as I think we can all agree a 4-page invoice for one change is obnoxious.

nice +1 should be the default theme for blesta

Hey guys, Thought others might find this useful. I needed to have old configurable option values available in my POST requests from the universal module so after a bit of digging a pretty simple edit to app/models/services.php takes care of this nicely. Unfortunately it's a core edit, though hopefully this can make it into core officially *hint hint* // KNOWNHOST MOD RETURN OLD CONFIG OPTS foreach($service->options as $config_option){ if(isset($config_option->option_type) && $config_option->option_type == 'quantity'){ $vars['oldconfigoptions'][$config_option->option_name] = $config_option->qty; }else{ $vars['oldconfigoptions'][$config_option->option_name] = $config_option->option_value; } } // END KH MOD RETURN OLD CONFIG OPTS Insert this code around line ~1064 (right above $service_info = null;) of app/models/services.php I've only tested this a few times with different scenarios but it works perfectly in my environment. Enjoy

Carl said: I would like to see something better than passwords coming. ...but it's always a new "second factor" method. It never really change the problem : passwords. I think you missunderstood how it's work (since about more than one decade for 99% EU banks), by using a second factor, it's mean you have added a new layer of security to the user/password, as just after using that most common second factor, is you need to type a "moving key", so if your user/password couple is stolen (by viral software that know what websites you are connected with, what user/password you used), it's will be stopped to re-use it by the moving key they can not know as it's change every time. The "moving key" depending of method, can come by : - SMS OR - Email (better that SMS, because if you travel, depending of countries, you will not get your SMS) Or you have a little "digipass", it's like a micro-device that display new key every x mins but synchronized with the bank system or with, or other etc. Off course there are many other methods, but these above are some of the most common

Conditionals will be amazing to have!

I believe the goal is to keep it backwards compatible. Existing modules that are not updated to take advantage of features of the new plugin should work, they just won't make use of any plugin features.