Skip to main content

CsCart - Guest checkout only

One of our clients needed a redesign of the checkout process of his website. Even though, it would be easier for me if it was a Ubercart or DrupalCommerce eshop, it was CsCart and I had to make my hands dirty. Or not...

The fact that I didn't really know the logic behind this system, I was obliged to think practically. The original checkout process needs 4 different forms to be submitted. The modified checkout process also submits 4 different forms. But no buttons exist for the checkout. The only button seen by the user is the "Complete checkout" button. Every other button is hidden and forms are submitted with jQuery .blur() calls when the input fields of each form have changed from their previous values. I must also say that the new checkout only allowed Guest Checkout. Every other option was removed.

Anyway, everything until now was just Javascript and CSS modifications in one tpl file. But we had another problem. The website also had registered users and CsCart has a problem with users trying to checkout as guests. CsCart doesn't really have a problem; it's the developers who couldn't find a reason for a user to guest-checkout and coded an extra if-statement. They are probably right about this "if", but I would prefer it to be a setting for the administrator to choose whether or not he needs it.

Of course, I Googled my problem and found that a few other cscart-licence-buyers also had this problem but no answer existed (@see 20444-the-username-or-email-you-have-chosen-already-exists). And then I decided to check and (eventually) hack the website code. I know it breaks the upgrade path but we don't really care about that. So... All I had to do was to go to /controllers/customer/checkout.php file and comment out the lines 518-529 and have the following result-code:

PS: The CsCart version used was 3.0.4 PROFESSIONAL. Unfortunately, I couldn't create an account in CsCart forums to post my solution, so I hope that anyone interested will find it here sooner or later.


Nathan Wallis said…
Hi there, are you able to share your code for the guest checkout, I would be interested to know how you did it.
Forerunner said…
Unfortunately, I cannot share the full code. I think I may provide some guidelines though.

The checkout page of CSCart contains some tabs (more like an accordeon) and when one step gets submitted, the next one appears.

What I did in my case was to show all fields from the very beginning and when a user filled all the values of each step/form I triggered, using jQuery, the click event of the submit button of the form I had previously used .hide() on.

I also had to modify the CSS for the throbber appearing on AJAX calls. I transformed it to a fullpage transparent overlay to make sure that the user doesn't keep filling the fields of the next form until the end of submitting the previous one.

Popular posts from this blog

Configure drupal_http_request() on the fly

The drupal_http_request() function supports connections using a proxy. You can configure a global proxy to use for all drupal_http_request() callbacks from the settings.php file of your website/installation by filling the following lines with the proper information:For those of you preferring a UI, then HTTP proxy module is for you.But what if you only want to use a proxy in some cases; like a custom module? In that case you will need the following function(modify accordingly):Now all you have to do is Call <?php _MYMODULE_change_proxy(); ?>.Do your drupal_http_request() calls.Call <?php _MYMODULE_change_proxy(TRUE); ?> to reset your previous settings.

Drupal: Allow registrations through Invite or Referral modules only

The Invite module provides invitations from existing users to their contacts. The Referral module, in contrary, creates a special URL for each existing user, which can be found in each user's profile, and allows new user registration. Even though, these two modules seem to provide the same functionality, they don't (and they shouldn't). Invite module, provides a mechanism for a site administrator to limit new registrations to "Invitations only". Referral module doesn't provide any of this functionality. Some users have requested the Invite module and Referral module to join in one module. Until now, there isn't anything to that direction. Wouldn't it be great though if there was a solution to limit drupal registration to referral or invitation only? Copy the functions below to a refinvite.module file in your sites→all→modules→refinvite folder and enable the module. Then go to http://<your-address-here>/admin/user/settings and enable the new …

Send mass email to certain users using VBO

Views Bulk Operations uses the built-in actions to act upon nodes, users, entities etc. Among these actions is our ability to send emails to users. If you try to use this action though you will encounter a small but serious problem. You are asked for an email address to send your message. You might say "but I have selected the users I want this message to reach. Why should I input an address again?". Don't get overwhelmed. What this field expects is not an address but a token. Specially this token [user-email]. If the website is intended for you, then you might say that's not such a problem to write this token down again and again. But if the manager of the website is bound to be the client or if you just want to spend less time writing things down, you might prefer to use a custom hook_form_alter() callback to set a default value. It could be done in both theme and module environment so suit yourself. Just add the following in your module or theme.