Leaderboard

Hey, I think it would be handy if user input was run past php trim() before being processed, at least for the search if not everywhere. I've been trying to think how this could cause a problem but for the last few days I've come up with nothing, just many more times I've been caught out by having a space at the start of a copy/paste into the search box. The search in the top right corner will not find what you are looking for if you copy/paste and catch a space, or tab at the start or end of your copy trim() would also be handy on domain input for the cPanel module, that one caught me a few times when adding a few services. In the end I added it to my import script to do it first, but got caught out on a few I had to put in manually. This is again a small thing and it's simple to find/remove the space at the start but still a valid feature request as I would have thought it should have already been in. No flaming for silly feature requests.... I understand that my feature requests are trivial and there are much better things for devs to spend time on, but the only way to better the product is to point out places that I feel could be improved on. Thanks.

Did you run /admin/upgrade after uploading 3.6.1? If not, do that. After that, go to Settings > Company > Plugins, and make sure no plugins have an upgrade waiting.

You should totally license the first theme (http://fotos.subefotos.com/b4154aba2434a8056339e76221db6df0o.png) would be highly interested in purchasing!

When you have a blesta setup with relatively high client volume, you may want to periodically check if everything is OK, or clean up things that should not be there (i.e: data that is not automatically removed by blesta/plugins). I've come up to this queries which I use periodically: - Show users that have at least 1 active service and more than 3 unpaid invoices: This may happen when a provision plugin is not suspending a service, or just human mistake (useful to find customers that are not paying because of not having their services suspended) SELECT many_invoices_customers.id 'customer_id', services.id_value 'service_id' from (SELECT i.client_id 'id', count(*) 'c' FROM invoices i, clients c WHERE c.id = i.client_id AND i.status != 'void' and i.paid != i.total GROUP BY i.client_id HAVING c > 3) many_invoices_customers, services WHERE services.client_id = many_invoices_customers.id AND services.status = 'active'; - Show users that have more than 3 unpaid invoices and at least 1 suspended service: let's you clean up users that don't pay anymore (and manually cancel them) SELECT many_invoices_customers.id 'customer_id', services.id_value 'service_id', many_invoices_customers.c 'invoices_number' from (SELECT i.client_id 'id', count(*) 'c' FROM invoices i, clients c WHERE c.id = i.client_id AND i.status != 'void' and i.paid != i.total GROUP BY i.client_id HAVING c > 3) many_invoices_customers, services WHERE services.client_id = many_invoices_customers.id AND services.status = 'suspended' ORDER BY many_invoices_customers.c DESC; I haven't implemented auto service cancel yet, but maybe is useful to someone here *Those queries are meant to be executed directly into your blesta MySQL DB.

These can also be added to Blesta as Custom Reports, which is super cool, and would even allow you to customize them across dates or status values, etc.

Hi, I literally spent weeks thinking the logging functionality was broken. When you are in the admin gui, and go to tools -> logs, I think it's really confusing(and a VERY easy fix). Here's an example -- if you look at "Modules" (assuming you have one, if not choose "Gateways" or something else). If you click on the anchor text for the "Name" of the log item(e.g. "Stripe in Gateways"), it takes you to the stripe management page(e.g. /admin/settings/company/gateways/manage/1/). I have literally clicked this hundreds of times trying to figure out where the logs actually were!!! By accident, I clicked in the blank space.. and there was a collapsible div with the log data. Simply adding a font awesome expander icon in the blank space would help(e.g. http://fortawesome.github.io/Font-Awesome/3.2.1/icon/expand/ or http://fortawesome.github.io/Font-Awesome/3.2.1/icon/expand-alt/ or http://fortawesome.github.io/Font-Awesome/3.2.1/icon/arrow-down/). Alternatively(I think this makes more sense), change the destination link for the anchor text to expand and show the logs, and add a (configure) link next to it that goes to the manage step. Just a suggestion -- this was extremely frustrating for me and I really thought it was a bad product and the logging wasn't functional.

Please see CORE-1935. Thank you for the suggestion, this has come up several times and adding an icon indicating that the row can be expanded is a simple fix to alleviate some frustration. User experience +1