Ability To Override The System Information Tab In Modules

[Mickey]

I would like to have the ability to override the default system information tab in modules.  I have currently modified my version of Blesta to allow me to override it with a specific named tab.  It would be nice if this was a default feature in blesta so that I would not have to modify Blesta code when building modules.

[Cody]

We need more info on why that would be useful/beneficial to users for us to make a feature. Persuade us.

[Blesta Addons]

I would like to have the ability to override the default system information tab in modules.  I have currently modified my version of Blesta to allow me to override it with a specific named tab.  It would be nice if this was a default feature in blesta so that I would not have to modify Blesta code when building modules.

this has a relation with attaching modules to each others ?

[Mickey]

Right now the information ont he page is pretty basic.  I would like to have that page be more of an over view of their service, not just the renewal date & price etc..  Here is an example of a work-in-progress module I'm working on for proxmox.  It doesn't have all of the info I want on the page yet, and styling is still a bit rough, but you'll get the idea of the type of data I'd like to include.  Currently this is not possible without some way to override the main page, or inject data into the main page.

 

The way I went about it was name the tab overview & make a few mods to the client_services.php

$method = isset($this->get[1]) ? $this->get[1] : "overview";

and

$tabs = array();
if(!key_exists("overview", $client_tabs)) {
   $tabs [] = array(
      'name' => Language::_("ClientServices.manage.tab_service_info", true),
      'attributes' => array('href' => $this->base_uri . "services/manage/" . $service->id . "/", 'class' => "ajax"),
      'current' => empty($method)
   );
}

It's a fairly small thing, but it lets me make that a useful page.

[Mickey]

this has a relation with attaching modules to each others ?

 

No, I am currently re-writing the proxmox module to include a bunch of things it's missing (bandwidth limits for instance) & I would like to replace that tab with something with more useful info from the module itself.

[Mickey]

Another option for this would be to implement a new method on the module class that could be overriden & called to retreive data from the module that could be displayed on that tab.  Either way would work for my use case. 

[Blesta Addons]

Right now the information ont he page is pretty basic.  I would like to have that page be more of an over view of their service, not just the renewal date & price etc..  Here is an example of a work-in-progress module I'm working on for proxmox.  It doesn't have all of the info I want on the page yet, and styling is still a bit rough, but you'll get the idea of the type of data I'd like to include.  Currently this is not possible without some way to override the main page, or inject data into the main page.

 

The way I went about it was name the tab overview & make a few mods to the client_services.php

$method = isset($this->get[1]) ? $this->get[1] : "overview";

and

$tabs = array();
if(!key_exists("overview", $client_tabs)) {
   $tabs [] = array(
      'name' => Language::_("ClientServices.manage.tab_service_info", true),
      'attributes' => array('href' => $this->base_uri . "services/manage/" . $service->id . "/", 'class' => "ajax"),
      'current' => empty($method)
   );
}

It's a fairly small thing, but it lets me make that a useful page.

why not to add another tab and work with it ?

[sysc]

why not to add another tab and work with it ?

That's definitely one option, I see value in having more information in that initial tab. As it stands today, that tab is basically useless (in this case especially)

[Blesta Addons]

you can make a tip ;

clon the tab info into another tab , in the initial tab add a redirect (0 second) to second tab , so the client willbe directly to the second tab .

[Mickey]

I'll stick with modifying core files before I implement something hacky like that.

[Cody]

Obviously we don't think the overview tab is useless, or we wouldn't have spent time creating it. It does serve an important purpose.

That said, maybe allowing the module to display some overview info under the service overview section would make sense.

From a UX perspective, consistency is super important, so I'm very hesitant to allow modules to override the service overview.

[Blesta Addons]

so I'm very hesitant to allow modules to override the service overview.

is a good addition , so override/adding can make sense for all .

[Mickey]

Obviously we don't think the overview tab is useless, or we wouldn't have spent time creating it. It does serve an important purpose.

That said, maybe allowing the module to display some overview info under the service overview section would make sense.

From a UX perspective, consistency is super important, so I'm very hesitant to allow modules to override the service overview.

 

Then it would be nice to have a standard method on a module that was called, if defined, that could inject data into the page.  Either by rendering a template, or by returning a context object that could be used in the client template for that page.

[dado023]

i hope you guys will get done this proxmox thing, so Blesta will have one more extra feature

[Paul]

Has anyone mocked up an example of what they'd like this page to look like for a specific/custom module?

[Blesta Addons]

i prefer if you can devide the tab into 2 part , part for blesta and part for models . like the mickey exemple .