Leaderboard

Blesta Warning System By CubeData This will serve as the placeholder for the Blesta Warning System by CubeData that is coming soon! it was suggested by @LicenseCart or Michael Dance and will feature a automated system that will issue "warning points" to accounts that don't pay there bills, have too many overdue invoices etc which will be configurable in the plugin's settings also this plugin will also automatically mark accounts that have too many warning points that you can set the threshold in the plugin's settings as well as to how many warning points are the max allowed and if a client reaches this max warning points or goes over it there account will be automatically switched to inactive preventing login and also serving as a sort of "ban system" to make sure they don't even try to order something else which they wouldn't pay for also. These warning points will also be editable in each individual client's accounts and this system will run as a cron job. This warning system plugin is sure to make everyone know that you mean business and if you don't pay up you will wish you did lol. as if you really want to make sure clients comply and pay for what they owe or bought display an optional "notice" on your homepage which would be a image showing the plugin is installed on your blesta and that you mean business hey if you want to scare your clients into complying go ahead lol(although like I said this will not be on by default and you would have to explicitly turn it on to show in the portal plugin or in blestacms if you have that from michael dance which would require manual code entry on both but it should work.) as it will be a image drawn by php that states the warning system plugin is installed and is enforcing and how many warning points you are allowed to get before you get the "can" lol. More will come later but this is just a placeholder for now for the new plugin CubeData is developing.

from my point of view , making notes as reply is a logical error . notes != reply . if you remember , i have notified about a problem in notes for multi-languages , notes should be moved to a separate table . that is just my opinion . but i think is not impossible to find a condition that will check last reply that is not the note . regarding my first request , i believe the status is soo helpfully , specially when you have a average of list of 20 or 30 ticket opens . Awaiting Client Reply (automatically set after a staff member responds) Awaiting Staff Reply (automatically set after a client responds to a ticket)

when a client open a tiket , and a staff make a response , the status is open . when a client open a tiket , and a staff make a response, client make a response , the status is open . is better to add new status , waiting staff response .. that way the client know the ticket waiting other's response, the actual scenario , the client should always enter the ticket to see there is a new update .

1. Not sure exactly what you mean. The nav link is click-activated, so that it will still work on mobile devices. But, once activated, you can hover over other primary nav items and the menu moves with you. 2. The breadcrumbs were actually the subnav links. They have been moved to the menu. This is actually one of the complaints we got (a lot of actually) that the subnav looked like a breadcrumb.

Yep, ours was an April fools joke.. looking forward to the *real* thing you're working on though.

Sounds interesting! Sort of reminds me of the Parallel Payment Optimizer - http://www.blesta.com/2014/03/31/parallel-payment-optimizer-video-free-plugin/

LOL nice one! Did they send you an SMS back upset after they went to the supermarket and did not get the discount? Reminds me of Czech Dream, a heavily advertised new store with amazing prices that turned out to be totally fake.

The behavior of checking that option is also described in the docs. The service will not renew, and therefore will not generate an invoice for its renewal.

Blesta v3 is much different than v2 due to the complete rewrite and redesign, so it's to be expected that some details would function differently because of the updates. I looked at Blesta v2 to check how it unsuspends services, and I see that it simply fetches all suspended services in the system excluding those assigned to an invoice that is past due. The problem with doing this in Blesta v3 is that a service and any of its options can be set on an invoice at any time, and paying any one of those invoices could potentially cause the service to be unsuspended, which is not ideal. The system would have to check that all invoices associated with the service are either paid or not past due. This would be a very slow operation, and there are a lot of different things to consider as well since Blesta v3 does so much more with invoices and services than it did in v2.

Thanks for the recommendations - Ken is AWESOME.

Hi Folks, I just wanted to share my integration with everyone, I'm more of a server guy (design is not my strong point), so please, go easy on me! This was my first time integrating a billing client and I've been using it like this for a while. I've also integrated a WordPress blog and the rest of the theme started off as HTML but I've recently converted it to PHP for easier management of the multiple HTML pages! Any feedback would be great, I've managed to test it on FireFox, Safari and Chrome on both my MacBook and IPhone 6 as well as on a Windows 10 laptop with no issues, if you have any let me know!

Mike, we are not talking about open or closed . awaiting reply is also open, on hold is also open . open is also open . but we talk about a more descriptive status , if you log as a client , the ticket is open , can you know the ticket is replied by staff or not ? you can't ... what we need here is simplifying the life for both staff or client . note this status was exist in v2

If the service has not been suspended, adjust the invoice due date. If the service has been suspended, adjust the invoice due date and unsuspend the service. The staff that (un)suspended a service is logged in the `log_services` table in the database. It is not shown in the interface. However, you can always write a custom report to export them if you want.

If a service is already suspended because of an unpaid invoice, changing the invoice due date will not affect the service status. The service will only be unsuspended via cron if it has been paid and if it was previously suspended by cron. In your case, the service should be unsuspended manually.

yes it is a edit of the standard one shipped with Blesta.