PHP Fatal error: SOAP-ERROR: …in class-pr-dhl-api-soap-label.php

Hi,

I’m seeing this in our logs:

[18-Apr-2018 07:54:23 UTC] PHP Fatal error:  SOAP-ERROR: Encoding: object has no 'streetName' property in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/dhl-for-woocommerce/includes/pr-dhl-api/class-pr-dhl-api-soap-label.php on line 69
[18-Apr-2018 07:54:47 UTC] PHP Fatal error:  SOAP-ERROR: Encoding: object has no 'streetName' property in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/dhl-for-woocommerce/includes/pr-dhl-api/class-pr-dhl-api-soap-label.php on line 69
[24-Apr-2018 11:53:13 UTC] PHP Fatal error:  SOAP-ERROR: Encoding: object has no 'name1' property in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/dhl-for-woocommerce/includes/pr-dhl-api/class-pr-dhl-api-soap-label.php on line 69
[24-Apr-2018 11:53:42 UTC] PHP Fatal error:  SOAP-ERROR: Encoding: object has no 'name1' property in /srv/data/web/vhosts/www.mysite.de/htdocs/wp-content/plugins/dhl-for-woocommerce/includes/pr-dhl-api/class-pr-dhl-api-soap-label.php on line 69

PHP Fatal Error should always be avoided in my opinion, either by better validation or catching errors. I think that these errors occur when the user has entered a wrong (or misspelled) address, hence no 'streetName' property or no 'name1' property.

Maybe you could look into this and make the plugin more “resistant” against these kind of errors.

So maybe even giving the shop-manager some kind of feedback when she/he trys to print a label for which DHL throws an error. AFAIK, DHL only accepts valid addresses and if the customer entered with some kind of type, then it’s not going to be processed (in geschäftskundenportal, i.e. business portal, of DHL). But this might be a second UI/UX step, first it would be good if these SOAP-ERRORs would be caught software-wise…

Thank you!