Troubleshooting


Introduction


We are proud of the quality of our extensions and find that in most circumstances there are no issues with installation and getting the most out of your chosen extension.  However if you do come across an issue this general troubleshooting page provides information relevant to many extensions.
 
If you think that the issue is a general one e.g. general installation or setting up a CSV file then please check here for guidance. If you think your issue is more extension specific then please refer to the troubleshooting pages behind your chosen extension. There is some crossover between the two but all issues should be addressed in these sections.
 

Common reasons the extension will not work after installation:


  1. Incorrect serial key. Obtain the correct server_name from your store using our instructions here.
  2. Uploaded to the wrong location. Upload the app directory from src to root Magento directory. 
  3. Permissions for the extension are incorrect. CHMOD extension directory to 755 recursively.  
  4. SQL failed. Go to the core_resource table and drop the entry for our extension e.g. productmatrix_setup. Refresh the frontend with cache switched off. See here. You can also check for the presence of the extension attributes e.g. package_id in the eav_attribute table. Also check for the table shipping_<extension> e.g. shipping_productmatrix. If neither of these are present, the installation had failed to compile.  
  5. Incorrect Magento version was uploaded giving SQLSTATE[42S02] error. Upload the correct M1.x extension version and refresh with cache switched off. See here.  
  6. Forgotten to refresh the indexes. Giving an error SQLSTATE[42S22]. Refresh all indexes in `index management`. See here.  
  7. Incompatible version or conflict. Giving an error Fatal Error: Call To A Member Function getId() On A Non-Object In app/code/core/Mage/Tax/Model/Calculation.php on line 211. Contact us for an updated version.
  8. Extension conflict. Tells: white screen; half page loading or something missing on load. See here.
  9. Missing files. If one of the files hasn't copied over correctly you will see an error similar to this:

        "Fatal error: Class 'Mage_Wsacommon_Helper_Data' not found in /home/yourdomain/yoursubdomain/app/Mage.php on line 520"

         or

           "Fatal error: Call to a member function toOptionArray() on a non-object in

            /home/yourdomain/yoursubdomain/app/code/core/Mage/Adminhtml/Block/System/Config/Form.php on line 385"

        Copy the files over again and ensure each and every file copies sucessfully.
 

Common configuration mistakes during setup:


  1. Attributes have not been defined. The groups associated to your products have not been created yet. Read about attributes and how to setup. See here.
     
    • Attributes not assigned to every attribute set. Only assigned to the `default` set on initial install.
       
  2. Incorrect CSV format. For whatever reason - the CSV format is not correct. We recommend using Calc to manipulate the tables and to always save in the original format. See here.
 

I cant resolve my issue - where do I go now?


Please take a look under your particular extension, there are screencasts, examples, & troubleshooting guides to help you.

If you are still having issues then raise a support call to support@webshopapps.com


Contents

  1. 1 Introduction
    1. 1.1 Common reasons the extension will not work after installation:
      1. 1.1.1 Common configuration mistakes during setup:
      2. 1.1.2 I cant resolve my issue - where do I go now?
  2. 2 Installation  
    1. 2.1 Password Protected ZIP File
    2. 2.2 Uploaded M1.3 onto M1.4  
    3. 2.3 Indexes Have Not Been Refreshed  
    4. 2.4 M1.4 Magento GetId() Error  
    5. 2.5 SQL Not Being Run  
    6. 2.6 Reinstalling Extension - SQL Not Being Run
    7. 2.7 Specified Key Was Too Long
    8. 2.8 Integrity Constraint Violation
    9. 2.9 Extension Not Showing Up In Admin Panel
    10. 2.10 Extension Not Working - Serial Keys  
  3. 3 Uninstallation
    1. 3.1 Disabling Extension
    2. 3.2 Removing Shipping Extension
    3. 3.3 Invalid Model For Shipping Method: MatrixRate
  4. 4 Shipping Methods
    1. 4.1 Debug In Shipping Method
    2. 4.2 This Shipping Method Is Unavailable - Using Mac
    3. 4.3 Parent Shipping Groups And Bundle/Configurable Items
    4. 4.4 Configurable Product Setup
  5. 5 Product Listing  
    1. 5.1 No Shipping Tab In Product Listing
    2. 5.2 Tax & Shipping - Rounding Issues
  6. 6 SQL
    1. 6.1 Open_Basedir Restriction In Effect
  7. 7 Locales  
    1. 7.1 Multi-Lingual Stores & Shipping Text
  8. 8 Debugging
  9. 9 CSV Tables
    1. 9.1 Using Post/Zip Codes
    2. 9.2 CSV Import Error: Notice: Undefined offset: 16 in ....
    3. 9.3 Unable To Import CSV - Using Europe ; CSV Format
    4. 9.4 Undefined Offset Error When Uploading CSV File
    5. 9.5 Duplicate Row Error
    6. 9.6 What Do I Enter In Region Field
    7. 9.7 Country Codes in Magento
    8. 9.8 Google Checkout Country Codes
    9. 9.9 UK Postcode Validation In Shipping Estimator
    10. 9.10 American State Zip Codes  
    11. 9.11 Quickly Merge Postcodes Onto 1 Line
    12. 9.12 No Import Button To Upload CSV File
    13. 9.13 Excel Leading Zero
    14. 9.14 Exporting The CSV File
    15. 9.15 Locating The Backup CSV File
    16. 9.16 Post/Zip Code Filtering Not Working
    17. 9.17 Not getting rates defined in csv but instead getting $0.00

