MDS BLOG

For most of us hoping to use Oscommerce3  for our ecommerce system, there is little distubing thing with it after post installation but dont worry it’s also easy to debug. Normally after installing Oscommerce, you would be asked to delete the install folder for security purpose and also to change the permission on the configure.php file to read only.

But the following type  messages appear to be difficult to get rid  of;

• Number of queries: 19 [0s]
• Execution Time: 0.078s [osC_Services_debug]

Dont worry it’s easy, Here is the solution

Go to your Admin, > then go to Modules(on top menu in your admin) > choose Services > When the window opens , then choose to uninstall the “Debug” in the list by clicking on the icon uninstall linked to it.

Now refresh your store page and this should be fixed.

Just a little tip for my good readers using joomla. Recently  an email from one of my clients hosting provider came  informing him that his site has been suspended due to his site overloading the entire server. As a seriously growing website, you would not want your site to be offline for even a minute.

One of the reason why it is good to rent your server from an established hosting provider is the fact that they are used to most problems and would normally work with you to take care of the problem.

The culprit was simply the joomla cache that was turned off. If you turn on the joomla cache option from the joomla admin > Site >  Global configuration >System > Cache Setting.  Joomla would generate a file saved on your computer that can be called up when ever it is requested instead of stressing the server all the time if requests are made. In order to avoid this happening to your site, it’s better to turn it on after installation.

Please visit Joomla Hacks for more info.

Sorry i have been extremely busy these days trying to put some clients online, but just a quick note, after installing HESK help desk software, if you run into the problem of not being able to log into your admin panel please follow the instructions below.

The password reset script only resets the password, not the username.
You can either look in the mySQL database (table hesk_users) for the username or use the password reset script again, but open it in Notepad first and change

`pass`=’499d74967b28a841c98bb4baaabaad699ff3c079′

to this:

`user`=’Administrator’

Then you can use the default info to login;
User: Administrator
Pass: admin

One of the headache  that come with Prestashop is the fact that most people cannot get around the function in the admin. I considered myself a prestashop guru but was brought down to my knees with a simple problem setting default carrier in Prestashop.

PROBLEM: Once a customer logs in and checks out an order, they cannot go further because of this message “There is no carrier available that will deliver to this address!”

You may wonder why this is happening even after you have created a carrier and saved it as a default.

Quick solution: Go to Admin > shipping > Carriers. Make sure you have set up your carrier and save it as the default carrier, then go to the >  Price 0r > Weight tabs  just above on the menu.  Add a price rage  or weight range.

Please note that this must be realistic with the range of prices and weights in your store. It’s better to set a range for one and then click on >Shipping tab,

Select a radio button to reflect  billing according to weight or price  as you have chosen and then just below  where you find this text “Fees by carriers”, select the default carrier and save the page. Now test your clients account again and you should be okay.

If you are having problems with this , feel free to leave a comment here and we will answer it.

So many people have problems passing through the first installation stage in Drupal and the problem is usually the error page that tells you that “register_global” is on and must be disabled. There are so many ways proposed in the Drupal documentation on how to do this but to me the one i find to be the easiest is simply creating php.ini file in your root folder. Some solutions would tell you to contact your host or do this or do that but before you go ahead, try this solution first.

Now let’s leave every other thing behind and see how this can be done;

If you meet this error, simply open up a notepad, put this text in it register_globals = off , exactly like that, then save the file as php.ini and then upload the file to your root folder and that should be the answer to your problems hopefully.

Not only do this php.ini problem apply only to Drupal, it also applies to other similar problems with similar php built database driven sites.