[Knowledge Base] Most Popular Articles

Installation of extension through MagentoConnect fails

Tue, 22 Dec 2009 02:49:51 GMT

If you get the following or similar error message: Failed to download magento-community/Unirgy_Giftcert within preferred state "stable", latest release is version 0.9.4, stability "beta", use "channel://connect.magentocommerce.com/community/Unirgy_Giftcert-0.9.4" to install Cannot initialize 'channel://connect.magentocommerce.com/community/Unirgy_Giftcert', invalid or missing package file Install Errors Package "channel://connect.magentocommerce.com/community/Unirgy_Giftcert" is not valid PEAR ERROR: install failed Add "-beta" suffix to the extension key for install, like this: magento-community/Unirgy_Giftcert-beta

My vendors do not receive new order notifications and don't see new orders in their interface

Wed, 03 Feb 2010 09:56:34 GMT

Most common causes for that: 1. Orders not reaching the status configured in System > Configuration > Drop Shipping > Vendor Options > Make Available to Dropship on Order Status(es). For example, you're testing with Check/MO payment method, which leaves order in status "Pending", with default configuration of making orders available to dropshippers on "Processing". In this particular case, creating an invoice for the order would bring it to "Processing" and fire up vendor notifications. You'll need to figure out on what stage you want your vendors to receive the notifications, and update the configuration accordingly. 2. Orders were made not using Dropship or Dropship Split shipping methods. If the regular Magento shipping methods are enabled (flat rate, UPS, FedEx, etc), and customer used them to complete the order, the order will not be processed sing Dropship logic, and the notifications will not be sent to vendors.

How to disable/uninstall uDropship extension

Tue, 10 Aug 2010 11:19:31 GMT

These steps are required to disable the extension:

1. Remove shipping carrier configuration values from database:

DELETE FROM `core_config_data` WHERE `path` LIKE 'carriers/udropship/%' OR `path` like 'udropship/%';

2. Delete product Dropship attributes in Admin > Catalog > Product Attributes.

DELETE FROM `eav_attribute` WHERE `attribute_code` LIKE 'udropship_%';

3. Disable the extension in configuration:

Edit app/etc/modules/Unirgy_Dropship.xml and change "true" to false.

Repeat for any Unirgy_Dropship*.xml add-on file in the folder.

4. Refresh Magento cache, log out from admin and re-login.

It is not required to remove any files to fully disable extension funcitonality.

The following steps are optional for uninstallation, but required before future re-installation of the extension and add-ons:

5. Delete all udropship tables:

-- if you have uMicrosite add-on installed:
ALTER TABLE admin_user DROP FOREIGN KEY FK_ADMIN_USER_VENDOR;
DROP TABLE IF EXISTS udropship_vendor_registration;

DROP TABLE IF EXISTS udropship_label_batch;
DROP TABLE IF EXISTS udropship_label_shipment;
DROP TABLE IF EXISTS udropship_vendor_shipping;
DROP TABLE IF EXISTS udropship_vendor_product;
DROP TABLE IF EXISTS udropship_vendor_statement;
DROP TABLE IF EXISTS udropship_vendor;
DROP TABLE IF EXISTS udropship_shipping_method;
DROP TABLE IF EXISTS udropship_shipping_website;
DROP TABLE IF EXISTS udropship_shipping;

6. Delete reference to extension's DB resources:

DELETE FROM core_resource WHERE code in ('udropship_setup', 'umicrosite_setup',
'udmulti_setup', 'udsplit_setup', 'udmrate_setup', 'udlocator_setup');

7. Refresh Magento cache, log out and re-login to admin

How to configure Magento to have subdomains for each vendor

Tue, 29 Dec 2009 23:46:04 GMT

1. Configure webserver to point all subdomains to Magento root. 2. Make wildcard DNS to point all subdomains to the same server, or add subdomains to DNS for every new vendor, depends on how often you have new vendor registrations. 3. Set Admin > System > Configuration > Web > Default Pages > Homepage = "umicrosite"

