Leaderboard

We appreciate the feedback, thanks guys! I think this is the link for the shirts http://160693.spreadshirt.com/

That looks pretty cool. Cody and I were actually discussing the possibility of supporting file based HTML email templates in the future. This would add a drop down on the email template page that would let you select a pre-made email template. The template would contain the header and footer, and then anything you enter into the WYSIWYG editor would appear in the content section. While HTML can be used in the templates now, through the editor, this would simplify things dramatically when supporting rich designs, give people that flexibility, and allow a market to open up for email template designs.

They charge 3.40% and 20p fee on GBP Payments and 2.90% and 30c on USD payments. I have a PayPal calculator app on my android But yeah they are high if you charge 10p you get nothing, if you charge 20p you get nothing.

The imported services won't have the customer-id that logicboxes requires in order to pull domain info. So that's explains why that's not in there. I'm pretty sure we have a task for adding the ability to specify the customer-id in the edit service page to allow services that have already been provisioned outside of Blesta v3 to be properly linked through logicboxes. Check your module log to see why you receive this error. That's the first major step in determining whether this is an issue with your logicboxes (et. al.) account or with the module itself.

It's there right now. I'll setup cron and run it to see if that changes anything.

Thanks for the confirmation Paul, and thanks for making it so easy to add input and ideas to make Blesta even more awesome!

Haha I bought it from the Blesta store Paul gave a link to.

Not one by default with Blesta at the moment however ModulesGarden are building one: http://www.blesta.com/forums/index.php?/topic/826-cpanel-extended-for-blesta/

CORE-708. Admin configurable time frame, and notice to the client that replying to the ticket will re-open it, and that they should open a new ticket if it's unrelated.

Please open a ticket so we can confirm the license is valid and eligible for transfer. We don't recommend anyone purchase unconfirmed licenses.

No, the calendar is not very helpful. Their calendar doesn't have the ability to auto-populate events (create a "3-day customer followup with user ____" entry 3 days after service is activated, etc) so I've never touched it.

You can modify the language used for these actions, and add "\n" at the end of the "The <action> completed successfully." definitions.

It's not possible to pipe email from Google Apps to anything, you'll need to use the POP or IMAP method to fetch messages every 5 minutes.

just add it to jira ...

CORE-596, it's still pending.

We are planning to add the ability to update directly from within Blesta. There will be options for stable release, or beta. It's not a super high priority right now, because there are other features more heavily requested. It's also not something we want to screw up.

Just attempting to populate some data into their system, we found a lot of weird bugs. I think there was one where you can add events to the calendar, but they don't appear on the calendar. Are you experiencing that one too? We checked the database and they were in there, so we know how to import them at least -- and they should then appear on the Blesta calendar.

Yeah Paul was talking about making them like this: <img src="//gravatar.com/avatar/<?php echo md5(strtolower(trim($this->Html->_($reply->email, true))));?>?s=120" />

It would be nice if when emailing a client we had the option to select a template to send the client. This came in handy when using our old billing system.

We've asked for this before mate, and they said they are going to loads of updates together for the support module, if you remember the Beta suggestions.

Maybe a option soon to add sensitive information in tickets, which doesn't show up on the tickets except the admin side. So if I was making a technical department I'd have a box saying "Sensitive Information". And I was looking for support with my server, I was asked to put the Port and password in the sensitive information part. So I did that, and the technical team can click a button to see this information, and after they have solved the issue they can click a button to remove it. That way it stays confidential. The sensitive information boxes can be added on any department by a ticket box and also by adding the fields required. All sensitive information is encrypted in the database. Fields example: 1. - Label: SSH Port - Name: SSH_Port - Type: Text 2. - Label: SSH Password - Name: SSH_Password - Type: Password Then they will be optional on support tickets.

If a ticket is closed, what purpose does that status serve if the ticket can still be replied to? I can see having a Re-open Ticket option available X days after a ticket is closed, and which may be extended to replies being emailed in, but otherwise, I think the Closed status needs to be used as the ticket end-state.

For this year or the last 6 months . Make it as setting to change it would be very perfect .

we've got the Blesta addiction