Git Product home page Git Product logo

netresearch / dhl-module-shipping-m2 Goto Github PK

View Code? Open in Web Editor NEW
30.0 25.0 21.0 1.86 MB

This extension is in legacy status since 04/2020 and will run out of maintenance and support after a short transition period. You can find the official replacement extension here https://github.com/netresearch/dhl-shipping-m2. It includes the latest and greatest possible range of functions that DHL is currently offering.

PHP 86.75% JavaScript 5.81% HTML 7.11% CSS 0.34%

dhl-module-shipping-m2's Introduction

Warning: This extension is no longer supported and should not be used. You can find the official replacement extension here on GitHub

DHL Shipping Extension

The DHL Shipping extension for Magento® 2 integrates the DHL Business Customer Shipping API or the DHL eCommerce Global Label API into the order processing workflow.

Description

This extension enables merchants to request shipping labels for incoming orders via the DHL Business Customer Shipping API (DHL Geschäftskundenversand-API) or the DHL eCommerce Global Label API.

For more details on the API connections, see the documentation.

Requirements

  • PHP >= 7.0.6
  • PHP >= 7.1.0
  • PHP >= 7.2.0
  • PHP >= 7.3.0

Compatibility

  • Magento >= 2.2.4
  • Magento >= 2.3.0

Installation Instructions

Install Source Files

The DHL Shipping module for Magento® 2 can be installed from the following sources:

Integrators

As an integrator you installed Magento using Composer and acquired the DHL Shipping module on Magento Marketplace (free of charge).

The Composer repository https://repo.magento.com/ is declared in your root composer.json which allows you to directly install the module like this:

composer require dhl/module-shipping-m2

During installation, Composer might ask for a user and password. You must use the public and private key of the Magento Marketplace user which was used to purchase the module.

Developers

If you want to contribute to the module, you can declare the GitHub repository in your root composer.json and install the module like this:

composer config repositories.dhl-shipping-m2 vcs https://github.com/netresearch/dhl-module-shipping-m2.git
composer require dhl/module-shipping-m2

Enable Module

Once the source files are installed, make them known to the application:

./bin/magento module:enable Dhl_Shipping
./bin/magento setup:upgrade

And finally: flush the cache, compile, and deploy the static content:

./bin/magento cache:flush
./bin/magento setup:di:compile
./bin/magento setup:static-content:deploy <list_of_locales>

The list of locales could be something like: en_US en_GB fr_FR de_DE it_IT

Uninstallation

The following sections describe how to uninstall the module from your Magento® 2 instance.

Composer

To unregister the shipping module from the application, run the following command:

./bin/magento module:uninstall --remove-data Dhl_Shipping
composer update

This will automatically remove source files, clean up the database, update package dependencies.

Manual Steps

To uninstall the module manually, run the following commands in your project root directory:

./bin/magento module:disable Dhl_Shipping
composer remove dhl/module-shipping-m2

To clean up the database, run the following commands:

DROP TABLE `dhlshipping_quote_address`, `dhlshipping_order_address`;
DROP TABLE `dhlshipping_quote_address_service_selection`, `dhlshipping_order_address_service_selection`;

DELETE FROM `eav_attribute` WHERE `attribute_code` IN ('dhl_dangerous_goods_category', 'dhl_tariff_number', 'dhl_export_description');

ALTER TABLE `quote` DROP COLUMN `dhl_service_charge`, DROP COLUMN `base_dhl_service_charge`;
ALTER TABLE `quote_address` DROP COLUMN `dhl_service_charge`, DROP COLUMN `base_dhl_service_charge`;
ALTER TABLE `sales_order` DROP COLUMN `dhl_service_charge`, DROP COLUMN `base_dhl_service_charge`;
ALTER TABLE `sales_invoice` DROP COLUMN `dhl_service_charge`, DROP COLUMN `base_dhl_service_charge`;
ALTER TABLE `sales_creditmemo` DROP COLUMN `dhl_service_charge`, DROP COLUMN `base_dhl_service_charge`;
DELETE FROM `core_config_data` WHERE `path` LIKE 'carriers/dhlshipping/%';
DELETE FROM `setup_module` WHERE `module` = 'Dhl_Shipping';

Support

In case of questions or problems, please have a look at the Support Portal (FAQ) first.

Also check the user documentation.

If the issue cannot be resolved, you can contact the support team via the Support Portal or by sending an email to [email protected].

Developer

License

OSL - Open Software Licence 3.0

Copyright

(c) 2019 DHL Paket GmbH

dhl-module-shipping-m2's People

Contributors

andreasmueller75 avatar gewaechshaus avatar magicsunday avatar mam08ixo avatar moehrenzahn avatar ngolatka avatar powli avatar sebastian80 avatar tuunit avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dhl-module-shipping-m2's Issues

Column 'adress_id' cannot be null

Bug description
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'adress_id' cannot be null, query was: INSERT INTO "dhlshipping_quote_adress" (adress_id, info) VALUES (?,?)

Steps to reproduce
To reproduce the problem:

  1. Sadly I can not reproduce this yet. A user reported it with the above error as a quote.
  2. I'll try to find out more by playing around with the specific user's address. It may be related to migrated customer address entries from Magento 1.9 using the Magento migration tool.

Expected behavior
Add the expected behavior. In other words: what SHOULD happen, but doesn't.

Screenshots / logs

