PauloV

Statistics & Reports For Blesta
Stats is an advanced statistics gathering plugin,  it give the staff the ability to know about their clients, services, products ... ect, the plugin now display the fallowing data :
    Clients (Overview Data)
    Top Clients Due
    Top Clients Credit
    Top Clients By Income (Overall, This Year, This Month, This Week, Today)
    Top Clients By Services (Active, Suspended, Canceled, Pending)
    Top Clients by Country
    Services & Packages (Overview Data)
    Top Active Services (Overall, This Year, This Month, This Week, Today)
    Top Canceled Services (Overall, This Year, This Month, This Week, Today)
    Top Packages by Income (Overall, This Year, This Month, This Week, Today)
    Top Packages by Sold (Overall, This Year, This Month, This Week, Today)
    Packages Unordered (Packages never ordered by term)
    Packages Forgotten (12 Month, 9 Month, 8 ,7,6,..... 1 Month) package that was not ordered for a while .
    Transactions (Overview Data)
    Top Revenue by Gateway
    Top Revenue by Payment Types
    Revenue by Months
    Revenue by Years
    Revenue by Days
    Revenue by Periods
TODO :
Add transaction Reports
Add Graphs
Send Daily, Weekly, Monthly Reports to Email .
 
this  plugin requiere a the Pro (Silver) subscription .
Order Link
Plugin page
 
 

I have been using Blesta for many years (I've been storing up my feature requests for years too - sorry!) and I know that this topic comes up from time to time, however, I would like to give what I believe is a strong case as to why it should be allowed to delete clients.
Firstly, I realise that it is not possible to delete clients if they have an invoice or service attached and I believe that the reason for this is for accounting purposes in particular geographic locations (one of them being the UK it would seem). 
However, in the UK we also need to comply with Data Protection laws. This says that we must not retain personal data for longer than necessary. See here:
https://ico.org.uk/for-organisations/guide-to-data-protection/principle-5-retention/
According to the above page, we are allowed to retain the data if required for tax returns and this will not be considered to be retained for longer than necessary. So far so good...but according to my research, HMRC says that you only need to keep your business income records (including sales invoices) for 5 years after the submission of the tax return:
https://www.gov.uk/self-employed-records/how-long-to-keep-your-records
Therefore, my feeling is that UK businesses should be removing the client records after 5 years of them ceasing the relationship with the business, thereby complying with the data protection act that says that you must not retain personal data for longer than necessary. This is how I interpret the law and in my opinion this makes a much stronger argument for the necessity to be able to fully delete client records from Blesta.
Also submitted to: https://requests.blesta.com/topic/delete-client-for-data-protection-reasons (posted here for awareness)

ask blesta team to sponsor the extra features . they love such thing .

just to update everyone the lines have changed a bit in blesta v4.2
plugins/support_manager/models/support_manager_tickets.php
 
Add after Line 300:
where("support_tickets.status", "!=", "on_hold")->
 
Add after Line 1200:
'on_hold' => $this->_("SupportManagerTickets.status.on_hold"),
the rest is the same as above in op.

I just added this and wanted to share. I do not see any issues on our side and I did not do anything to modify the clients views. I looked at their view and it's acceptable as is for us.
 
Blesta Version: 3.6.1
 
Warning: BACKUP your files and database first!
 
If anyone has suggestions or sees something I did wrong, please let me know.
 
Files to modify:
 
plugins/support_manager/views/default/admin_tickets.pdt
 
Add after Line 7:
array('name'=>$this->("AdminTickets.index.category_on_hold", true) . " <span>(" . $this->Html->($status_count['on_hold'], true) . ")</span>", 'current'=>($this->Html->ifSet($status) == "on_hold" ? true : false), 'attributes'=>array('href'=>$this->base_uri . "plugin/support_manager/admin_tickets/index/on_hold/", 'class'=>"ajax")),
 
plugins/support_manager/language/en_us/support_manager_tickets.php
 
Add after Line 51:
$lang['SupportManagerTickets.status.on_hold'] = "On Hold";
 
plugins/support_manager/language/en_us/admin_tickets.php
 
Add after Line 27:
$lang['AdminTickets.index.category_on_hold'] = "On Hold";
 
plugins/support_manager/models/support_manager_tickets.php
 
Add after Line 266:
where("support_tickets.status", "!=", "on_hold")->
 
Add after Line 1029:
'on_hold' => $this->_("SupportManagerTickets.status.on_hold"),
 
plugins/support_manager/controllers/admin_tickets.php (adds the status count)
 
Add after Line 90:
'on_hold' => $this->SupportManagerTickets->getStatusCount("on_hold", $this->staff_id),
 
Add after Line 149:
'on_hold' => $this->SupportManagerTickets->getStatusCount("on_hold", $this->staff_id, $client->id),
 
In your database, go to the support_tickets table and under structure, add the following to the Status column: 'on_hold' (I added it right before 'closed')

Hello,
There is a simple fix that I have added to Support Manager Pro in my latest update 
Its because the CSS Position: fixed, has to be changed into Position: absolute
The problem is the position of the box that will Drop to the end of the page but will always be visible in all browsers
Hope that helps
 

Hello,
There is a simple fix that I have added to Support Manager Pro in my latest update 
Its because the CSS Position: fixed, has to be changed into Position: absolute
The problem is the position of the box that will Drop to the end of the page but will always be visible in all browsers
Hope that helps
 

Expanding on this at some point would be nice but I still personally think the domain manager is a bigger priority.

Thanks for the report, we'll take a look. CORE-2594

I just set up a fresh v4.2.0 install.
The MySQL database password contains the character "$" which was stored in config/blesta.php as "\$". This made sense in older versions as the config options were surrounded by double quotes in v3.6.?, but it appears they've been changed to single quotes which led to me banging my head for a minute trying to figure out why I was only getting blank pages.
 
<?php //... Configure::set('Blesta.database_info', [ //... 'pass' => '\$abc123', //... ] );  

Great job, good to see that you are still working!

of course, as you have the VIP subscription you can benifict from any beta test.
I hope we can finish it soon and release it.

Great Update

Hello blestars
Update finally here
Get it while is HOT! on first post!
Any bugs please tell me
Regards,
PV

The new version will include confirmation popovers on all irreversible action buttons, such as the "Delete" button.
There is not yet available.

Check My admin tools plugin ; it has a feature to re activate a canceled service .

Hello blestars
Update finally here
Get it while is HOT! on first post!
Any bugs please tell me
Regards,
PV

TWO USEFUL TIPS:
1) - If you STILL see a two (2) Support Ticket widgets on the client dashboard you probably have the "User Manager Add-Ons" plugin installed and need to "disable" it.
===============