What is the correct sequence of uDropship extension installation?

Tue, 22 Dec 2009 01:52:58 GMT

1. Upload the license file to Magento root. 2. Unpack and upload archives downloaded from provided links to Magento root. 3. If Magento Cache is enabled, refresh it. 4. If Flat Product Catalog enabled, refresh it. 5. Log out from Magento admin and re-login.

Making Dropship work with GoogleCheckout

Tue, 22 Sep 2009 08:28:59 GMT

Configuration:

Go to Admin > System > Configuration > Google API > Shipping - Merchant Calculated
Enable Merchant Calculated rates
Add all Dropship Shipping Methods

There are few bugs in Magento 1.3.2.3 that prevent Dropship from working with GoogleCheckout. Here are the changes that need to be done to make it work correctly:

Edit app/code/core/Mage/Shipping/Model/Shipping.php

Around line 175:


// ADD:
$request->setAllItems($address->getAllItems());
// RIGHT BEFORE:
return $this->collectRates($request);

Edit app/code/core/Mage/GoogleCheckout/Model/Api/Xml/Callback.php

Around line 141:


// ADD:
$limitCarrier = array_unique($limitCarrier);
// RIGHT BEFORE:
foreach($googleAddresses as $googleAddress) {

Around line 163:


// COMMENT OUT:
#$address->setCollectShippingRates(true)->collectShippingRates();

Around line 245:


// RIGHT AFTER:
    $result->SetShippingDetails($methodName, $rates[$methodName], "true");
    $merchantCalculations->AddResult($result);
}
// ADD: 
else {
    $result->SetShippingDetails($methodName, 0, "false");
    $merchantCalculations->AddResult($result);
}

Even if all is configured and coded correctly, you still might experience issues with GoogleCheckout, because of hardcoded 3 second timeout for merchant calculation API callback, if your vendors are using external API to calculate rates, such as UPS, USPS, FedEx.

When using pear from shell php not found

Sat, 20 Jun 2009 09:20:06 GMT

When trying to run ./pear you get this or similar error message:

$ ./pear mage-setup
Running initial setup...
exec: 94: php: not found

The issue is that each *NIX setup can have PHP executable located in different place, and you will need to edit ./pear file to accomodate this. Just replace:

MAGE_PEAR_PHP_BIN="/usr/local/bin/php"

With your location of PHP CLI executable and you should be good to go. Another thing to watch is that your PHP CLI should have the same configuration and php extensions as PHP used in webservice, to avoid issues with PEAR package php extension dependencies.

Vendors do not receive notifications and do not see the orders in vendor interface.

Sat, 05 Dec 2009 22:43:07 GMT

There are few configuration issues to check:

Shipping carriers other than "Drop Shipping" are enabled.
When customer make an order with a regular Magento system shipping carrier directly (i.e. UPS, USPS, FedEx, FlatRate, FreeShipping, etc.), the order does not pass through dropship logic, and no related records are generated in database. Make sure that only "Drop Shipping" (or "Drop Shipping (Split), if you have this add-on installed") carrier is enabled.
The order did not reach one of a configured statuses to become available for dropship vendor.
There's a configuration that allows store owner to decide at which stage the orders are automatically available to dropship vendors.

Admin > System > Configuration > Drop Shipping > Vendor Options > Make Available to Dropship on Order Status(es)

The notifications will be sent to vendors and be available in the vendor interface only when the orders will reach one of selected statuses. The notifications will be sent only once per order.

Example: the store is configured to use an offline payment method (Check/MO) and when the order comes in, it has "Pending" status, until an invoice is generated and order becomes "Processing" or "Complete". By default dropship is configured to become available to vendors on order status "Processing" only, and will trigger only when the invoice is generated. If you'd like the order to become available to dropship right away, you'll need to add "Pending" status in the configuration.