I was only able to activate logging after the fact. So this ticket may stay open for a while until either other users with the same error message can chime in or this happens again and I can provide more details.

Environment

  • Magento version: 2.2.6
  • PHP version: 7.1
  • Module version: 0.9.1

FAQ
Has the Knowledge Base been checked for a solution?

  • Yes, but couldn't find anything
  • Yes, but solution did not work

IMPORTANT: Before creating an issue

Before creating a Github issue, please think about the following:

  • Do you have a general question (module integration, configuration, usage, workflow)? Then please look into the Support Portal (Knowledge Base) first, and do not create a Github issue.
  • You can make a support request here.
  • Did you find a bug in the code? Or do you have a suggestion for an improvement? Then go ahead and create an issue here. Going through the Support Portal is also fine.
  • FYI: The module documentation can be found here (English) and here (German).

Missing source class

Hey netresearchers,

under MCE2.2.0 and php7.1 there's is the following error coming up while running setup:di:compile.
Installed the 0.6.0 archive in app/code... (I know 2.2.0/7.1 aren't officially supported)

[RuntimeException]
Source class "\Dhl\Shipping\Webservice\AppData" for "Dhl\Shipping\Webservice\AppDataMapper" generation does not exist.

Grüße
Jan

Problem with shipping label creation if streetname and housenumber are not seperated by space

if the customer enters his address without a space between streetname and housenumber (for example Thisisastreetname.30) - which is allowed by form validation of Magento 2.x - then if you try to create a shipping-label in the backend the module produces a error with following message:
"Shipping labels could not be created: Hard validation error occured. Bitte geben Sie eine Hausnummer an. Die eingegebene Adresse ist nicht leitcodierbar. Bitte geben Sie eine Hausnummer an."

If you enter a space then it works. Also if problem can be temporarely fixed if the backend user modifies the address the module should be capable to to this automatically.

used Magento Version: CE 2.2.1

Update:
http://dhl.support.netresearch.de/support/solutions/articles/12000036090-was-bedeutet-die-meldung-street-number-is-a-required-value-

But in germany it's quite common that users do not enter the space after the streetname.

Greetings,
Marc

What test data to use?

What test data for system configuration should I use? In order to generate a shipping label I need a valid IBAN, BIC etc. The module is set to sandbox mode. Thanks :-)

Missing GlRestClientInterface

while installing get this error:

PHP Fatal error: Interface 'Dhl\Shipping\Webservice\Client\GlRestClientInterface' not found in /xxxxx/htdocs/app/code/Dhl/Shipping/Webservice/Client/GlRestClient.php on line 45

Exception #0 (Magento\Framework\Exception\NoSuchEntityException): Angeforderter Store wurde nicht gefunden.

Re: DHLSUP-1046263: website/store verwechslung

DHL Support (Netresearch) [email protected]
18:29 (vor 0 Minuten)
an mich

Thank you, we have received your request and will get back to you shortly. Your ticket number is DHLSUP-1046263.

-—————————

Vielen Dank, Ihre Anfrage ist bei uns eingegangen. Wir melden uns in Kürze bei Ihnen. Ihre Ticket-Nummer ist DHLSUP-1046263.

-—————————

Netresearch DTT GmbH
Nonnenstraße 11c – 04229 Leipzig – Germany
Registergericht: AG Leipzig HRB 34690
Geschäftsführer: Thomas Wilhelm

Netresearch GmbH & Co. KG
Nonnenstraße 11d – 04229 Leipzig – Germany
Registergericht: AG Leipzig HRA 15614
Komplementär: Netresearch Beteiligungs GmbH, AG Leipzig HRB 17018
Geschäftsführer: Thomas Fleck

Matthias Büsing wrote:

Moin,
ich habe einen kleiner aber sehr nervigen Bug gefunden im DHL Modul für Magento 2.
Magento ist Version 2.2.6, DHL Modul hat Version 0.9.1

Exception wird geworfen:
1 exception(s):
Exception #0 (Magento\Framework\Exception\NoSuchEntityException): Angeforderter Store wurde nicht gefunden.

Stack Trace:

Exception #0 (Magento\Framework\Exception\NoSuchEntityException): Angeforderter Store wurde nicht gefunden.
#0 /home/matthias/htdocs/XXX/vendor/magento/module-store/Model/StoreManager.php(171): Magento\Store\Model\StoreRepository->getById('6')
#1 /home/matthias/htdocs/XXX/vendor/dhl/module-shipping-m2/Model/Config/ConfigAccessor.php(116): Magento\Store\Model\StoreManager->getStore('6')
#2 /home/matthias/htdocs/XXX/vendor/dhl/module-shipping-m2/Model/Config/ModuleConfig.php(114): Dhl\Shipping\Model\Config\ConfigAccessor->getConfigValue('shipping/origin...', '6')
#3 /home/matthias/htdocs/XXX/vendor/dhl/module-shipping-m2/Model/Config/ModuleConfig.php(348): Dhl\Shipping\Model\Config\ModuleConfig->getShipperCountry('6')
#4 /home/matthias/htdocs/XXX/vendor/dhl/module-shipping-m2/Block/Adminhtml/System/Config/Form/Field/ApiType.php(87): Dhl\Shipping\Model\Config\ModuleConfig->getApiType('6')

