Paul

I thought I'd chime in on this even though it's closed. The restriction sounds like it was placed by Softaculous, whether or not they do this for anything else I don't know. However, if the subdomain you install Blesta under does not exist yet it is possible that your trial license would have to be re-issued. This is especially true if you access the install by IP or some other hostname/subdirectory and then later set up the subdomain. In your case I would suggest a manual install. It's pretty straight forward, and should take no more than 15 minutes. See https://docs.blesta.com/display/user/Installing+Blesta

I bumped this up in our backlog. If you don't see it in 4.0 beta 1, feel free to remind us and we may be able to sneak it in before final.

nice! looking good

Seems like a fair comparison It wouldn't be a Blesta vs WHMCS thread without a link to BillingBrawl though.

Currently all widgets are displayed on the dashboard. The idea is that you can set the sort order of the widgets (including plugin widgets), disable them, or have them appear on their own page instead. If they appear on their own page, the nav link would have the same name as the widget name. If it is assigned to its own page, the page would contain only that one widget.

I personally like the lighter (2nd mock) also, for what it's worth.

That's a good question -- I don't know. It is high on my personal priority list and the client area can benefit from some improvements.

Why not? See CORE-2119. Thank you for the suggestion!

Right, synchronization of expiration date. Is there anything beyond that that we may be overlooking? After the transfer, assuming the expiration date is in sync, Blesta will generate an invoice when it's time to renew for the price of the domain and any extras at that time.

Do you think "On Hold" is beneficial to have now, ahead of custom ticket statuses? We may consider adding this single status in advance of custom statuses since it's pretty simple to do.

Well said Mike, thanks for that. Support & updates for Blesta Owned Branded and Unbranded is $39/yr after the 1st year. It's not mandatory, you just won't be able to upgrade or get support if it's expired. There are no penalties if you don't renew, wait some time, and then renew it. Also, for a fun, and biased comparison of Blesta vs whmcs, check out www.billingbrawl.com

This is what we are planning to do regarding this: New options under Settings > Company > Look & Feel Show / hide / sort dashboard widgets Opt to move individual dashboard widgets to their own page. For example, transactions widget could be moved to a new nav element called "Transactions". This will allow staff to customize the look of the client area. Thoughts or questions?

I'm not familiar with this 3rd party module, but if it works similarly to the native module in terms of this, you are safe to remove them from the server group. Given it's a 3rd party module though, you should test this out.

A couple questions: If clients can upload documents, can they also see the documents they uploaded, or should they only be viewable to staff? Should this be a setting? I can imagine some may not want to allow clients to upload files.

Since this thread has turned into a shouting match, I'm going to close it. We appreciate all of the productive comments, and we take the requests of our customers seriously. As stated, v4.1 is designated for improving domain support. Please feel free to start a new thread if you have specific suggestions related to domains.

Name servers, whois information can be changed by the customer. DNS zone control with registrar's name servers are not yet supported but is planned. EPP request is available for at least some of the modules.

When you create an invoice there is a checkbox for Invoice Delivery that contains your delivery methods. Email is selected by default. If you save an invoice with this box checked, it will be delivered when the cron next runs. So, if you manually sent it, then this would explain why two were sent.

Something necessarily must have changed in order for it to stop working. Interesting. What I would try is this: Make sure you're running the latest version of Blesta 3.6.1 Re-upload the plugins/support_manager files, and make sure there is not a pending upgrade for the plugin under Settings > Company > Plugins Set up the forwarder for piping to be like the following: Make sure the path to PHP and the path to pipe.php is correct. There should be nothing after pipe.php. Double check that it is chmod +x (executable). EDIT: Also, make sure you have the mailparse pecl extension installed. If that doesn't work, then the next step would be to try to manually pipe a test email in via SSH to determine if it's an error with Blesta or an issue with the mail server not sending it to STDIN.

It may be beneficial to delete and re-create the pipe forwarder in cPanel. If the hashbang or permissions of the file are not correct or have changed, cPanel may automatically correct them or prompt you to correct them.

Certainly there is room for improvement. Specifics in terms of how the existing process can be tweaked to be improved is most helpful. Details are important. "This other form is better" as others have suggested in the past doesn't really help. I am curious to see what you come up with.

What version of Blesta and the support manager are you running? See https://docs.blesta.com/display/user/Support+Manager#SupportManager-email-pipingEmailPiping You should double check that the hashbang in your pipe file are correct. Also ensure that the company ID defined in your pipe file references the correct company. If you have only 1 company, then it should be 1. It should also be executable by exim. If you have SSH, a chmod +x pipe1.php should suffice. Any idea what changed?

When you're a big hosting company and have a pre-defined set of services you're offering, it's easy to streamline the order process to fit that small subset of services if you're building it yourself. When you build software that has to work with a very wide array of different services, you have to take a more generic approach. Really, the solution in most cases is to create new order forms that have a different, potentially more specific flow for what is offered. I think the most helpful thing to see would be some mockups of how you'd like things to work. If we have something clearly defined, then we have a basis from which to design new order forms.

If we update just the PayPal button graphic for the interim, which do you want to see? This one was recommended - http://www.blesta.com/forums/index.php?/topic/2938-clean-payment-buttons-for-paypal-paypal-subscriptions-etc/?p=35478 But we have to have 2 separate buttons, one for PayPal and one for PayPal Subscriptions.

What is the consensus of this thread? A generic button, or swapping out the PayPal image buttons with different image buttons? The generic button change, which Cody at least seems to be an advocate of here would be a change that affects all non-merchant payment gateways and would take a little longer to implement.

If you make the change and run it once (and then revert the change), it will probably accomplish what you're looking for. LOL naja7host