Printing labels using thermal printer

Sat, 12 Dec 2009 12:15:05 GMT

If a vendor is configured to print EPL (thermal) shipping labels, by default you'll just see a download with extension .EPL To configure your computer to print the labels automatically on the thermal printer, follow these instructions (Windows only): 1. Share a locally connected USB thermal printer using Windows Sharing, and give the shared printer a meaningful name (ex. LP2844) 2. Create a batch file, for example print.bat, with this line: COPY %1 \\MYCOMPUTER\LP2844 Where MYCOMPUTER is the name of your computer and LP2844 is the name of the printer share you've created in step 1. 3. When you have downloaded .EPL file, choose to open it using the .bat file you've created in step 2. 4. Additionally, you could create a Windows association of .EPL files with print.bat file.

The labels are not attached to vendor notification emails

Thu, 12 Nov 2009 14:27:04 GMT

Check the following configurations:

Global configuration:
- System → Configuration → Drop Shipping → Vendor Options → Attach Shipping Label to Vendor Notification = Yes
Vendor configuration (if the problem is vendor specific):
- Vendor Information → Used Carrier - should be one of Fedex, UPS, USPS
- Preferences → Integration → Attach Shipping Label to Notifications = Yes
- Preferences → Shipping Labels → Label Type - should be one of PDF, EPL

Is your dropshipping extension editable? Is it open sourced or closed?

Fri, 15 Jan 2010 03:03:48 GMT

The extension contains 1 small ionCube encoded file, which contains an essential functionality, which usually does not need customization. In case the customization is still needed, I'm able to provide information about method parameters/returns and available event hooks upon request. All other code, configuration, phtml templates, email templates are open for your customization and editing.

How to change vendor interface URL from /udropship to /vendor

Wed, 10 Feb 2010 02:28:57 GMT

If you have local custom module, add this to your module's etc/config.xml, otherwise add this to app/etc/local.xml:  <frontend> <routers> <udropship> <args> <frontName>vendor</frontName> </args> </udropship> </routers> </frontend>  </config>

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'e.cost' in 'field list'

Fri, 05 Feb 2010 10:40:11 GMT

If you get this error during product save, that means the Magento flat catalog is not updated. The issue is fixed by running: System > Cache Management > Catalog > Rebuild Flat Catalog Product

Does uDropShip support buyers paying sellers directly?

Fri, 29 Jan 2010 20:56:21 GMT

The uDropship does not provide this functionality. I believe there's a good reason why most or likely no software out-of-the-box supports multiple real-time charges for the same order. I'll attempt to describe the complications of direct payment from buyer to seller. The ordering process relies on authorization/capturing of the funds before accepting the order on frontend. If the transaction succeeds, the customer sees 1 payment on the credit card statement. The store owner has now full control over payout to the vendors and withholding commissions, transaction fees or adjustments for negative customer experience when it is a vendor's fault. If the transaction fails, the order does not go through, the credit card statement does not contain any charge, the customer gets error notification and gets a chance to re-enter payment information. That is, when there's only 1 authorization/charge for the order, the whole payment goes to online store, and later distributed to the suppliers. Let's see how it will work if you want to charge for each vendor separately during the checkout. If all the transactions succeed, the customer sees a number of payments on the credit card statement for each supplier. There are few issues with that: a) Absolute majority of my clients didn't want the customers to have multiple charges on CC statement for the same order. b) If the vendor for some reason is unable to fulfill the ordered products (either not in stock, or order request was misplaced), and you want to transfer the fulfillment request to another vendor, you will have to request a refund from the vendor or chargeback the vendor payment. Both options are troublesome. c) Online store owner will have to charge the vendors for commissions, transaction fees separately, hoping that the charges will go through. If the customer's credit card is maxed out after first (few) charges, and some charges are declined, there a situation: the customer was charged partial amount, but the order didn't go through. Now you have to choose: 1. a) If you're authorizing only, cancel the authorizations. Not all payment APIs allow cancelling authorizations, relying on expiration of few days. b) If you're charging automatically, refund the successful charges and not let the order through. The refunds can take time as well, depending on payment API. While the authorization cancellation or refund processing takes its time, the customer funds are locked and he won't be able to use them for this or other transactions. This situation is highly unfavorable. 2. Let the order through and mark only the paid items as ready for fulfillment, and notify only paid vendors about the order. This option requires: a) accounts receivables management b) partial stock inventory locking for the failed part of the order c) manual or automatic handling of partial order cancellation in case the remaining payment wasn't made. There are more implications, but the ones above should show that multiple order payments will introduce a substantial overhead of handling the orders, on top of Magento customization complications.

