Leaderboard

You can resend the welcome email from the admin panel by going to Clients -> Choose the Client -> Show All Actions (Left sidebar) -> View Mail Log -> Find and click the Welcome Mail -> Click "Resend" I would also like to see all of the featured the OP requested on the client end implemented.

Hopefully they'll see this. It's seems overly cumbersome to have to make multiple orders for an add-on item.

I agree. I hate always having to change the status of a ticket. It should automatically change to the most logical status and then we would have to override it if we wanted it to be something else, or, better yet, give us a settings panel to set it up how we want in case we want it to auto change, but just not to the status that blesta wants.

They've asked us to post one request per thread which is why I included the thread to the client side two-factor authentication.

Same here. I need to be able to add the customer-ID to have everything sync up. Any help on this would be appreciated! Scott

Ah the tags section show which are accepted. You can read more about this in the documents: http://docs.blesta.com/display/user/cPanel

Thanks for that alex. There should also be a way for clients to do it themselves

I think these features need to be added

Your "correct statement above" was not clear to me. Thats why I am verifying is its this {name_server}. I am assuming its that or do I put {% for name_server in module.name_servers %} Name server: {name_server} {% endfor %} like you said in your above post above

Did you set yourself up for emails? 1. Visit: /admin/settings/system/staff/editgroup/1/ check if Email BCC Notices section (tick all boxes). 2. Now go to: /admin/myinfo/notices/ Tick the boxes you wish to be alerted about.

Batch processing is a common technique when building scalable systems. It allows the system to scale with the needs instead of having a static overhead / demand ratio. In the case of provisioning it may have been fine to run the task when a service is paid for; I'm not quite sure why they used a cron for that. Maybe the developers can shed some light on that. But, in the case of downloading ticket emails it is clear why they used a cron, because there is no other trigger to tie the event to. For me it's less about whether these should be cron jobs at all and more about making sure the individual cron tasks are flexible enough to be run more frequently than 5 minutes.

+1 for this request

http://www.blesta.com/forums/index.php?/topic/819-client-two-factor-authentication/?hl=authentication

I am a little confused here as 5 minute wait on cron is standard in the industry. Some of the larger providers actually endup setting it to 15 minutes on allocation.

I also think account creation should be done every minute and not every five.

I did ask for a feature to be implemented that allowed you to add outgoings (eg server costs and license costs) to give a proper overall income/outgoings graph.

Agreed. Support tickets need to be polled much quicker.

I would definitely like to see forcing two-factor auth for staff as an option. I also look forward to making it an option for clients. I'd like it if clients were presented with the same forced two-factor screen during sign up but it had some explanation and an opt-out "Skip" link in case they don't want to do it. (But they should be able to configure it later if they like.) Maybe an option like "Present two-factor auth during client sign-up" could handle this.

We are aiming for 8-12 weeks (closer to 8 preferably) between minor releases, however since Blesta 3 is new there have been a lot of little things taking up our time out of the gates. So, 3.1 is likely to take a little longer than say 3.2 or 3.3, but we will make a beta version available as soon as we have something feature complete. We'll know more in terms of time frame in the next few weeks of when this will be.

The license module is used to generate licenses, and the license manager plugin serves as the license server. These will ship together. We have not yet made this available, but are planning to do so before long, and it will be a paid extension. Do you have a project you're looking to set up licensing for?

Ok now worked it out. Got the product I'd from the products area. )

I'm against this completely. If I update a ticket I want it going out immediately because I work in a mission critical environment where seconds count. As far as editing I'm going with Paul on this one... the email would be sent out via email so even if you edited the ticket that would be inconsistent. Unless an "Edit" email want out to them but then why not just update the ticket again with the correction. The ticketing system is nothing other an a fancy email client. I treat them like emails because you can't edit emails either. There's my input.

Package pricing ID values really have nothing to do with package IDs. Everytime a package is created one or more package pricing options are created as well. Package pricings are stored in the package_pricing table. Don't rely on package pricing IDs being functionally determined by package ID.