Configuring The Order Form For Domains & Hosting

[Krystalogik]

Hey Guys

 

I'm new to Blesta having been a WHMCS user for some years. I'm generally not clueless at all when it comes to using systems, scripts and software in general, but I have to say Blesta has got me a little stumped and from the few hours I've spent going through the various configurations and setting up products etc, it doesn't seem to be the easiest to setup (easy for those who know the system and how it works, but for someone looking at it out of the box, it's a chore..)

 

Firstly I'm interested to know why the the nice short url for ordering gets extended more than it really should be.

 

eg shorter url: mydomain.com/billing/order/

 

redirects to mydomain.com/billing/order/main/packages/label/?var=1&var=2

 

Seems a little pointless. I really don't need the extra (required) label on the ends at all (although I appreciate it has its use for other users of Blesta). But even so, why not just tack the label on the end of order (eg domain.com/billing/order/label/).

 

I'm a nut for tidiness and logic.. so when most of the pages on my site are logical (domain.com/contact/ | domain.com/support/) it looks rough when the nice -> domain.com/billing/order/ runs off to something much longer..

 

OK, enough whinning..

 

All I am trying to do is setup 4 hosting packages (done) where a user can click a link from the home page and start the order process.

 

I'm looking for this order process:

 

Step 1 - Package -> selected elsewhere (i.e home page or packages page) and not from the generic blesta ordering page.

Step 2 - Domain -> I need various options here.. Register domain / Use existing domain / Use subdomain + box to enter subdomain).

Step 3 - Script -> Select software/script to install or an option to not install anything.

Step 4 - Details -> User account information (Login or register I guess).

Step 5 - Pay -> Make payment.

 

From what I can see and tried, the order starts with asking for a domain name, which defeats the point of linking to a particular package from elsewhere within a site. Is there anyway for Blesta to remember what package was selected so it bypasses the "select hosting" part of the order process?

 

This all seemed relatively easy enough with WHMCS, but somewhat of a headache in Blesta (inless I am missing something). I'm really eager to use Blesta, I just need to totally figure this out and make it work without using hacks.

 

Incidentally, there is not much in the way of tutorials for Blesta out there at all. Written or otherwise. The documentation for Blesta, while thorough, isn't being of much help and can be confusing at times. I looked for various tutorials in setting up hosting plans, domains, order forms.. get it all working together.. couldn't find squat..

 

In closing, I apologise if it sounds like I'm bashing Blesta.. certainly not intentional, just a frustrated and "dont quite get it" first time Blesta user..

 

Thanks in advance for taking the time to read and respond.

 

Clive

 

 

 

 

[Michael]

The order redirects to the default order form.But I don't see why your complaining....

http://domainname.com/blestafolder/order/main/packages/order-form-name/?package_id={package_id}&group_id={group_id}

http://domainname.com ==> Your Domain

 

blestafolder ==> Your Blesta folder

 

order/main/packages/ ==> Order system plugin stuff

 

order-form-name ==> Order form's name

 

?package_id={package_id} ==> The Package ID for the package in Blesta's Database

 

&group_id={group_id} ==> The Group ID for the package in Blesta's Database

 

Direct Link tutorial is here: https://licensecart.com/billing/plugin/support_manager/knowledgebase/view/3/how-can-i-get-a-direct-url-to-a-package/11/

[Krystalogik]

Appreciate the response.

 

Firstly,  as much as it sounded like a complaint, it really wasn't. I was just asking why all that extra stuff in the url that isn't related to packages or products is needed (when in reality it isn't, at least not by the backend PHP side of things should paths within the code be correct).

 

I am aware of how to get a direct link to a package, but thanks anyway.

[Michael]

Appreciate the response.

 

Firstly,  as much as it sounded like a complaint, it really wasn't. I was just asking why all that extra stuff in the url that isn't related to packages or products is needed (when in reality it isn't, at least not by the backend PHP side of things should paths within the code be correct).

 

I am aware of how to get a direct link to a package, but thanks anyway.

 

If you don't have the package or group in the url it wouldn't select a package or find what packages in the group.

If you don't have the /main/packages/ the plugin wouldn't work.

[omaticon]

I believe what he is getting at is that it would be possible to have "cleaner" URLs for the ordering system if rewrites or post URLs were used.

[WebHostCentral UK - Dean]

I agree in a way.. I don't like the fact that it shows the full destination I.e plugin/support-manager/ etc

But I am starting to like blesta to much to care lol

[Michael]

But I am starting to like blesta to much to care lol

Yeah it does the job and it doesn't matter people don't complain it's that you aren't used to it it grows on you

[WebHostCentral UK - Dean]

again i do like the idea of hiding the full path as this is a potential clue to hackers etc... but with a little htaccess modding etc we can hide the full path

[Michael]

again i do like the idea of hiding the full path as this is a potential clue to hackers etc... but with a little htaccess modding etc we can hide the full path

 

You can make the shorter order urls by following: http://www.blesta.com/forums/index.php?/topic/1733-short-order-routes/

[JNdev]

The process of such orders in the mean @Krystalogik is crucial for client convenience.

I vot +10 if the team is able to change the style order blesta like WHMCS.

Perhaps the complicated process for us is not a problem, but for clients who are beginners will be very problematic. 

[Paul]

While the path to the order form doesn't seem logical at first, it really is. The path tells Blesta exactly what it needs to render the right page. For example, since Blesta supports unlimited order forms instead of just one, the label for the order form is included in the path. It would be nice to have shorter URLs in places though, and I see what you're saying.

Information on linking to a specific package can be found at https://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoOrderPages but I don't believe this will work when using a Domain & Other order type that starts with a domain.

It's likely there will be a new domain order form type with the new domain manager.

[JNdev]

35 minutes ago, Paul said:

While the path to the order form doesn't seem logical at first, it really is. The path tells Blesta exactly what it needs to render the right page. For example, since Blesta supports unlimited order forms instead of just one, the label for the order form is included in the path. It would be nice to have shorter URLs in places though, and I see what you're saying.

Information on linking to a specific package can be found at https://docs.blesta.com/display/user/Order+System#OrderSystem-LinkingtoOrderPages but I don't believe this will work when using a Domain & Other order type that starts with a domain.

It's likely there will be a new domain order form type with the new domain manager.

 

 

Glad to hear.

Waiting for the new domain manager, I'm trying some features of the trial.

Step 1 - Package

Step 2 - Domain -> . Register domain / Transfer / Existing domain / Use subdomain + box to enter subdomain).

Step 4 - Details

Step 5 - Pay & Done

Please develop.