doclucas

Thank you. What about restricting shipping methods?

What do your php error log, mysql error log and apache error logs show? Also, did you try disabling MemCached and check?

Where or how can I set products cost (the cost I paid for them before reselling)? It will make managing selling prices and managing profitability calculations a lot easier. Thank you

Is there any add-on that shows real-time users' activity like this (attached image)? It also shows the browser used, referrer, country flag, map location, number of orders (in the bracket, for registered customers), shopping cart content, when clicking the session link (second attachment) - it shows a full trace history of all the pages/actions of that session/IP. Thank you

Hi, Is there any recommended order editor add-on that can also connect to other pre-installed shipping modules (such as DHL/UPS/FedEx real-time services) and fetch the new shipping rates of an order being edited. For example, if I have an order that the customer selected DHL shipping and got the real-time rates from DHL during checkout, when I edit the order, if I change quantities, the measurements and weights of the order may change, and the shipping rate should change accordingly. And/or if the customer wishes to change a shipping method after he placed the order, I edit the order and change to UPS real-time rates method and the rates will be updated accordingly. Is there anything like this? Thank you

Hi, Is there any way or any recommended add-on/s to configure PS 1.7 to restrict specific customer from using specific payment method/s and/or specific shipping method/s? Thank you

Of course I agree, Fabien Good luck with the re-development, it should be quite easy, as long as you set debugging on (and output XML request/response to header), use a developer FedEx account/meter etc. you will be able to make this FedEx module back to proper functionality quite quickly.

Fabien, you will have to debug the module. The problem is not in the wsdl, the problem is in the XML request that the module is sending. Frankly, I am not using presta or this fedex module, so I can't debug this myself, but since I developed the osCommerce FedEx module I was just curios to see how it works on Presta, and I can assure you that if the module is sending PurposeOfShipmentType, then it's not really necessary in the XML request, so you should read the documentation and see what the XML request really require in your own ship scenarios and change the code accordingly. It will probably require proper debugging and re-development of the code, but if you are familiar with PHP and XML, it should be quite simple, as long as you do read the documentation. Maybe then you can share your fixed/updated module with the community

Yes, Fabien, this is a fix to the built in module in v1.6 By the way, the v10 wsdl and v13 are not much different and it's perfectly fine to use v10. p.s. sorry for the late response, I am subscribed to the thread, but for some reason didn't get any email notification...(?)

Here is the solution for error 868: http://www.prestashop.com/forums/topic/323053-fedex-carrier-module-error-868-service-not-allowed-how-to-fix/

Here is the solution: http://www.prestashop.com/forums/topic/323053-fedex-carrier-module-error-868-service-not-allowed-how-to-fix/

By the way, very important note, you must properly setup and enable the same currency in your shop's backoffice (Admin -> Localization -> Currencies) of your country, to be able to use this module outside the USA. That's because FedEX sends the XML response with a price using your own currency, something like this: ... <Currency>SGD</Currency> <Amount>65.02</Amount> ... In this case, the quote is in Singapore dollars, and you must have SGD currency properly configured in your back office, or else the front office will not show the FedEx module at all. If the currency is properly configured, you will get real time quotes, anywhere in the world. Hope I explained this well enough.

Here is a fix: http://www.prestashop.com/forums/topic/323053-fedex-carrier-module-error-868-service-not-allowed-how-to-fix/

Here is a (free) fix: http://www.prestashop.com/forums/topic/323053-fedex-carrier-module-error-868-service-not-allowed-how-to-fix/

I was just looking for solution to this problem and bumped into this thread: http://www.prestashop.com/forums/topic/173948-fedex-carrier-module-error-868-service-not-allowed/ All I have to say is...Mike Kranzler, are you out of your mind????!!! First, the guy clearly explains the issue and pointed to the direct problem. You eventually *lock* the thread with this comment: "Since this is not an issue with PrestaShop, but a request to circumvent another company's own rules, I am locking this thread" The official module has this problem, and nobody can use it except for people in the USA because of the way it was written, it has a built in bug that doesn't allow it to be activated! I can't believe it has not been identified and fixed until now, but with moderators like this, no wonder... Here is the solution/workaround: in /modules/fedexcarrier/fedexcarrier.php Find $request['RequestedShipment']['Recipient']['Address'] = array('StreetLines' => Configuration::get('FEDEX_CARRIER_ADDRESS1'), 'City' => Configuration::get('FEDEX_CARRIER_CITY'), 'StateOrProvinceCode' => $shipper_state['iso_code'], 'PostalCode' => Configuration::get('FEDEX_CARRIER_POSTAL_CODE'), 'CountryCode' => $shipper_country['iso_code']); Replace with: // $request['RequestedShipment']['Recipient']['Address'] = array('StreetLines' => Configuration::get('FEDEX_CARRIER_ADDRESS1'), 'City' => Configuration::get('FEDEX_CARRIER_CITY'), 'StateOrProvinceCode' => $shipper_state['iso_code'], 'PostalCode' => Configuration::get('FEDEX_CARRIER_POSTAL_CODE'), 'CountryCode' => $shipper_country['iso_code']); $request['RequestedShipment']['Recipient']['Address'] = array('StreetLines' => 'Av. Mouzinho de Abuquerque C.C. Premar Lj. 95', 'City' => 'Povoa de Varzim', 'StateOrProvinceCode' => '', 'PostalCode' => '4490409', 'CountryCode' => 'PT'); This disabled the first $request line and replaces it with a line that does not use the same (shipper's) address, so you will no longer get any error when trying to activate the module. You can basically change the address in the array to any valid address that you wish, but this one will work, as long as you don't reside/ship-from PT (Portugal).