New Ajax Order Form

[gei]

Matt: will this allow us to add our own server side field validation? We had to add some in to the current order form using javascript and it's really ugly.... not to mention a major hassle whenever we want to upgrade...

[doktorbune]

This is so good but It will be very good if the moving ajax box places on the right side panel.

[getup]

I'm impressed. Really good job.

[TheHostingHeroes]

matt

 

Love the new Ajax system. FYI when u change from USD to GBP on the right, it does not change the ($18 month \ $180 annually) drop down box to GBP on the left.

[Grizzlyware Josh]

I would never compare modernbill with whmcs. There is no comparison, whmcs just works.

 

We should make an advert, like the Honda one

[xiconsulting2]

We did this with WHMCS here, was waiting for beta access to test AJAX form - but never received it so coded our own using XAJAX, the WHMCS API and hooks for fulfillment.

 

Still some code cleanup (especially with the javascript) but it does work well for us. We have some stuff in there to check for date of birth (older than 18), existing members, etc in addition to working with the WHMCS promo code database to determine the validity of the codes.

 

http://bit.ly/a1yB9T

Edited July 13, 2010 by xiconsulting2

[xiconsulting2]

I would have to say that after creating such an advanced script and completely coding many custom behaviors, functions, and what not - WHMCS has been extremely flexible even with closed code. We were able to do everything we had set out to do, although it takes a little more time, its very simple to easily create new API functions.

 

We additionally have created an entirely new support frontend Adobe AIR application with Flex - which was based on some of the existing API functions along with some new ones we created (we converted all of the API calls into REST format to make sure the structure of all of our API calls are the same regardless of the underlying script). Many of the custom API functions work directly through the database, or make multiple calls using the WHMCS API. We also utilize the subaccounts feature, but in a different way (for spouse accounts).

 

At first it seemed a bit hopeless with closed source, but with some creativity, patience, and a decent amount of php - pretty much any obstacle can be overcome.

 

Anyone could create a form similar to this, would have been nice to get beta access though as it woulda been nice to test and provide some feedback.

[ExsysHost]

Wow Matt thank you so much that is exactly what I wanted to see!!

[vchosting]

It will certainy be a great addition to the cart.

[ExsysHost]

@xiconsulting2

 

So did your order form make its orders by using the API, or did you just modify the origional order form and add some API calls in to it?

 

I really like what I see on yours and hopefully WHMCS's can be customized to resemble...

 

I think it is key to show people how much they are saving for term selection and the terms of service like you have done.

[ExsysHost]

@xiconsulting2

 

looks like I will be following your route... just tested and the new official ajax order form does not degrade gracefully for people who don't have javascript enabled...

 

The proper way would to have all the form elements as html then hide them with a javascript library as needed for slide effects.

 

 

Any pointers you have to set me in the right direction would be much appreciated.

[zhu]

This looks great. It's a lot less clicks for the user which can only be a good thing. Great work guys!

[xiconsulting2]

@xiconsulting2

 

So did your order form make its orders by using the API, or did you just modify the origional order form and add some API calls in to it?

 

I really like what I see on yours and hopefully WHMCS's can be customized to resemble...

 

I think it is key to show people how much they are saving for term selection and the terms of service like you have done.

 

The actual processing takes place by calling individual functions and passing them along to other functions depending on the outcome, there definitely are optimizations to be made - but basically we used our own validation via PHP/xajax, and if all validates, pass it along to various API functions.

 

1. Validate form, return the errors if there are any

 

2. if ok, process payment (again with our service, they HAVE to have paid before we establish their account, we do not want to be using an invoicing system for the first order because it confuses the elderly, we had an 80 year old woman sign up for our service with the old WHMCS template based form, and she did not know what to do to pay an invoice - we have since provided better instructions for users) (pass transaction ID to next function)

 

3. Then use API Create Client (our clients service does not allow any more than one product per user, so at least for our needs there is no login form to "pre-fill" the account information, although it could definitely be done) (pass client id to next function)

 

4. Then API add order (pass order id/invoice id/transaction id/client id to next function)

 

5. Then API mark invoice, pass client id and order ID to next function

 

6. Then API accept order, pass client id to next function

 

7. Finally, do create module function and in XAJAX we do:

 

$redirecturl = "https://whmcs.domain.com/members/dologin.php?username=$email&password=$password&goto=authentication";
$objResponse->redirect($redirecturl, 0);

 

which does a redirect to log the user in and then provides the page where their order is confirmed and they may continue to activate their account.

 

Of course between each of these steps, we needed to account for an error in processing, or if there is some snag between the database or WHMCS, chaining these functions needs to be logged, so we do keep a log of what is going on during the order - and return a jquery growl alert telling the user to not submit their order again and to contact customer support. We also disable the submit button during and after processing until errors are corrected.

 

Sorry its a little confusing, it was a unique situation but we plan to clean it up a little more or if possible do everything directly with the DB and pass the API altogether.

[nike.stars]

the new ajax form seems quite a bit ugly look (unprofessional) compared to the original non-ajax order form

[D9Hosting]

the new ajax form seems quite a bit ugly look (unprofessional) compared to the original non-ajax order form

 

I think it'll provide a good starting point, with the source code available it gives us all the ability to customize it to our own needs

[Derek]

Been a few weeks. How we looking for 4.3 ?

[ExsysHost]

Yeah we are getting anxious, we rolled a new site and are waiting on the realease of the new system before customizing the cart.

 

We have always had customers calling because they have issues with figuring out how to use the cart, some people get confused at the many buttons like Update cart... we are hoping to streamline this process for these type of customers with this new order form.

[sorin.pohontu]

The new AJAX order form is looking very nice.

 

Looking forward to see the new version released

 

Regards,

/Sorin

[InterServed]

Been a few weeks. How we looking for 4.3 ?

 

almost a month i guess ^^

[Derek]

almost a month i guess ^^

 

yeah, sigh can't keep to time lines.

[ckh]

yeah, sigh can't keep to time lines.

 

That's why they don't give release dates. Their priority is to make sure the release is stable and bug free and they won't release it until it is.

 

If they give a release date say they'll try to release something within a certain time period and don't, then the complaints come rolling in.

 

I would much prefer the way it is. I want and need fully tested and stable releases. In fact, I'll wait a while before upgrading, checking the forums often to make sure there weren't any problems before upgrading.

 

I guess if you are in such a hurry, you could see if you could receive the beta releases, but, please, don't try to push them to put out a release early. They won't do it and justifiably so.

[rmaweb]

I agree with ckh, its better to wait and get a stable package.

[ExsysHost]

Software development never can keep to timelines... making claims to such deadlines just results in buggy code... look at the catastrophe known as modernbill for a perfect example.

 

On the same note, I really wish WHMCS had a bug tracker that was public so we could watch the progress in action, I think this would really put peoples anxieties at ease.

[Derek]

That's why they don't give release dates. Their priority is to make sure the release is stable and bug free and they won't release it until it is.

 

If they give a release date say they'll try to release something within a certain time period and don't, then the complaints come rolling in.

 

I would much prefer the way it is. I want and need fully tested and stable releases. In fact, I'll wait a while before upgrading, checking the forums often to make sure there weren't any problems before upgrading.

 

I guess if you are in such a hurry, you could see if you could receive the beta releases, but, please, don't try to push them to put out a release early. They won't do it and justifiably so.

 

Your point is so moot as they did give a time line. I never asked once when it would be ready but I expect when they say when it will be ready we will be able to download the new version.

[HostOrca]

I would rather they release it once it has been tested and is ready for stable release.

 

Rather than them pander to people who want it released straight away, regardless of whether it is ready or not.