2) - If you want to dynamically connect your Admin Dashboard to read and display and URL link the ticket counter for the "Support Manager PRO" plugin...

-  You will need to open plugins/system_overview/controllers/admin_main.php

-  Change...
                    
                   
$this->uses(['SupportManager.SupportManagerTickets']); $value = $this->SupportManagerTickets->getListCount('open'); $url = $this->base_uri . 'plugin/support_manager/admin_tickets/'; $icon = 'fa-ticket'; break; - To...
 
//The 3 lines of codes below allows the admin to see how many tickets are open and also gives a link to the Admin ticket page. $this->uses(['SupportManagerpro.SupportManagerproTickets']); $value = $this->SupportManagerproTickets->getListCount('open') $url = $this->base_uri . 'plugin/support_managerpro/admin_tickets/'; $icon = 'fa-ticket'; break;  
 

*** RESOLVED ( I believe )***

I believe this is a JS issue.
And I believe I found the solution from within the  forum
==================
Please see...
https://www.blesta.com/forums/index.php?/topic/2001-plugin-support-manager-pro-tickets-delete-merge-spam-multiple-tickets/&do=findComment&comment=41487
==================

To fix it just open the file /plugins/support_managerpro/support_managerpro_plugin.php
 
Find on line 1233:
if ($params['portal'] == "client") Replace with:
if ($params['portal'] == "client" && $this->client)  
=================

So far everything is working fine using your NEW version on PHP 7.0

Thanks.
You might consider adding this to YOUR version of "Support Manager PRO" .

Excellent plugin a great contribution

People keep PM'ing me for download link for verison that works 5.6 and 7.0, so i am updating here to give download link, You can download here.
I have made no other changes to this code than whats quoted in this thread by me and anothers, I DO NOT own this code, I DO NOT provide support for this plugin. 

Here's the fix for the issues I've seen posted here so far, and have experienced personally.  This runs just fine on PHP 5.x and 7.x, and Blesta 4.0.  This requires some DB modifications and file changes so if you don't feel comfortable doing that you can either reach out to me for assistance or post here.
The below is from a fresh install of the plugin.  YMMV but I hope this at least helps bridge the gap between those who can and can't upgrade Blesta over a plugin.
* When creating ticket, says ticket was created but no ticket actually shows
* No tickets also show in admin panel
* No ticket # is generated
ERROR: ERROR 1364 (HY000): Field 'name' doesn't have a default value
The same error occurred for the other 3 columns as well.
CAUSE: The INSERT SQL is not using these columns, but they are marked as NOT NULL in the db, which is blocking the SQL from executing successfully.
FIX:
alter table support_ticketspro modify name varchar(255) null; alter table support_ticketspro modify reading varchar(255) null; alter table support_ticketspro modify readed varchar(255) null; alter table support_ticketspro modify cfields varchar(255) null; * Badge not rendering
CAUSE: On the initial load of pages with the tab, there's validation to ensure that the user is a client or staff, where as the $this->{type} property does not exist.  Which is causing PHP to throw an error.  An alternative fix is to have property_exists($this, {type}) before the $this->{type} but seeing as how everyone is wanting to move to 4.x I decided to ignore that solution.
FIX: Edit file support_managerpro_plugin.php
Line 1209: remove "&& $this->staff" (property does not exist anymore on class)
Line 1233: remove "&& $this->client" (property does not exist anymore on class)
* Enabling this causes extra padding at top of page due to jQuery to get the ticket count due to response being full HTML page instead of expected single line, so instead of just rendering the badge data it's rendering a full HTML page

CAUSE: I'm not really sure what the cause is here.  It's basically an HTML page without any real content, but it was breaking the design.
But, since this was an Ajax call being made anyways I don't know why the original author just did not go this route to begin with.  The method has existed since Blesta 3.x
FIX: Edit file support_managerpro_plugin.php
Line 1218: change newRowCount.trim() to newRowCount.content.trim()
Line 1223: repeat change above
Line 1242: repeat change above
Line 1247: repeat change above
Edit file controllers/admin_tickets_count.php
At end of index() method add this: return $this->renderAjaxWidgetIfAsync(true);
Edit file controllers/client_tickets_count.php
At end of index() method add this: return $this->renderAjaxWidgetIfAsync(true);

Thanks Paulo V. 
Are there any screenshots of the new features ?
Or is there a changelog concerning the updates so that we can test those features within the plugin once released ?

I second that thought.
And thank you.

Take the time as you need to do it right! I prefer to wait rather than have a "buggy" version. Keep up the good work and continue to value quality over speed!