Geht los bei:
Dhl\Shipping\Block\Adminhtml\System\Config\Form\Field\ApiType
in Zeile 86 wird die website-ID aus den GET Parametern geholt, in Zeile 87 wird damit die Methode getApiType angesprochen.
Diese erwartet jedoch eine store-ID und dann sol im weiteren Verlauf dann der Store mit der Webseiten-ID geladen werden.
Das fällt nicht weiter auf, solange die Website mit der 1 geladen werden soll, denn meist gibt es ja auch den Store 1.
In unserem Fall aber nicht - und darum geht das ganze kaputt.

Das Ganze lässt sich so replizieren:
AdminPanel>Shops>Konfiguration>Umsatz>Versandmethoden und dort einmal über die StoreView Auswahl einen Webseite auswählen die nicht die 1 ist.

in unserem Fall sieht man dann in der URL: /website/6/

Wäre schön, wenn Sie das einmal prüfen und ggf. ASAPST fixen könnten. Danke.

Falsche Produktauswahl bei Label Internation

Hallo @ngolatka,

folgendes ist mir aufgefallen:

Wir haben in der Konfiguration -> Participation Numbers folgende Produkte analog zu den bestehenden Verträgen hinterlegt:

DHL Paket - V01PAK - Participation: 01
DHL Paket International - V53WP - Participation: 01

Wenn wir ein internationales Label drucken wollen (in dem Beispiel Belgien als Empfängerland), steht aber links im Dropdown nur DHL Paket Connect zur Verfügung. Das Label lässt sich logischerweise nicht anlegen.

Die EKP wurde im Beispiel angepasst auf 1122334455

Shipping labels could not be created: Invalid XML: cvc-length-valid: Value '112233445555' with length = '12' is not facet-valid with respect to length '14' for type '#AnonType_billingNumberAbstractShipmentType'.

Der korrekte Wert der Anfrage müsste ja
11223344555301
sein, was auch der korrekten Zeichenzahl von 14 entspricht. Stattdessen erfolgt der Aufruf von Paket Connect ohne participation number, aber das siehst du ja selber...

Beste Grüße
Jan

Partial shipment

I stumbled upon this some time ago, so I think this isn't version related in case of M2. I even don't know if this is a bug or not.

If you try to make a partial shipment, f.e. you have 3 items and want to ship out 2 in stock, you can't click on the save button, it stays disabled. The result is, you have to manage partial shipments externaly etc. I didn't review the code, just want to report it.

Cheers
Jan

hallo

ich habe module unter PHP 5.6.5, 5.6.30, PHP 7.0.18 durch composer installiert. Installation ging problemlos. In Admin Panel, wie beschrieben, habe ich Module mehrmals mit Zugangsdaten von Intraship und Geschäftskundenportal getestet. Unter dem Rubrik von Order kommt keine Option DHL versenden.
Test war unter Magento 2.1, 2.1.4 und 2.1.6. Immer gleich, keine Option.
die vorgänger Version für Intraship läuft unter 1.9 bis 1.9.3.2 fehlerfrei.
Trotz Aktivierung Log-Level erzeugt kein Logdatei.
Berechtigung für media, vendor, var waren 644 bis 777 gestellt.
Die Daten sind mal wie DHL-Geschäftkundenportal und mal Intraship eingetragen

Mit freundlichen Grüssen

Cannot install DHL module 0.9.1 with lib-shipping-mx 0.10.0

Bug description
The dhl-module-shipping-m2 0.9.1 cannot be installed with the currently available lib-shipping-mx 0.10.0.

This results in PHP Fatal Errors during installation, for example:

PHP Fatal error: Declaration of Dhl\Shipping\Webservice\Client\BcsSoapClient:: getVersion(Dhl\Shipping\Bcs\Version $request) must be compatible with Dhl\Shipping\Webservice\Client\BcsSoapClientInterface:: getVersion(Dhl\Shipping\Webservice\Schema\Bcs\Version $part1)
...


Cause
This is a known problem. Because of the too loose version requirements in the composer.json of dhl-module-shipping-m2, Composer tries to install lib-shipping-mx 0.10.0, which is unfortunately too new and not backwards compatible.

Library version 0.9.0 is needed for dhl-module-shipping-m2 0.9.1


Workaround option 1
Requiring "dhl/lib-shipping-mx": "0.9.0" explicitly in the project's root composer.json lets you get around this problem, so you can install the DHL module.

Workaround option 2
Instead of using the Github repository, install the module and the library using these ZIP files:

Follow the instructions in the README.md chapter "Installation Instructions -> Artifact".

Workaround option 3
Install the DHL module using Packagist. Do not execute this command:
composer config repositories.dhl-lib-shipping vcs https://github.com/netresearch/dhl-lib-shipping-mx.git
The library 0.10.0 has been delisted from Packagist. You will therefore get library version 0.9.0, which works.


Clean solution
As soon as dhl-module-shipping-m2 0.10.0 is released, the above problem will disappear. We are working on that release together with DHL with high priority, see issue #44.


And finally:
We're really sorry for the trouble this may cause! Contact our support if you have any questions.

Setup:di:compile Error

Bug description
Add your description here. Include all the essential information.
When running setup:di:compile i get Fatal php error

Steps to reproduce
To reproduce the problem:

  1. Clean Magento 2.2.5 install

  2. composer config repositories.dhl-module-shipping-m2 vcs https://github.com/netresearch/dhl-module-shipping-m2.git
    composer config repositories.dhl-lib-shipping vcs https://github.com/netresearch/dhl-lib-shipping-mx.git
    composer require dhl/module-shipping-m2:0.9.0

  3. ./bin/magento module:enable Dhl_Shipping
    ./bin/magento setup:upgrade

  4. ./bin/magento setup:di:compile

