How To Change Headings On Checkout Page in Magento

Here was another tough item to track down in Magento. When you go to “One Page Checkout” in Magento, it really takes 6 steps to checkout, kind of a pain. We’re looking for a free solution to make it a true one page checkout process. In the meantime, we figured if we made the steps more clear, it might make checking out easier and therefore convert to more sales.

One of the ways to make checkout more clear in Magento is to use different wording on the checkout page. For instance, “Billing Information” may not be clear to people that they need to add the actual credit card bill mailing address. So to make it clear, we added to that line, so now it reads “Billing Information (If using credit card, make sure you use the billing address for that card)”. Problem is, where the heck is that line?

We wasted about an hour looking for it and finally found it in app/locale/en_US of all places. Find the line that reads “Billing Information”,”Billing Information” and change it to read “Billing Information”,”Billing Information ( If using credit card to pay, make sure you use the billing address for that card on this page)”

Typical Magento to make things hard to find, but there you go. That’s how to change headings on checkout page in Magento.

Problems With DrWeb Sending Failure e-mail Notices

If you have your own server and you are getting failure notice emails from DrWeb Antivirus, you need to make some changes to your settings.

You should change the crontab of the DrWeb update to not mail you in the first place – this will remove all the spam you recieve at every DrWeb update.

Login to Plesk as Admin.

In the Settings -> Scheduled Tasks -> drweb (just click the link)

You change the Command of the cronjob by adding a “>/dev/null 2>&1″ to the end of command. I.e.

Code:

/opt/drweb/update.pl >/dev/null 2>&1

This will make sure that Crontab does not mail you with the output of the updatescript every time it exits.

Please keep in mind that depending on your OS – for some reason there might also be a crontab entry for the update in your filesystem under

#/etc/cron.d/drweb-update

Where you will also need to edit the commandstring to be “/opt/drweb/update.pl >/dev/null 2>&1″

The Magento File Structure and Architecture

When you start working with Magneto, you may find it confusing as to the directory structure. In this article I hope to help shed a little light on some of the key directories in Magento and what they do so that maybe when you’re working in Magento, things will make a little more sense.

Here are a few things you need to know the location of at some point when developing with Magento and the directories that they are stored in.

1. The templates file

/app/design/ is the core storage folder for template files. With it breaking down into adminhtml/ for administration templates, frontend/ for frontend templates and install/ for installation templates.

Within these you’ll find your default template set aptly named default. In your template set folder are your individual theme folders that come with Magento.

layout, locale and template are the core directories that contain the files that make up your themes.

2. The skin files (resources, components, resources)

In /skin/ you’ll find your CSS, images, Flash, JavaScript and any other resource files that relate specifically to templates in the system. You will also find the adminhtml, frontend and install directories distinction here.

3. Language files and e-mail templates

/app/locale/ is your core directory. With sub-directories for each language set installed for the store. You will find .csv files for each of the modules installed on the system relating to their translations. You’ll find the Magento e-mail templates in /template/email/ within your language directory in /app/locale/.

4. Core configuration

/app/etc/ contains all configuration files for Magento. From the local.xml file which contains your database configuration, amongst other things. To your modules/ folder which contains the declaration of modules in the system.

5. Local, core and community modules

All modules for functionality are stored in /app/code/ and are broken down into the following folders:

  • community – for modules installed via Magento Connect.
  • core – for modules that come with Magento by default.
  • local – usually for locally developed modules

6. Media files

All images uploaded to the system as well as the images resized dynamically by the system are stored in media/.

When importing media files via system profiles (Magento’s name for batch processing), /media/import/ will be your folder to place the images for the products.

7. The var directory

The var directory is used for several functions in the system:

  • Backups are exported to backups/ by the built in system backup tool.
  • The system cache is stored in both cache/ and session/ folders.
  • Data import for default system data import profiles is set to import/.
  • Data export for default system data export profiles is set to export/.

Hopefully this has given you a good indication as to the important directories in Magento’s file structure.

How To Find A File Using SSH

To find a file on your server using SSH, simply use the “locate” command.

Example: locate fileyouwant.file

This will result in an output of all files on your server with that name