interfasys

It's in 3.1 beta1

I guess it depends on how you communicate in your tickets. If you don't even put your name or are on a first name basis with your service provider, then it doesn't really matter, but if you fill in tickets like letters you write to the support department, you may sign the ticket like a letter and provide additional information like company name, phone number, OS, etc.

I'm getting tired of pasting my signature when I use ticketing systems of various companies and I imagine my clients are too, so I think it could be useful to let them have a permanent signature. Just like staff can provide useful information in there, so can clients, if they wish to. What does the community think?

Thanks for testing I'll check the web server's restrictions regarding symlinks. I think there is a nofollow somewhere...

And my uploads folder is outside of my docroot.

Indeed, I only pasted the end of the path Uploads /home/dom.com/uploads GeoIP Path /home/dom.com/uploads/system/GeoLiteCity.dat The upload folder is reachable since I was able to upload a logo there.

Permissions are exactly the same, but I'm not sure what is going on as Blesta just says "not found" and doesn't log anything anywhere.

I'm not able to add a domain to a client at the moment, logicbox gives me a {"status":"ERROR","message":"An unexpected error has occurred"} even though, I asked the console not to provision the domain. But from what I understand from your reply, whois management is performed after registration. What I'd like to see at registration time are dropdowns Registrant: [customer, custom1, etc., new contact] Admin contact: [default admin, customer, custom1, etc., new contact] Billing contact: [default admin, customer, custom1, etc., new contact] Tech contact: [default tech, customer, custom1, etc., new contact] That way a domain is properly configured right from the start, for people hosting with us and adding domain names. People who know what they're doing can pick a different existing contact or create a new one. I like what I'm hearing about phase 2 and I hope you'll consult with all of us when trying to put it all together. There is not a single billing platform which does it right, although AWBS was quite close last time I checked. It's not too much of an issue if people don't care about whois data and only use a single registrar for all their domain needs, but it's a headache otherwise.

Maybe I've missed something, but I'd like the default language for the client side to be set to French while still being able to manage everything in English on the admin side. If I set the default language to French, then I can't find a way to have the admin side in English while, theoretically, clients should be able to switch to English if they prefer to use that language via a language selector I can't see. Would it be possible to have a language switcher on the admin side? EDIT: Found the selector in the client zone, when the client edits his profile... Should really be a selector so that people who have not registered yet can read the site in the language of their choosing.

I'm with electric and I'm glad Blesta will publish a roadmap

In most cases, people who will register domain names with us will want us to manage them as well, which means that the admin and tech contacts will, most of the time, be the same and won't be the ones of the customer. So, how about letting us add those contacts in the module section so that they're being offered as standard admin and tech contacts at register/transfer time? That would be phase 1. Phase 2 would introduce a personal contacts database for domains so that a user could, at registration time, select a contact from a dropdown instead of having to type everything every time or accept to use his account details for every domain contact. Having such a database would make it very easy for customers to change their address on every domain they own. Every serious domain registrar offers a contacts database and it makes it so much easier to quickly and properly register domains.

Just did, I had forgotten

When creating a new package, if an error is made, the Module Options fields are reset. I had to switch module and back in order to have the options for my server module back. Create new package Select Directadmin module Select a server group Fill in the rest of the form Type "mucho" in Term, under pricing Hit "Create package" Expected result The form should keep all the fields as they were filled Result The Directadmin Package dropdown, in Module Options, is broken

I wasn't thinking of a specific environment, as anybody can install the libs in a centralised location for all apps to use, but FreeBSD, via ports, does put the main database in /usr/local and updates it via cron.

Instead of having to maintain yet another GeoIP installation, I symlinked the location given by Blesta to the already installed file. I get a green box when updating my settings, but Blesta still gives me an error message dom.com/uploads/system/GeoLiteCity.dat does not exist. My dir listing of uploads/system/ lrwxrwxr-x 1 cake4me cake4u 36B Dec 4 23:52 GeoLiteCity.dat -> /usr/local/wildwest/GeoIPCity.dat

Quite a few apps rely on GeoIP and it's not uncommon to have it installed in /usr/local for all apps to use. Since the control panel offers to turn it on, maybe it could also have a field where we could paste the path to GeoLiteCity.dat

Roadmap would be really useful

I might be able to help if nobody else can. I have a dormant setup which you could use in case you don't have access to a dev setup.

Looking forward to weekly patches

I would want to deduct from the amount of credits/minutes the customer has purchased. So this is what would show up in the invoice: -30m for "CMS one-click install", deducted from "180m support package". 150m remaining for future support requests. Thank you for your customs. Customers would know how much was used, what for and what's left.

So many refugees who don't need the DC or cloud modules will be happy to hear that.

Thank you.

I would vote that the client can re-open a ticket at any time, unless he can easily link to old tickets from within the "compose" window. Ticket history can be very important for some problems. In any case, it's very frustrating when you want to add to a ticket and you can't because it's been closed.

OK. I was just wondering if they had mentioned their release cycle during the beta phase.

I'm missing a good cctld registrar. Netim would be another one to consider, since they have very good support, but their prices are a bit higher.