Both directories exist:
vendor/dhl/module-shipping-m2
vendor/dhl/lib-shipping-mx

Error:
PHP Fatal error: Class 'Task' not found in /var/www/html/magento2/vendor/dhl/module-shipping-m2/build/tasks/DockerProperties.php on line 28

Expected behavior
compilation works...

Screenshots / logs
If possible, add screenshots or logs to clarify your problem.
image

Environment

  • Magento version: 2.2.5
  • PHP version: 7.1.12
  • Module version: 0.9.0

FAQ
Has the Knowledge Base been checked for a solution?

  • [x ] Yes, but couldn't find anything
  • Yes, but solution did not work

Is the DHL API down?

This is not a real issue, more like a general FYI for everyone:

If you are wondering "Is the DHL API down?", have a look at this article in the Knowledge Base.

It shows the status of the sandbox and production APIs for:

  • DHL Business Customer Shipping (used for creating shipping labels)
  • Parcelmanagement API (for additional DHL services in the checkout)

Hint: You can also register in the DHL Developer Portal to get notified via email about outages and upcoming changes.

Label sizes [feature request]

Hi @ngolatka,

are there plans to implement different output sizes for the generated pdf labels like in the M1 version?
If not, we would like to request that feature for clients using label printers.

Cheers
Jan

Feature Request: Tare weight

Feature description
Add an option "tare weight" for packaging that is added to all orders.

Reason
Magento itself only offers this option in the "Magento Shipping" part that is not offered in Europe and probably not compatible with DHL anyway.
So it can currently only exist in the shipping module itself.

If a merchant sells small items (in my case lightweigh sets of playing cards)
that are sold in quantities >1
then adding the weight of the packaging to each item is exsessive.

Additional context
A custom item "packaging" added to each shopping card can always be removed by the user.

feature request: "street.nr"

Feature description
"xyzstrasse 12" is supported.
The format "xyzstr.12" should also be supported.

Reason
It is a format users in Germany like to enter and this module failed to find the separation between street-name and house number

Uninstaller does not seem to work

Magento Version 2.2.0

$ ./bin/magento module:uninstall --remove-data Dhl_Shipping
You are about to remove code and/or database tables. Are you sure?[y/N]y
Enabling maintenance mode
You are removing data without a database backup.
Removing data of Dhl_Shipping
PHP Fatal error:  Uncaught TypeError: Argument 1 passed to Magento\Eav\Setup\EavSetup::__construct() must implement interface Magento\Framework\Setup\ModuleDataSetupInterface, instance of Magento\Setup\Module\Setup given, called in /home/self/example/workspace/example.de/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 111 and defined in /home/self/example/workspace/example.de/vendor/magento/module-eav/Setup/EavSetup.php:88
Stack trace:
#0 /home/self/example/workspace/example.de/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php(111): Magento\Eav\Setup\EavSetup->__construct(Object(Magento\Setup\Module\Setup), Object(Magento\Eav\Model\Entity\Setup\Context), Object(Magento\Framework\App\Cache\Proxy), Object(Magento\Eav\Model\ResourceModel\Entity\Attribute\Group\CollectionFactory))
#1 /home/self/example/workspace/example.de/vendor/magento/framework/ObjectManager/Factory/Dynamic/Developer.php(66): Magento\Framework\ObjectManager\Factory\AbstractFactory->createObject('Ma in /home/self/example/workspace/example.de/vendor/magento/module-eav/Setup/EavSetup.php on line 88

Can't install with PHP 7.2.13

Bug description
Can't install the version 0.10.0 via VCS eventhough my PHP version is 7.2.13

Steps to reproduce
To reproduce the problem:

  1. Run command composer require dhl/module-shipping-m2:0.10.0
  2. An error is displayed and installation fails

Expected behavior
Should install successfully since I have PHP version 7.2.13

Screenshots / logs
[InvalidArgumentException]
Could not find package dhl/module-shipping-m2 in any version matching your PHP version (7
.2.13)

require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-suggest] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--update-with-all-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--] []...

Environment

  • Magento version: Magento ver. 2.3.0
  • PHP version: PHP 7.2.13
  • Module version: 0.10.0
  • OS: CentOS

FAQ
Has the Knowledge Base been checked for a solution?

  • [ x ] Yes, but couldn't find anything
  • [ ] Yes, but solution did not work

Release 0.10.0 breaks SOAP and REST schema generation in Magento

Bug description

After upgrading from the 0.9.x release to 0.10.0 all SOAP and REST APIs are broken.
Removing the /vendor/dhl/module-shipping-m2/etc/webapi.xml file solves the problem
as a temporary workaround.
(Update: That workaround may break the checkout process. Not confirmed yet.)

Steps to reproduce
To reproduce the problem:

  1. Upgrade to dhl/module-shipping-m2 0.10.0 and dhl/lib-shipping-mx 0.10.2
  2. Open https://(Magento2)/swagger/ as a simple test

Expected behavior
swagger opens and presents the APIs available to the given api key or the anonymous user

