Leaderboard

Hello, We are currently developing a tcadmin module. Of course it's going slow but we plan on having a full working version out soon. We are still debating on if we will offer this module for free or for a very small monthly licensing fee. Don't pay attention to the horrible logo job. We'll update as we keep moving forward on this project.

...haha bet your thinking what the hell is automatic tickets? I mean something like this... Blesta is smart, and powerful, so why not have a cool feature... 1 staff is online: - Tickets don't get allocated to a staff member, they just show up as they do now. 2+ staff are online: - Tickets get automatically assigned per staff member equally in order they came in. (Blue highlighted per staff). Staff logs out: - Their tickets get automatically re-assigned if a staff member has a free slot, the rest get re-assigned to the normal procedure (Removes back to Not Assigned). --------------------- Settings (Staff section): [ ] Enter number of tickets to assign to. For example: [0] - Michael (0 = Unlimited) [5] - Callum (Callum only gets 5 tickets to deal with at a time). [10] - Holly (Holly only gets 10 tickets to deal with at a time). Thought I'd share this idea.

I talked to Dan Ushman earlier this year and they would very much like for us to build a module for integration with Tandem. We just haven't got enough requests for it yet to dig into it too much. So, definitely something we'd like to do, but we have some other things to finish up on first.

You can show the previous due, for example, in the "Invoice Delivery (Unpaid)" template: e.g. {% for invoice in invoices %} Invoice #: {invoice.id_code} Previous amount due: {invoice.previous_due | currency_format "USD"} Amount due on this invoice: {invoice.due | currency_format "USD"} {% endfor %} I'm not sure if you specifying the currency as a variable would work, but if so, it would be a better solution: {% for invoice in invoices %} Invoice #: {invoice.id_code} Previous amount due: {invoice.previous_due | currency_format invoice.currency} Amount due on this invoice: {invoice.due | currency_format invoice.currency} {% endfor %}

All our licenses use to be unbranded, and it actually caused more confusion. This is an area we have sort of "conformed" to, and it's actually interesting to see the split between branded and unbranded license sales. I think it's here to stay for the time being, and to be honest we could use the publicity for branded licenses.

I like it +1 Though, I think the unlimited should be changed to -1, as what if we have a staff member that we want to not respond to tickets?

Maybe if enough people request it!

We are aiming to allow customers to start, restart, stop their services through the billing panel. In additional we are also looking at allow console commands through the billing panel. Basically cutting out the tcadmin panel portion out of way so they won't feel the need to open two things. Although we will keep the panel around so people can still access it if they feel more accustom to using the tcadmin panel.

Hi, It would be great if you could maybe consider adding a basic internal knowledgebase so any admin/staff member can view for important internal information. It doesn't need to be all the features of the world but something where you can add a basic article or information piece for techs is great maybe also a basic ACL which prevents which admins/staff can edit, remove, add articles. Knowledge Is Power

I always like to hear about plugins coming together for Blesta, especially when developed by third parties. So I'm happy to hear you're working on something to integrate with Wordpress. I'm sure there are several people that would jump at the opportunity to use it.

I'll have to take another look at Singlehop. We use BurstNET and Limestone for our dedicated servers. BurstNET is cheaper unless you start to load up on configurable options, then it's usually Limestone. Reliability and support from both are outstanding. We used to use BurstNET for our VPSes when we were first starting out, but nowadays we run our own Xen nodes.

We need to get more done on the documentation, as well as the countless video tutorials that I'm planning to do. Maybe we can link those up somehow. In any case, anything that helps people learn how to use Blesta would be free.

There are lots of arguments I can make in favor of a wiki. At the core it boils down to this: If you want a traditional Q&A / FAQ KB, it is VERY easy to make a wiki behave like one. If you want a wiki, it is VERY difficult to make a traditional Q&A / FAQ KB behave like one. So the wiki gives the best of all worlds.

I would love this, and I think it really is the way to go...specially since either way I'm guessing the KB will be coded from scratch...might as well push forward with technology and create a wiki based platform . I'm pretty sure I posted a detailed explanation of why a wiki would be an awesome way to go during beta, but sadly I don't think that thread made it over to the live forums .

Re-uploading that module seemed to fix it, thanks for the hint!

I think it may work in Canada, would have to verify that though. We are going to implement Docsaway as another option, which has better international support as far as I know. We do have plans to add a delivery method fee that will allow you to cover costs for such delivery if you want to. I don't have an ETA on this yet.

Great. I think I might set up a simple wiki for now. Crude but effective. Speaking of, what are your thoughts on a wiki-driven KB? It would still have the same article structure as a regular KB, and it would be easy to set up category / list pages so that it behaved like a conventional KB, but I think the wiki format encourages more reading. Either way, as long as it hooks into the support system, I'm good.

The KB is moving up our priority list, and is tentatively scheduled for version 3.2. I don't have an ETA yet, but 3.1 is in active development and we are aiming for a beta release by the end of this month.. we'll see how it goes.

There is dummy code for each module method and some getting started with modules documentation. What other information would you like to see? It's always good to start from scratch, otherwise you'll need to go through the module later to remove extraneous functionality, views, language definitions, etc. that are specific to the other module you copied from, but not to your new one.

I'd actually recommend creating a plugin to do this. Your plugin can create a cron task, and you could have it evaluate if today is the 1st, and if so create your necessary invoices. Your plugin would interact with the API locally, from within the Blesta environment, so it would be more efficient than running a bunch of HTTP API requests. Wow... every time I explain how some part of the plugin system works I'm reminded just how incredibly awesome it is.