Leaderboard

Blesta: Janitor Small Blesta plugin to automate cleaning of abandoned orders, invoices, and services. Installation Download the latest release version from our releases and then simply upload the janitor folder to ~/plugins directory on your Blesta installation. How it Works: Janitor creates two cron entries which can be configured both by the cron settings and by the direct plugin settings. All of the plugin’s settings are based on the time the order was created. It may be important that you not cleanup and cancel at the same interval if you expect the orders to be marked as cancelled for any amount of time. Both cron tasks will never cleanup any orders or services which meeting the following criteria: The order’s invoice has any amount paid towards it. The order’s service is active or already cancelled. The order’s invoice is completely paid and is already closed (database: invoices.invoice_date_closed) Cron Task: Cancel Abandoned Orders This task is designed to strictly check for open orders which have never had any payments attached to them. First, the task will cancel the order and then next, it will void the invoice with a message as described in the language file. This cron task will also cancel any services attached to the order. This part of the cron intentionally leaves orders, invoices, and services in the database, in the possible event of this data being used by sales automation, etc. Cleanup Order Database This task is designed to completely delete all related database entries related to the order. It will remove the orders database entry, the order_services entry, and provides you the option to either leave the services as marked cancelled, or completely delete the service from the database via the plugins options. Only canceled services will be deleted if this option is set. If the service on this task is any other status than canceled, as set in the ‘Cancel Abandoned Orders’ cron task, it will ignore the service entirely. Download: https://github.com/nodecraft/janitor/releases Issues/feature requests: https://github.com/nodecraft/janitor/issues

Thanks guys. Looks like it was mod_security related, the host took care of it so things are working again. I feel as though I've had this issue in the past... thankfully this thread is here so I will find it the next time and remind myself of the solution.

Well done ... When i finish testing and tweaking my plugin and release it , maybe we can merge the two plugins .

Hello, I have to send now a very important email to my clients as i use multi company not so easy export emails from phpmyadmin. (impossible now) Is there any chance to be there this month the 4.0 Beta? I really interested about the mass mail plugin. Or there any chance to get this plugin earlier? I have to send the emails this month. Thanks Peter

We have no plans to allow clients to be members of multiple client groups. This would introduce ambiguity because client groups can have their own settings, which in turn might conflict.

Thanks, I've moved CORE-737 to the short term bucket. In the meantime, there is an option to block or force manual review of orders that use free email addresses with Maxmind.

Go to the profile page: Manage then change the client group. You can also set different client groups per order form so they are automatically put into that client group.

My plugin . Has the fallowing settings Days to clean uncomplete orders.( Number of days, list from 1 to 90 days) . Action for attached invoice (void/delete) Action for attached services (cancel/delete) . Delete = remove from database . We will implement a option to send email about uncompleted orders for x days (partially paid) . The plugin will be released next mounth with another 4 other plugins .

We are also investigating implementing a similar solution. Our design concept is to adhere to the following rules: Remove orders which have been fulfilled from the database, including attached meta data such as order_services. Assigned un-paid orders which are older than $x date (via config) to be "cancelled". Cancelled orders will have services cancelled and invoices voided. Delete "cancelled" orders from orders table older than $y date (via config), including attached meta data such as order_services Our goals are to remove the potential of database bloat as new orders are added, but not full-filled. Removing completed orders doesn't provide any additional value to companies as the order process is not transparent to staff. As far as we can tell the only value the order has is to stitch the invoices to a service to get the initial setup running and data retention afterwards is not relevant. We're just hoping to confirm that these facts are accurate so that we don't break any features by removing orders as they are completed or abandoned.

Check your error/access log of your webserver. It will tell you why it is giving a 403. It could very well be mod_security related. -Adam

403 error is maybe a modsecurity error

Sorry but your post above(not this one I quote,but previous ) is not constructive criticism...constructive criticism is when you post your opinion about blesta with valid facts without advertising their competition or post provocative comments....but unlike Mike I think that post should stay..maybe even bold it...it say more about you than about blesta or WHMCS. It is Ok to use WHMCS I use it once.....but I don't see why post such provocative comments...like you are angry . I mean it is not ex Wife..it just ex-billing script....to be honest your post above is like it was made by 10 year old kid .....I don't see any point ....you sound like angry bride ....