Screenshots / logs
instead var/log/exceptions.log shows this:
[2019-03-09 16:43:48] main.CRITICAL: Report ID: webapi-5c83ed448f3c4; Message: Class "ServiceInputInterface[]" does not exist. Please note that namespace must be specified. {"exception":"[object] (Exception(code: 0): Report ID: webapi-5c83ed448f3c4; Message: Class "ServiceInputInterface[]" does not exist. Please note that namespace must be specified. at /vendor/magento/framework/Webapi/ErrorProcessor.php:205, LogicException(code: 0): Class "ServiceInputInterface[]" does not exist. Please note that namespace must be specified. at /vendor/magento/framework/Reflection/TypeProcessor.php:140)"} []

The cause seems to be the Dhl\Shipping\Api\Data\Service\ServiceInputInterface class
that belongs to dhl-lib-shipping-mx

Environment

  • Magento version:
  • PHP version: 7.1
  • Module version: 0.10.0

FAQ
Has the Knowledge Base been checked for a solution?

  • Yes, but couldn't find anything
  • Yes, but solution did not work

File / class missing?

If you get errors about missing files or classes, for example:

  • PHP Fatal error: Interface ... not found
  • PHP Fatal error: Uncaught Error: Class ... not found
  • Source class ... for ... generation does not exist

it is most likely not a bug. The reason is in most cases that the required library lib-shipping-mx was not installed.

Please check the README.md. It explains how to install everything correctly, which will resolve the above errors. There's also an article in our Knowledge Base that explains the necessary steps.

Any questions about this? Feel free to contact our support team.

2.2.0 Compatibility

Hey guys,

thanks for your latest help within my feature request. This time I just want to know if there's a timeline for a 2.2 compatible version?

Greetings
Jan

add all products by default

Feature description
When I create a shipment for a new order,
I want to have all products of that order already added by default.
The user still has the ability to remove items or change their count as it is now.

Reason

  1. Loading all products,
  2. then selecting them all,
  3. then adding all selected products
    needs to be performed manually for every single order.
    In 99% of all cases no change to the list of items needs to be performed.
    Thus wasting a lot of time and effort.

Additional context
n/a

File missing

PHP Fatal error: Uncaught Error: Class 'Dhl\Shipping\Config\BcsConfigInterface' not found in /var/www/html/magento218/app/code/Dhl/Shipping/Setup/ShippingSetup.php:106

screenshot from 2018-02-22 19-32-15

incompatible with your PHP version (7.1.22)

Bug description
I get following Error:
Package dhl/module-shipping-m2 at version 0.6.0 has a PHP requirement incom
patible with your PHP version (7.1.22)

Steps to reproduce
To reproduce the problem:
Installation with composer download or github

Expected behavior
Add the expected behavior. In other words: what SHOULD happen, but doesn't.

Screenshots / logs
If possible, add screenshots or logs to clarify your problem.

Environment

  • Magento version: 2.2.6
  • PHP version: 7.1.22
  • Module version: 0.6.0

FAQ
Has the Knowledge Base been checked for a solution?

  • Yes, but couldn't find anything
  • Yes, but solution did not work

Weight is not correctly calculated

Bug description
After upgrading to 0.9.1 the weight of a shipment is not calculated correctly based on the products weight anymore. This also causes missing warnings when total weight exceeds the dhl maximum.
Normaly the extension then said to pack the items in multiple packages.

Steps to reproduce
To reproduce the problem:

  1. Create an order with many items which weight around 15-30kg
  2. Weight is not correctly calculated (Qty is ignored)

Expected behavior
Weight should be calculated correctly

Screenshots / logs
screenshot-maruhn shop-2018 10 18-11-40-46

Environment

  • Magento version: 2.2.4 CE
  • PHP version: 7.0
  • Module version: 0.9.1

FAQ
Has the Knowledge Base been checked for a solution?

  • [x ] Yes, but couldn't find anything

Problem writing SAAJ model to stream: sun.security.validator.ValidatorException

Hi.
When I want to create a shipping label in backend I get the following error:
(Problem writing SAAJ model to stream: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.)

I've tried some options on the Internet.
But it didn't work.

  • - I changed JAVA.
  • - I saved the certificate.
  • - I added the certificate to be reliable in Java.

Do you have any other suggestions?

Thank you for your help..

Customs clearance dialog, can't add items

Another long term bug ;) If you want to ship out to a country were you need to fill in the customs clearance details, you can't add any products to the shipment. As a result, all shipments to switzerland etc. are processed over the GK Portal.

grafik

It can be related to the controller as the browsers dev console throws an error 500 on the request (add products to package button clicked)
https://www.xxxxxxxxxx.com/radmin/dhl/order_shipment/getShippingItemsGrid/order_id/4836/?isAjax=true

Cheers
Jan

Standard package sizes [feature wish]

Hey,

at first let me say thanks for creating this nice module. Everything works well oob. During our daily backend work we are missing the following feature:

Each time you ship out a package, you need to write down the packages size. As we are working with many different sizes, you can only remember the most ordered sizes. In conclusion you have to look in another window to grab the right package size. So if there would be a feature to crud packages sizes and apply them by a dropdown(or more advanced by rules like weight or volumetric weight) in the label creation popup, our work would be much easier.

Cheers
Jan

Cannot create return label (Beilegeretoure)

Bug description
Selecting "Return shipment" in the popup for creating a DHL label has no effect. No Return Label (Beilegeretoure) is created, only a "regular" shipping label.