Tutorials

 
 
 

Installation
 


 

Password Protected ZIP File


We do not password protect our ZIP files, if you are asked for a password when trying to extract your extension it may be that the directory structure is too long. (I.e C:\downloads\long directory name\long directory name\unzipped folder\...), try downloading the ZIP to the C: drive and extracting there.

Uploaded M1.3 onto M1.4
 


After Installation: Column Not Found: 1054 Unknown Column 'Used_In_Product_Listing' in 'Field List'
 
You are trying to install a 1.3 extension onto a 1.4.* Magento release. When you purchase the extensions you will have 2 zip files - one will be marked with M1.4.  Make sure you install this on Magento 1.4.* releases. Upload over the existing 1.3 release and refresh the back end with cache disabled.

Indexes Have Not Been Refreshed
 


SQLSTATE[42S22]: Column Not Found: 1054 Unknown Column 'e.Some Attribute' in 'Field List'

This error means that your new attribute has not been indexed yet.

After installing an extension you should re-index all indexes and refresh the cache - always keep the cache disabled during modifications and re-index whenever new attributes are created.

 

M1.4 Magento GetId() Error
 


Fatal Error: Call To A Member Function getId() On A Non-Object In app/code/core/Mage/Tax/Model/Calculation.php on line 211

This problem occurs in 1.4 Magento, and some of the shipping extensions expose it.  Please contact us directly from this sales link for an updated extension.

 

SQL Not Being Run
 


SQLSTATE[42S02]: Base Table Or View Not Found: 1146

Please make a full database backup and Magento backup before proceeding. We can not be held responsible for any loss of data or revenue. If you are unsure of what you are doing we recommend consulting with either us or your developer.

This means the extension or Magento can not find a table in the database.

If this happens when you first install an extension it means the SQL has not run. This is usually caused by a race condition in Magento whereby multiple entities are trying to access the same resource.

To resolve this you need to login to your database and find the table called "core_resource". You then need to find the entry for the extension causing the issue (Refer to the error thrown by Magento) and remove that entry.

This will force the SQL to be re-run after refreshing the frontend.

 

Reinstalling Extension - SQL Not Being Run


If you manually remove an extension and the SQL tables/entries, when you re-install you may find that the SQL side is not re-entered. This is expected behaviour. From a Magento perspective, it has no idea that you have manually removed the files.  

Be careful when following the actions below, as it will re-run all the SQL from the initial install. This may result in your site crashing if it cannot re-run the SQL successfully. I recommend you understand what the SQL is doing before you invoke it.

