Leaderboard

Merry Christmas guys from everyone at CubicWebs, hope you have a great day tomorrow. Here's a laugh for you all, you will be in stitches.

Good catch. I think it should probably strip the signature from the reply if that is the only thing in the reply regardless of the status (thus no reply created).

At the moment in 3.1.0 b1, you can have a signature which auto adds to every reply, so when you close a ticket, if you don't clear the text box it thinks it's a message and sends the reply to the customer (Just a signature). I believe it would be nice for it to auto detect the signature or have a tick box which says if the signature should be added.

Just as long as my tickets keep importing (cPanel piping)

This is included in the support manager plugin. Instructions here.

Fixed in 3.0.7. CORE-907.

This is in 3.1. CORE-810.

Merry Christmas guys!

Ho ho ho Merry Christmas!!!

Merry christmas dear Michael

Added CORE-949. That line (line #40 in /plugins/order/views/templates/standard/main_summary.pdt), should be removed. $item['qty'] = $this->Html->safe($item['qty']);

Created CORE-948 to address the error. The solution is to either enable some payment types, or record the payment instead. The error affects all version (3.0.0 - 3.0.7).

thank you please next update short url all plugins Example : https://account.blesta.com/client/download I do not like this link : https://account.blesta.com/client/plugin/download_manager/client_main/

The configurable options feature is free, and included in Blesta 3.1 assuming you have support & updates (Everyone on v3 does until at least Aug 14, 2014). With configurable options however, you can charge your customers more for certain options. For example, if you're selling dedicated servers you can have a drop down for the number of IP addresses.. Extra IPs -None- 2 - $3 3 - $5 4 - $6 Etc..

Don't forget multi-company.

I've been kicking around the idea of a plugin to do that sort of thing.

Please post 1 feature request per thread, and include as much information about the feature as possible. Having 1 feature request per thread allows the thread to focus entirely on that feature. One of our goals is to gauge community interest in a particular feature, which helps us prioritize the feature if we decide to add it. If we do add the feature to our project management system, we will usually post a task ID associated with it. The feature can then be tracked in the thread to completion. Posting multiple feature requests in a single thread waters down the request, and it will usually receive fewer responses. So, sticking to 1 request per thread increases the odds of it being implemented!