Steps to reproduce

  1. In the DHL configuration in Magento, set the option "Use Return Shipment Service" to "No".
  2. Open an order and create a new DHL shipment.
  3. In the "Create packages" popup, enable the checkbox "Return Shipment" and confirm.
  4. Open the DHL label (PDF). There is no second page with the Return Label.

The checkbox in the "Create packages" popup has no effect. The setting is always taken from the configuration option "Use Return Shipment Service".

Expected behavior
The checkbox should have an effect and override the default configuration.

Environment

  • Module version: 0.10.1

Got certificate error while shipping label creation

When I want to create a shipping label in M2 backend I get the following error:

Shipping labels could not be created: Problem writing SAAJ model to stream: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Is this a temporary error from the DHL webservice or have I configured something wrong?

ZIP code in wrong field after editing address

Bug description
When editing the shipping address for a shipment to a DHL Postfiliale (German post office), the receiver's ZIP code ends up in the wrong request field. It is copied to the receiver city field, which overwrites the city name.

The DHL Versenden API throws this error as a result:

weak validation error: Der angegebene Ort passt nicht zur Postleitzahl

Steps to reproduce

  1. Create an order to a DHL Postfiliale using the regular Magento checkout, and make a deliberate mistake (e.g. non-existing post office number) to provoke a failure.
  2. Try to create a DHL label, which should fail.
  3. Correct the shipping address in the admin panel.
  4. Again, try to create a DHL label.
  5. Look at the request in the debug.log. The receiver city is filled with the ZIP code.

This problem only occurs when shipping to a DHL Postfiliale. It does not occur for DHL Packstations, Paketshops, or regular postal addresses.

Expected behavior
The ZIP code and city name should not get mixed up when editing the shipping address.

Environment

  • Module version: 0.10.1

SOAP-ERROR: Parsing WSDL

Bug description
When creating any shipping label an SOAP-ERROR: Parsing WSDL:
Couldn't load from 'https://cig.dhl.de/cig-wsdls/com/dpdhl/wsdl/geschaeftskundenversand-api/2.2/geschaeftskundenversand-api-2.2.wsdl'

Yesterday everything worked fine - did anything change?

Steps to reproduce
To reproduce the problem:

  1. Go to order
  2. Click on ship and check "create shipping label"
  3. Add product to parcel and click save
  4. See error message ...

Expected behavior
Shipping label should be created in dhl geschäftskundenportal.

Screenshots / logs

image

Log entry in var/log/exception.log:
[2018-08-28 08:46:52] main.CRITICAL: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://cig.dhl.de/cig-wsdls/com/dpdhl/wsdl/geschaeftskundenversand-api/2.2/geschaeftskundenversand-api-2.2.wsdl' : failed to load external entity "https://cig.dhl.de/cig-wsdls/com/dpdhl/wsdl/geschaeftskundenversand-api/2.2/geschaeftskundenversand-api-2.2.wsdl"
{"exception":"[object] (SoapFault(code: 0): SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://cig.dhl.de/cig-wsdls/com/dpdhl/wsdl/geschaeftskundenversand-api/2.2/geschaeftskundenversand-api-2.2.wsdl' : failed to load external entity "https://cig.dhl.de/cig-wsdls/com/dpdhl/wsdl/geschaeftskundenversand-api/2.2/geschaeftskundenversand-api-2.2.wsdl\"
at /var/www/html/magento2/vendor/dhl/module-shipping-m2/Webservice/Client/BcsSoapClient.php:111)"} []

Environment

  • Magento version: 2.2.5
  • PHP version: 7.1
  • Module version: 0.9.0

FAQ
Has the Knowledge Base been checked for a solution?

  • Yes, but couldn't find anything
  • Yes, but solution did not work

White page nach Installation v0.6.0

Guten Tag,
wie auch schon nach der Installation der version 0.1.0 besteht bei uns weiterhin das Problem der "weißen Seite" in der 0.6.0 version.

Nach vcs Installation wie in der Readme angegeben wird die Seite unter
Stores/Configuration/Sales/Shipping settings weiterhin als weiße Seite ausgegeben ( keinerlei Inhalt außer die übliche Magento Admin Sidebar ). Die 0.1.0 version wurde vorher vollständig deinstalliert.
Bei uns läuft derzeit Magento 2.1.5...

Andere Module sind unteranderem:
Fooman - Same OderInvoice-Number
Itoris - Dynamic Product options
Payever - Payment integrations

SOAP-ERROR: Encoding: Element 'majorRelease' has fixed value '1' (value '2' is not allowed)

Hello @ngolatka

since today we are getting the following (possible temporary) error (which is currently not listed in faq), while creating single shipping labels in M2 backend:

Shipping labels could not be created: SOAP-ERROR: Encoding: Element 'majorRelease' has fixed value '1'     (value '2' is not allowed)

The last related commit did work before
42cd90d

So this might be a change within the DHL Api or it is related to the last composer update.

Cheers
Jan

Empty streetNumber for Receiver isn't updated if present in streetName.

Change description
Could you add splitStreet() to UpdateShippingInfoObserver or AppDataMapper if Receiver->streetNumber is empty.

Reason
Our customer had the error message "Shipping labels could not be created: Hard validation error occured." because "Alter Berg 6" isn't split.

Additional context
After storing the incorrect shippingInfo->receiver, there is only the chance updating the receiver address by manual editing the magento shipping address. Maybe it's more convenient checking for a street number again.

Magento version: 2.2.6
Module version: 0.9.1

