Paul

Alright, so I know that 3.1 isn't even officially released yet, and the guys are focused on that.. but I've been cranking on markup for 3.2. It's a work in progress, but I think it's coming along nicely, and I thought I'd share and get your feedback. Here's 3 screenshots.. they were taken on.. 1. Macbook Pro 2. iPad Mini Retina 3. iPhone 4s This is just the dashboard, which has the most going on, but pretty much all the client area pages have been created. Bootstrap 3. Tried to stick pretty closely to the current design with improvements wherever possible. So, what do you think?

lol, it's been in there a while, apparently. We need to get the client area conversion to bootstrap done first. Should allow for more flexibility with module management features, and result in a better Onapp implementation.

Thanks Steve! Merry Christmas!

Merry Christmas guys!

Interesting, anyone else experience this on step 2? What module are you using?

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..

What page/URL are you seeing this error? You can copy/paste the URL and just remove your domain

Hi Swerlo, v3 is a complete rewrite and shares no code in common with previous releases. As such, it is basically new software and it's only been out for 4 months. Regarding feature requests, as you know, we have to prioritize development based on demand. When people request features they are considered, accepted rejected or put on hold, prioritized, and implemented. The core of Blesta will never do everything for everyone -- it would become bloatware, so we have to be thoughtful about the features we implement. The extension system should cover most other cases. I happen to like your feature request, and I think it would be beneficial to the majority. Being that CORE-547 is a similar feature, this can be implemented as part of that task. I've added a note to the task so that fields may be selected for display as read-only within the client area. Thanks

Yeah, I noted that it should work in addition to maxmind, not one or the other.

There is already a task, CORE-547 to hide optional fields from the client area and order pages. It is tentatively scheduled for 3.2, but may be pushed back. I'm not sure if this is exactly what you're asking for though.. this would allow you to set, from optional fields, which ones not to display at all. Are you wanting the fields rather to be displayed only as read-only? Feature requests aren't always answered right away, sometimes we purposely let them run on to gauge support. As we plan future releases, we also revisit the feature request threads on the forums.

CORE-935, thanks for the suggestion! No ETA at the moment, but it's in our system.

That's right, a conversion of the client area and order forms is planned for 3.2. It's undetermined if this initial release will be responsive or not. It may be, or it may be in a subsequent release.

The plan is for a 3.1 beta starting at the end of this week. Betas are open to all direct customers.

Looks really nice! Email me at sales and we can discuss, and/or feel free to start a new thread about CraftSRV.

Some customers may have multiple accounts with the same contact details, so a customer number helps identify the correct one. I agree that people don't like to be thought of as a number.. people are people not numbers. So, the question becomes, how do we make the number available to the customer in case they need to reference it, in a way that is respectful?

Thanks for the feedback! The release date of the module really depends on the feedback we get here and any issues found. I would love to include in in 3.1, but if we need to build in additional functionality, as I suggested people may want, then it will not make it into 3.1.

Please note that the module currently requires all information during checkout, including the CSR. We'd like your feedback on this, and whether or not the SSL cert should be purchasable without providing this information. In which case, the customer would then login, manage the SSL cert and enter the details to finish the process.

Please note that the module currently requires all information during checkout, including the CSR. We'd like your feedback on this, and whether or not the SSL cert should be purchasable without providing this information. In which case, the customer would then login, manage the SSL cert and enter the details to finish the process.

Fixed, thanks. I bet you can guess where the outline for that page was copy/pasted from.

You can create a universal module product with just a product name and that's all. You'll then be able to create a package using this universal module product. If you want to ask the customer for information during checkout, then the screenshot at http://docs.blesta.com/display/user/Universal+Module for service options may help you. Documentation is still in progress, and it's being updated nearly every day, but we have more yet to do. Happy to answer any questions you may have, and there are others here willing to help as well!

It looks like the licensing is friendly, and to be honest I have been looking for an HTML5 VNC client we could use. CORE-924 Do you want the swap size set on the package level where the storage, ram, and other options are set? Some of these options, like the number of IP addresses may be best offered as configurable options so that you can charge more for them.

A gratuity plugin of sorts would probably be the best solution here, however we'd need to make some changes to allow plugins to get in the middle of the payment process. I think some more discussion is in order.

I suggest trying a different cPanel server entirely. The logs are pretty clear, Blesta is not receiving a response from your cPanel server. Maybe the other guys assume no response means success, I don't know.. but Blesta can't consider the account creation successful unless cPanel says it was. Was the username of the new account lbraziel? Are you using zamfoo? If so, I'd suggest removing that software ASAP, it's an abandoned project riddled with security vulnerabilities that could take down your entire cPanel server.. it may even be contributing to the issue here.

There's a task for it though, CORE-621

CORE-395 describes a ticket statistics section above the ticket queue under Support > Tickets. Average response time is one of the stats described for this area. I have added a note to this task to make all stats, including average response times available for embedding in other areas.