To look at the SQL find the SQL folder under the extension directory. There will be an install.sql file.  The version number used can be found in etc/config.xml in the extension folder. You can either run this SQL manually (you will need to replace variables with real table names, or you can run by removing the entry for the extension setup in the core_resource table in phpMyAdmin.  E.g. productmatrix_setup.

It should be stressed that as long as you do not remove the SQL when you uninstall an extension you should never have to re-install, so this should not be an issue.

If your site does crash, then I recommend you replace manually the row you have deleted in core_resource (maybe take a backup first), or comment out the contents of the SQL install file in the extension directory.

No liability can be accepted for misuse of the information above, please be aware this could cause problems if you do not fully understand what you are doing. If in any doubt we highly recommend you contact us to do this for you at sales. There is a consultancy charge for such work as it outside the scope of extension sales.

 

Specified Key Was Too Long


Specified Key Was Too Long; Max Key Length Is 1000 Bytes
 

There is a problem that affects a minority of users when installing an extension with this error. This is because of a MySQL bug - a quick search on Google shows the issue.
 
You will need a revised SQL file to resolve the issue. You are advised to disable the extension temporarily to prevent your site from experiencing any more issues in the mean time. If the the complaint is about the unique keys, go to your SQL install script in app\code\local\Webshopapps\Productmatrix\sql\productmatrix_setup (using Product Matrix as example) and open the latest version into a text editor.
 
Find the line declaring UNIQUE KEY and remove this line. On the PRIMARY KEY line above, delete the last comma "," and save. Upload this over existing install script, clear your cache and keep disabled. Refresh the front end - if no errors are picked up you are resolved.
 
Otherwise, Disable the extension by renaming the relevant extension file from app/etc/modules, to e.g. Webshopapps_ProductMatrix.xml.orig refresh front end, rename and remove .orig and refresh again.
 
 

Integrity Constraint Violation


If you see an error complaining about duplicate entry with the word setup in it then it is probably because you have already installed this module before in some form.

 
Firstly check the appropriate SQL file to ensure that you do actually want to run it - in this case under freeoptionalshipping_setup. If not then comment out the main SQL section.
 
Then remove the entry "freeoptionalshipping_setup" from the table core_resource
 
 

Extension Not Showing Up In Admin Panel


If you can not see the extension then it is either because you havent installed the files in the correct location, or because you havent refreshed the cache.
 
You should have extension related files under app/etc/modules, and app/code/local or app/code/community.

Webshopapps was formerly known as Auctionmaid, so you may see extensions under the Auctionmaid banner

 
 

Extension Not Working - Serial Keys
 


When you try to save an invalid serial key - it will not be immediately erased. Only after you try to execute functionality of the extension will the serial key will be erased.
 
In most cases you will know this when you try to get a shipping rate using one of our shipping extensions. Get the server name of your Magento installation again and contact us to resolve the situation.
 
 

Uninstallation


 
 

Disabling Extension


In most cases it is possible to disable an extension by renaming the relevant .xml file in app/etc/modules. You must rename to be non .xml e.g. Webshoppapps_Productrate.xml.orig.

To enable reverse the process.

 

Removing Shipping Extension


Here are the steps for removing a shipping extension. All our extensions sit in the app/code/local or app/code/community areas, so there is no impact on core code.
 
 
  1. Disable cache
  2. Remove files from app/code/local/community (matrixrate) or app/code/local relating to the extension. These may be under a Webshopapps or Auctionmaid banner
  3. Remove the relevant .xml file from app/etc/modules
  4. Run the workaround to delete the extension from the list of shipping carriers - see here
  5. Verify removal on admin/frontend
  6. Enable cache

Invalid Model For Shipping Method: MatrixRate


This problem occurs as Magento is not very good at clearing out shipping methods when you delete them.  The shipping method can be the name of any shipping extension you have deleted.

Suggest you backup your database first, especially if you are not comfortable around sql.

To resolve go into phpmyadmin, get up a SQL prompt and do the following:

select * from core_config_data WHERE path like "carriers/matrixrate%";

If you are happy that the result set is that which you want to delete (should be around 15 rows) do following:

delete from core_config_data WHERE path like "carriers/matrixrate%";

If you get invalid SQL syntax can you replace the quotes above with quotes " from your keyboard - it gets confused in the copy/paste translation sometimes.

Replace MatrixRates where appropriate.

 

Shipping Methods


 

Debug In Shipping Method


Some of our extensions now have a debug switch where you can get logs that can be sent across to us to enable us to diagnose configuration issues.
 
To use this feature:
 
  1. Switch on Developer Logging under System > Configuration->Developer
  2. Switch on debug under System > Configuration > Shipping Method for the WebShopApps extension (you may have to change to website view under Current Configuration Scope to see debug option)
  3. Switch on debug under UPS, Fedex if appropriate
  4. Get a shipping quote
  5. Retrieve the log from /var/log/system.log and send to sales with an explanation of issue
 

This Shipping Method Is Unavailable - Using Mac


If you are unable to retrieve any shipping rates, and are using Excel on a Mac can you make sure you save the files in Windows CSV format. This is a known issue, and documented by Magento for tax imports here

You can confirm this issue by looking in the table where the csv file is uploaded. The table name is likely to be shipping_<extn_name> e.g. shipping_premiumrate

 

Parent Shipping Groups And Bundle/Configurable Items


The option is referring to which product the extension looks at when getting the shipping group for bundled and configurable items. Should the extension look at the actual bundle/configurable item shipping group? Or look at the shipping group of the individual products that make up the bundle products?
 
Bundled Example:
 
  • Product A with a shipping group  "LARGE"
  • Product B with a shipping group "SMALL"
  • Bundle Product with shipping group  "BUNDLE" holding products A+B

This option enables you to choose whether to use "LARGE" and "SMALL" as shipping groups from the child products or whether to use "BUNDLE" from the parent.

Configurable Example:

  • Configurable Product with shipping group "T-SHIRT"
     
  • Simple Products beneath with the shipping group "LARGE,SMALL"

In this scenario you may wish to define shipping based on the fact it is a T-SHIRT or the fact it is LARGE or SMALL. The "Use Parent" shipping option provides this.

Remember to ensure your shipping group association created is the same as in your CSV file, case sensitive.

 
 

Configurable Product Setup


Where the shipping group attribute is used to assign products to a group - it may have "Use to Create Configurable Product" field set to "Yes". In actual fact, by default this should be set to "No" - this may mislead you when creating a Configurable Product and show the shipping group as a selectable choice to the customer (which is very undesirable) and would also amount to the Configurable Product not having the "Shipping" tab available - meaning no shipping group is selectable for it either. 

So to fix this, just make sure"Use to Create Configurable Product" is set to "No" and re-do the Configurable Products where they have been mistakenly set up with the Shipping Group attribute. You will then be able to assign the group correctly and get back rates when the Configurable Product is in the cart as expected. In Product Matrix this attribute is "package_id", if you have another extension which uses shipping groups,refer to the documentation in order to know which attribute it is.
 

 

 

Product Listing
 


 

No Shipping Tab In Product Listing


Ensure the Shipping group and associated attributes are in the attribute set of the product you are editing - they are only in the default attribute set on extension install.
 
  • Attributes can be found under Catalog > Attributes > Manage Attributes.
  • Attribute Sets can be found under Catalog > Attributes > Manage Attribute Sets.

Tax & Shipping - Rounding Issues


Shipping extensions will generally be agnostic to tax settings, and they will always calculate based on the tax exclusive price. So if you are using something like Matrixrate and the Price filtering make sure you bear this in mind.  Webshopapps do produce extensions that work on the tax inclusive price, but we would recommend if you can stick to standard magento you should do so.

If you are experiencing rounding issues around tax then this forum article may help:

 

SQL


 

Open_Basedir Restriction In Effect


This error means that a script is trying to run (usually the SQL install script for an extension) in a directory where scripts are not allowed to run as defined in your php.ini or Apache config file (depending on your configuration). This is a security feature designed to disallow untrusted scripts to run - more info here
 
To resolve this you should either comment out the line or add in the directory where the script lies, on a standard install the line is commented out (see screen shot attached).
 
The full error will look something like this:
 
 
a:5:{i:0;s:509:"Error in file: "/var/www/vhosts/your-domain/httpdocs/app/code/local/Auctionmaid/Productmatrix/sql/productmatrix_setup/mysql4-install-3.0.2.php" - Warning: realpath() [<a href='function.realpath'>function.realpath</a>]: open_basedir restriction in effect. File(your install path) is not within the allowed path(s): (/var/www/vhosts/your domain/httpdocs:/tmp)  in /var/www/vhosts/your domain/httpdocs/app/code/local/Auctionmaid/Productmatrix/sql/productmatrix_setup/mysql4-install-3.0.2.php on line 2";i:1;s:1060:"#0 /var/www/vhosts/your-domain/httpdocs/app/code/core/Mage/Core/Model/Resource/Setup.php(374): Mage::exception('Mage_Core', 'Error in file: ...')

 

Locales
 


 

Multi-Lingual Stores & Shipping Text


If you want to add locale support for your CSV file you manage this via the Shipping.csv file in app/locale, much as you would do for other text on your store.
 
So, if for instance you want to specify shipping as Courier on your UK store and Kurier in German then in the Shipping.csv for GB add a line Courier,Courier, and for the German Shipping.csv add Courier,Kurier.  Then in the shipping rates CSV file which you upload in the shipping method configuration set the delivery type to be Courier.
 

Debugging


On some of our extensions we have now added a debug switch where you can get logs that can be sent across to us to enable us to diagnose configuration issues.

To use these feature:

  1. Switch on Developer Logging under System->Configuration->Developer
     
  2. Switch on debug under System->Configuration->Shipping Method for the WebShopApps extension
     
  3. Get a shipping quote
     
  4. Retrieve the log from /var/log/system.log and send to sales with an explanation of issue
 

CSV Tables


 

Using Post/Zip Codes


In some circumstances, it may be advantageous or necessary to filter shipping based on the packages destination post/zip code. This is achieved in a number of ways:

To specify a range of post/zip codes: These must be numerical only, I.e. 90210 is acceptable, W5 2LH is not.

  • Enter the start of the range in the column "Post/Zip code From".
  • Enter the end of the range in the column "Post/Zip code To".

To match a post/zip codes pattern: Use the field "Post/zip code from"

To match all post/zip codes beginning with a a sequence. I.e. to match any postcode beginning with 902 you would enter 902%.

This is very powerful but doesn't fit all requirements, such as if you need to use UK postcodes and treat the postcode EH12 2JK differently from EH1 2LD as entering just EH12% would potentially match both if no space is present. This can be solved by creating rules using "_" which represents one and only one character of any type. So you would create a rule such as such:

  • EH12 ___ for the EH12 postcode entered with a space
  • EH12___ for the EH12 postcode entered with no space
  • EH1 ___ for the EH1 postcode entered with a space
  • EH1___ for the EH1 postcode entered with no space.

If you do not want to use the post/zip code field, you can enter * and it will be ignored.

Note: The postcode logic uses mySQL regular expression syntax - for more info see here
 
 
 

CSV Import Error: Notice: Undefined offset: 16 in ....


You will see this problem if you have not got the correct amount of columns defined in the CSV file.  Check an example file and compare it with your own.
 
Sometimes this occurs when you have a last column (e.g. Notes) which has no values. If you open in Word pad you will see some rows with a comma at end and some without. To ensure it works try putting a * in the last column if not using.
 
 
 

Unable To Import CSV - Using Europe ; CSV Format


CSV means comma separated values. Unfortunately in Europe (ex UK) Excel is configured by default to use ; as the delimiter, rather than ,
 
This causes a problem for the extensions as they only upload based on comma delimiters.  We could obviously change this, but have chosen not to, in order to stay in line with standard Magento. We realise this is an inconvenience to our European partners but assume you will hit this problem elsewhere in Magento (e.g. Taxation files, product imports) so hopefully you can see the reasoning behind the decision.
 
The quick solution to opening comma separated files in Excel then do Data >Text to Columns and then selecting comma as a delimiter.
 
The better solution is detailed in following link - solution #3

Undefined Offset Error When Uploading CSV File


An error like this when you upload a CSV file means you do not have the correct amount of columns:
Notice: Undefined offset: 16 in /app/code/local/Auctionmaid/Productmatrix/Model/Mysql4/Carrier/Productmatrix.php on line 891
 
Please read documentation and see examples to see the amount of columns.  For the Product Matrix CSV it can be one of two formats, 15 or 17 columns. If you add in the algorithm column you must also add a notes column at end.

Duplicate Row Error


Duplicate Row #195 (Country "GBR", Region/State "*", Zip "Pa1___") exception 'Zend_Db_Statement_Exception' with message 'SQLSTATE[23000]: Integrity constraint  violation: 1062 Duplicate entry '1-GB-0--Pa1___---- 1.0000-10000000.0000--1.0000-49.9400-0.0000-10' for key 'dest_country'' in C:\xampp\htdocs\productmatrix\lib\Zend\Db\Statement\Pdo.php:238
 

Stack trace:

If you see something like above it means you are trying to put in 2 entries which would match the same logic including delivery price. Check through your CSV file to ensure you have no duplicates.  The Row # is an indicator as to the row the problem is on in some cases.

What Do I Enter In Region Field


This field can be left with a * which means include all.

Firstly check you have regions - these can be seen in the drop down on the cart shipping estimator.  If you don't then try downloading your countries locale extension. Otherwise you may need to define yourself (if you wish to use).

If you have region codes you need to use the short code in the CSV. This correlates to the 'code' field in the database table directory_country_region.

For example in the USA valid codes are AK, CA, NY, etc.
The values in the region/ state field (from csv) are converted into numeric values before they get save into the database by directory_country_region table. For example: 
  • If there is no value in region filed, it gets save as zero
  • If there is value say NSW or any region in that filed, then it will convert the value into its numeric value and saves into the database and when you try to retrieve it, then it gets convert back to the actual value

 

Country Codes in Magento


The country codes in Magento should conform to ISO3166 (aka ISO3) standards  - see the list here
 
There are some anomolies though, in particular Romania is ROU according to ISO3 but ROM in Magento pre-1.4. Magento have fixed this for 1.4 onwards (and Enterprise), so be careful if upgrading.  There are a handful of codes like ROU, I dont have the full list.

If you look in phpmyadmin at the table directory_country you will get the full list of ISO3 codes used.

If you look in directory_country_region you will get the full list of region/state codes used.  If you want to say remove some of the military states then you can do by modifying this table.

 

Google Checkout Country Codes


Please see here for a list of google country codes
 
 

 

UK Postcode Validation In Shipping Estimator


  • Take a look here for info on validating UK postcodes.

 

American State Zip Codes
 


  • This link shows all the California zip codes (and others) - here

 

Quickly Merge Postcodes Onto 1 Line


I use TextPad to do this. If we have the following set of postcodes:
 
  • PA11
  • PA12
  • PA13
  • PA14
Firstly copy out all your postcodes into TextPad.  Then do a regular expression search/replace for "$" replacing with ",".  This will put a comma at end of each line:
 
  • PA11,
  • PA12,
  • PA13,
  • PA14,
Remove last comma.
 
Now to concatenate, you can either do it manually, or use the TextPad macro "Carriage return remove" from here. You should end up with; PA11,PA12,PA13,PA14
 
Note
: this setup of filtering only currently works with ProductMatrix v11.1 and above. It is shortly to be rolled out on other commercial extensions such as Premium MatrixRate.

No Import Button To Upload CSV File


  • If you change Current Configuration Scope to your website you will then see the import button.

Excel Leading Zero


By default excel will trim the leading zeros from numeric values which is not very helpful if you are trying to set up zip code logic.

To stop excel doing this follow these steps:

Create a new numeric format by:

  1. Holding Ctrl + 1
  2. Under category click "custom"
  3. Put "0"# in the type field (or if you want to have more than one leading zero enter "000"#)
  4. Click OK when done.

Now select the applicable cells (probably your entire zip to / from column) and apply this new format.

 

Exporting The CSV File


Note: This example is using Product Matrix. The only way to export the CSV is through phpMyAdmin or similar. See the below article for an alternate solution.
 
You need to find the table called shipping_productmatrix and click on it. You then need to find the export tab at the top of the page and select the export as CSV option. Please see the attached screen shot for the settings you should have.Screen shot 2 shows you what to expect.
 
When you export the file you will need to remove the columns: "pk", "website" and "cost" from the CSV file.
 
You will also need to change the region codes back to region names. If there is a "0" in the region column you need to delete this as Magento will see it as an invalid code when uploading.

You should end up with a CSV file similar in layout to screen shot 3. The final layout should be like the attached CSV file Product_Matrix.csv. You may need to re-arrange some of the columns.

 
 

 

Locating The Backup CSV File


Every time you upload a CSV file to ProductMatrix (v16.11 or greater), Premium MatrixRate (v4.7 or greater) or ShippingOverride (v3.9 or greater) a backup of that file is saved to your file system. This can be found under <Magento Folder>\var\export\your_csv_file_name.csv

Therefore if you've misplaced your CSV file and need to edit your rates just take a copy of this file, edit it and reupload it to your extension. No need to re-create your CSV file or look in the database.

 

Post/Zip Code Filtering Not Working


If you are using a shipping extension with post/zip code pattern matching and it is not functioning as expected please ensure you have the option "Use Post/Zip code range" from under " Configuration > Shipping Methods > WebShopApps xxxxx " set appropriately.

If you are using zip ranges - e.g. in USA or Australia such as 6550-700 then "Use post/zip code range" should be set to YES, otherwise it should be NO.

If it is still not working please ensure you are using the correct column in the CSV file, which is "Zip/Postal Code From" and "Zip/Postal Code To" - which is usually column "D".

Users in the UK (and Canada) can use the UK postcode filtering option.

 

Not getting rates defined in csv but instead getting $0.00


This issue usually occurs when there is an issue around the formatting of your csv file.
 
Make sure you have not placed currency symbols in the shipping price column and that you have used the correct csv template with right amount of columns for your particular extension.
 
 
 

ċ
Product_Matrix.csv
(0k)
Unknown user,
Jan 11, 2011, 7:41 AM