Magento 2.1.9

Hallo,

funktioniert die extension auch unter M 2.1.9 und oder unter 2.2.1 und wann wird endlich ein offizielles Release kommen?

Habe es versucht auf M 2.1.9 zu instalieren, beim :enable Dhl_Shipping lief alles noch gut
beim upgrade kommt die Fehlermeldung

Fatal error: Interface 'Dhl\Shipping\Webservice\Client\GlRestClientInterface' not found in /html/app/code/Dhl/Shipping/Webservice/Client/GlRestClient.php on line 45

was nun?

Magento Data Migration tool: unmapped DB fields

When running the Magento Data Migration tool to migrate from a Magent 1.9 with DHL Versenden into a Magento 2.1 with dhl-module-shipping-m2, it complains that it does not know what to do with some database fields that sound like DHL Versenden introduced them.

A few lines to be copy&pasted into the mapping.xml would be very helpful for users of this module.

Source documents are not mapped: ...,dhl_versenden_label_status

Destination documents are not mapped: dhlshipping_order_address,dhlshipping_quote_address

Source fields are not mapped. Document: sales_flat_order_address. Fields: ship_to_packstation,package_notification,dhl_versenden_info

Source fields are not mapped. Document: sales_flat_quote_address. Fields: ship_to_packstation,package_notification,dhl_versenden_info

lbs instead of Kg

Bug description
For english orders, the product weight is used in "lbs" in the DHLShipping-M2 dialog.

Steps to reproduce
To reproduce the problem:
1.Set up Magento 2.2.6 with dhl-module-shipping-m2 0.9.0
2.Set Stores->Configuration->General->General->Locale Options->Weight Unit to "kgs" for Default, Website and all Views of that webside
2. Select frontend and admin-frontend to be English
3. place an order
4. try to buy postage for that order
5. The weight is the correct number for Kilogramm but the unit is "lbs"

Expected behavior
The weight of the combined products (+packaging) should be displayed and the selected unit is "kgs".

