I've seen your software mentioned on the HB forums and since I'm waiting anyday now for the HB implosion I need a quick exit strategy. I've read a lot of the forum posts and most of the documentation, but I might have missed a few important questions that I need answered before I start evaluating the software. If all goes well, then a license purchase is almost certain to follow.
1) How is the license activated? I've read that it is linked to the domain used. Does that mean I can use the same license on 2 boxes for a single company (failover configuration, same domain, databases synced)? Coming from HB, the license is linked to the installation path, domain name, and IP address. The IP address has always been a headache for us since the only way to activate private addresses (what we require for failover solution) is to send a ticket to "support" to get the IP updated on their end. Normal clients can only update a public IP that the license is linked to. Fine, no problem there. The downside is that we have to setup a failover solution for the private IP on our end, and have the license linked to that IP. More steps,more things to break apart (they always do, Murphy's Law).
2) Seen that most software code is not encrypted. What is encrypted?
3) How are software updates handled? I mean if I purchase a lifetime license without support, are the updates still available when the support runs out, or do I have to purchase additional yearly support for the updates after that? I do not mind purchasing support for when things go wrong, but I prefer not to have to rely on the subscription to keep the software updated.
4) Does the software need to be installed on the root website directory (www.example.com)? Or can I install it in a directory (www.example.com/billing or billing.example.com) and have my website template with links to purchase products?
5) I've seen that most pages can be edited with an in website editor. Does this support creating custom orderpages (a couple of paragraphs describing the products, maybe a small table/boxes on the bottom with buy now buttons for example)?
6) Any plans for full nginx integration? (no .htaccess, no manual file editing to make it work)
7) What is the average fix time for security bugs?
8) Can I move certain directories outside the publicly accesible directory (eg. template directory, speaking from HB experience)? If yes, what are the needed directories to keep in the publicly accesible directory?
9) A question for the developers, a must have in any job application. What do you do in your free time? Makes the difference on who get the job between a guy having all the certifications for it, or a guy having no certifications for it.
10) Will future updates (eg v4) require a license key renewal (paying for a new license)?
Question
mitsos
Hello,
I've seen your software mentioned on the HB forums and since I'm waiting anyday now for the HB implosion I need a quick exit strategy. I've read a lot of the forum posts and most of the documentation, but I might have missed a few important questions that I need answered before I start evaluating the software. If all goes well, then a license purchase is almost certain to follow.
1) How is the license activated? I've read that it is linked to the domain used. Does that mean I can use the same license on 2 boxes for a single company (failover configuration, same domain, databases synced)? Coming from HB, the license is linked to the installation path, domain name, and IP address. The IP address has always been a headache for us since the only way to activate private addresses (what we require for failover solution) is to send a ticket to "support" to get the IP updated on their end. Normal clients can only update a public IP that the license is linked to. Fine, no problem there. The downside is that we have to setup a failover solution for the private IP on our end, and have the license linked to that IP. More steps,more things to break apart (they always do, Murphy's Law).
2) Seen that most software code is not encrypted. What is encrypted?
3) How are software updates handled? I mean if I purchase a lifetime license without support, are the updates still available when the support runs out, or do I have to purchase additional yearly support for the updates after that? I do not mind purchasing support for when things go wrong, but I prefer not to have to rely on the subscription to keep the software updated.
4) Does the software need to be installed on the root website directory (www.example.com)? Or can I install it in a directory (www.example.com/billing or billing.example.com) and have my website template with links to purchase products?
5) I've seen that most pages can be edited with an in website editor. Does this support creating custom orderpages (a couple of paragraphs describing the products, maybe a small table/boxes on the bottom with buy now buttons for example)?
6) Any plans for full nginx integration? (no .htaccess, no manual file editing to make it work)
7) What is the average fix time for security bugs?
8) Can I move certain directories outside the publicly accesible directory (eg. template directory, speaking from HB experience)? If yes, what are the needed directories to keep in the publicly accesible directory?
9) A question for the developers, a must have in any job application. What do you do in your free time? Makes the difference on who get the job between a guy having all the certifications for it, or a guy having no certifications for it.
10) Will future updates (eg v4) require a license key renewal (paying for a new license)?
Thank you
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.