In category view, products do not show images and are out of stock

Tue, 02 Mar 2010 07:26:01 GMT

For Magento 1.3.x run this query:


UPDATE eav_attribute SET used_in_product_listing=1 
WHERE entity_type_id IN (
  SELECT entity_type_id FROM eav_entity_type 
  WHERE entity_type_code='catalog_product'
) AND attribute_code IN (
  'name', 'description', 'short_description', 
  'price', 'special_price', 'special_from_date', 'special_to_date', 
  'image', 'small_image', 'thumbnail', 
  'status', 'tax_class_id', 'url_key', 'required_options', 
  'price_type', 'weight_type', 'price_view', 'shipment_type', 
  'image_label', 'small_image_label', 'thumbnail_label'
);

For Magento 1.4.x run this query:


UPDATE catalog_eav_attribute SET used_in_product_listing=1 
WHERE attribute_id IN (
  SELECT attribute_id FROM eav_attribute 
  INNER JOIN eav_entity_type USING(entity_type_id) 
  WHERE entity_type_code='catalog_product' AND attribute_code IN (
    'name', 'description', 'short_description', 
    'price', 'special_price', 'special_from_date', 'special_to_date', 
    'image', 'small_image', 'thumbnail', 
    'status', 'tax_class_id', 'url_key', 'required_options', 
    'price_type', 'weight_type', 'price_view', 'shipment_type', 
    'image_label', 'small_image_label', 'thumbnail_label'
  )
);

Refresh Magento cache.

How to make uDropship work with Fontis AustraliaPost shipping method?

Thu, 06 May 2010 01:28:57 GMT

Edit app/code/community/Fontis/Australia/Shipping/Carrier/Australiapost.php

Replace getAllowedMethods() method (last) with:

    public function getAllowedMethods()
    {
        return array(
            'STANDARD' => 'Standard',
            'EXPRESS' => 'Express',
            'AIR' => 'Air Mail',
            'SEA' => 'Sea Mail',
            'EPI' => 'Express Post International',
            'EPI-EC' => 'Express Post International with Extra Cover',
        );
    }

How to send vendor notifications manually on demand

Fri, 03 Sep 2010 18:33:29 GMT

First you will need to create a custom order status, that will not be a part of standard Magento sales order workflow, and enable it in order state "processing".

Edit app/etc/local.xml and add right before the last </config>:

<global> <sales> <order> <statuses> <ready_to_ship> <label>Ready To Ship</label> </ready_to_ship> </statuses> <states> <processing> <statuses> <ready_to_ship/> </statuses> </processing>  <pending> <statuses> <ready_to_ship/> </statuses> </pending> </states> </order> </sales> </global>  </config>

If you have Magento cache enabled, refresh it.

Next, configure uDropship to use this new custom order status to send the notifications to vendors.

Go to System > Configuration > Drop Shipping > Vendor Options. Find Make Available to Dropship on Order Status(es) multiselect, and choose only Ready To Ship status.

Now, when a new order comes in, to notify and make it available for vendors, you will need to change the order status manually to Ready To Ship.