Screenshots / logs
(sorry, can't publicly post screenshots that inevitably contain customer data.)

Environment

  • Magento version: 2.2.6
  • PHP version: 7.1
  • Module version: 0.9.0

FAQ
Has the Knowledge Base been checked for a solution?

  • Yes, but couldn't find anything
  • Yes, but solution did not work

Return Label

Hi there,

I just wanted to ask whether the Magento built-in retrun management can be used with the M2 DHL extension. I found some code responsible for return management, but no section about that in the documentation. Is it already possible to generate shipping labels as a valid customer?
Or will this be an upcoming feature?

Thank you !

FAQ
Has the Knowledge Base been checked for a solution?

Weight unit in kg

Feature description
Default value for weight unit is lb. I think kg or "use magento weight unit settings is better

Reason
The module is mainly for european DHL customers, which are using kg instead of lb

Module breaks SOAP API

PHP Version 7.0.19
Magento Version 2.1.10
Module Version 0.6.0

After installing the module and going to http://192.168.13.31/magento2/soap?wsdl&services=searchV1 on my dev machine I get the following (I added some linebreaks for readability):

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:m="http%3A%2F%2F192.168.13.31%2Fmagento2%2Fsoap%2Fdefault%3Fservices%3DsearchV1%26wsdl%3D1">
    <env:Body>
        <env:Fault>
            <env:Code>
                <env:Value>env:Receiver</env:Value>
            </env:Code>
            <env:Reason>
                <env:Text xml:lang="de">
                    Invalid parameter type "\Dhl\Shipping\Model\ShippingInfo\CheckoutInfoInterface".
                </env:Text>
            </env:Reason>
            <env:Detail>
                <m:GenericFault>
                    <m:Trace>
                        <![CDATA[
                        #0 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(160): Magento\Framework\Reflection\TypeProcessor->translateTypeName('\\Dhl\\Shipping\\M...') 
                        #1 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(229): Magento\Framework\Reflection\TypeProcessor->register('\\Dhl\\Shipping\\M...') 
                        #2 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(198): Magento\Framework\Reflection\TypeProcessor->_processMethod(Object(Zend\Code\Reflection\MethodReflection), 'QuoteDataAddres...') 
                        #3 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(162): Magento\Framework\Reflection\TypeProcessor->_processComplexType('\\Magento\\Quote\\...') 
                        #4 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(229): Magento\Framework\Reflection\TypeProcessor->register('\\Magento\\Quote\\...') 
                        #5 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(198): Magento\Framework\Reflection\TypeProcessor->_processMethod(Object(Zend\Code\Reflection\MethodReflection), 'QuoteDataAddres...') 
                        #6 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(162): Magento\Framework\Reflection\TypeProcessor->_processComplexType('\\Magento\\Quote\\...') 
                        #7 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(229): Magento\Framework\Reflection\TypeProcessor->register('\\Magento\\Quote\\...') 
                        #8 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(198): Magento\Framework\Reflection\TypeProcessor->_processMethod(Object(Zend\Code\Reflection\MethodReflection), 'QuoteDataCartIn...') 
                        #9 /var/www/html/magento2/vendor/magento/framework/Reflection/TypeProcessor.php(162): Magento\Framework\Reflection\TypeProcessor->_processComplexType('\\Magento\\Quote\\...') 
                        #10 /var/www/html/magento2/vendor/magento/module-webapi/Model/Config/ClassReflector.php(103): Magento\Framework\Reflection\TypeProcessor->register('\\Magento\\Quote\\...') 
                        #11 /var/www/html/magento2/vendor/magento/module-webapi/Model/Config/ClassReflector.php(72): Magento\Webapi\Model\Config\ClassReflector->extractMethodData(Object(Zend\Code\Reflection\MethodReflection)) 
                        #12 /var/www/html/magento2/vendor/magento/module-webapi/Model/ServiceMetadata.php(119): Magento\Webapi\Model\Config\ClassReflector->reflectClassMethods('Magento\\Quote\\A...', Array) 
                        #13 /var/www/html/magento2/vendor/magento/module-webapi/Model/ServiceMetadata.php(148): Magento\Webapi\Model\ServiceMetadata->initServicesMetadata() 
                        #14 /var/www/html/magento2/vendor/magento/module-webapi/Model/ServiceMetadata.php(165): Magento\Webapi\Model\ServiceMetadata->getServicesConfig() 
                        #15 /var/www/html/magento2/vendor/magento/module-webapi/Model/Soap/Wsdl/Generator.php(366): Magento\Webapi\Model\ServiceMetadata->getServiceMetadata('customerV1') 
                        #16 /var/www/html/magento2/vendor/magento/module-webapi/Model/AbstractSchemaGenerator.php(160): Magento\Webapi\Model\Soap\Wsdl\Generator->getServiceMetadata('customerV1') 
                        #17 /var/www/html/magento2/vendor/magento/module-webapi/Model/Soap/Wsdl/Generator.php(374): Magento\Webapi\Model\AbstractSchemaGenerator->getAllowedServicesMetadata(Array) 
                        #18 /var/www/html/magento2/vendor/magento/module-webapi/Model/AbstractSchemaGenerator.php(95): Magento\Webapi\Model\Soap\Wsdl\Generator->getAllowedServicesMetadata(Array) 
                        #19 /var/www/html/magento2/vendor/magento/module-webapi/Controller/Soap.php(131): Magento\Webapi\Model\AbstractSchemaGenerator->generate(Array, 'http', '192.168.13.31', 'http://192.168....') 
                        #20 /var/www/html/magento2/var/generation/Magento/Webapi/Controller/Soap/Interceptor.php(24): Magento\Webapi\Controller\Soap->dispatch(Object(Magento\Framework\App\Request\Http)) 
                        #21 /var/www/html/magento2/vendor/magento/framework/App/Http.php(135): Magento\Webapi\Controller\Soap\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http)) 
                        #22 /var/www/html/magento2/vendor/magento/framework/App/Bootstrap.php(258): Magento\Framework\App\Http->launch() 
                        #23 /var/www/html/magento2/index.php(39): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http)) 
                        #24 {main}
                        ]]>
                    </m:Trace>
                </m:GenericFault>
            </env:Detail>
        </env:Fault>
    </env:Body>
</env:Envelope>

Timelines not kept for over one year now

This is not a technical bug reported, but more important a timeline bug.

The extension was promised in a full working version End 2016 on the website. Then it was beginning of 2017 - then end of Q6 as you can see here:

https://www.netresearch.de/blog/neue-dhl-magento-extensions-versenden-und-dhl-standortsuche/

It is now again over the timeline. Could you pls tell us why it is not possible to build a fully working extension (not alpha or beta). The development now goes on for far over 1 year! and it is still only a beta version available (which is in not case suitable for a production system).

We have found now 3 other solutions for our biggest shops - we are still waiting for this for one of you small shops but really loose trust in a) the company that develops the extension and promotes the timelines which are not hold at all and b) DHL why they do not react here.

Thanks for a feedback if this extension will ever be published next time (and i do not mean 2018 or 2019 with next time...

Cannot set Table rates CSV because change to website view not possible

we have magento 2 with different websites
i can install and use dhl shipping module
with
standard view
and storeviews
but if i want to set the csv from tablerates (standard shipping module for price display)
i have to change to
shopview otherwise the csv does not appear.
when switching to that i get

1 exception(s):
Exception #0 (Magento\Framework\Exception\NoSuchEntityException): Angeforderter Store wurde nicht gefunden.

Exception #0 (Magento\Framework\Exception\NoSuchEntityException): Angeforderter Store wurde nicht gefunden.
#0 /home/xxxxxxxxx/web/xxxxxxx.com/public_html/vendor/magento/module-store/Model/StoreManager.php(167): Magento\Store\Model\StoreRepository->getById('5')
#1 /home/xxxxxxxxx/web/xxxxxxx.com/public_html/vendor/dhl/module-shipping-m2/Model/Config/ConfigAccessor.php(116): Magento\Store\Model\StoreManager->getStore('5')
#2 /home/xxxxxx/web/xxxxxxx..com/public_html/vendor/dhl/module-shipping-m2/Model/Config/ModuleConfig.php(114): Dhl\Shipping\Model\Config\ConfigAccessor-

i have to remove dhl shipping module
then edit csv for shipping
and then activate shipping module haha -- not intended, Right?

Composer install - White page after installation

Hello,
I just installed the module with composer and did every like the instruction said. The installation gone through without any problems.

After enabling and successfully doing all steps i got a white page on Configuration > Sales > Shipping methods.

How do we fix this issue ?

User name as contact

On the shipping label the name of the Magento user, who create the shipping label is also printed. I believe most shops do not want the user name to be printed on the label, but only the shop name and adress.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.