Support » Plugin: DHL Shipping Germany for WooCommerce » non-numeric value warning

  • Resolved pandavisuals

    (@pandavisuals)


    there is an error on the order page top right:

    Warning: A non-numeric value encountered in /www/htdocs/w015c6fc/legend7.de/wp-content/plugins/dhl-for-woocommerce/includes/abstract-pr-dhl-wc-order.php on line 384

    this error appeared before, but my wordpress and woocommerce was not uptodate, thats why i didnt bother to tell it. actually it disappeared after a while without any reason.

    please check thanks

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author Shadi Manna

    (@shadim)

    Can you confirm if this is still happening or not, it is not clear from your comment.

    Thread Starter pandavisuals

    (@pandavisuals)

    Yes it is still happening.

    Plugin Author Shadi Manna

    (@shadim)

    This should be fixed in the new version 1.0.1, please let us know if it is not.

    Thread Starter pandavisuals

    (@pandavisuals)

    still getting the error:
    SOAP-ERROR: Encoding: object has no ‘streetNumber’ property

    street number field has a value in the backend. please check. thanks

    Plugin Author Shadi Manna

    (@shadim)

    This issue is happening because the street number should be in the “Address 2” field, my guess is the number is currently in the “Address 1” field. Move the street number to the second field and this should work.

    Thread Starter pandavisuals

    (@pandavisuals)

    just to clarify. your plugin is searching for the Street Number of the Senders Address?

    we dont have an address1 and address2 in the DHL Paket Plugin Settings.

    https://www.dropbox.com/s/tp4bdfhu169rtgb/error%20-%20no%20streetnumber%20property.jpg?dl=0

    thanks

    Plugin Author Shadi Manna

    (@shadim)

    No this is for the customer address not your shop – https://www.awesomescreenshot.com/image/3015941/987b28d5998820a2a3484b8b6a41bdd1

    Thread Starter pandavisuals

    (@pandavisuals)

    before the 00 bug behind the street number it was working.
    only that the 00 seems to come from the empty second line address field.

    can you please look for another solution.

    we have street and number in one field and using the second address line for additional shipping information: eg: Appertment, Suite, etc.

    we have thousands of clients. we can not separate the street number in a csv file manually. that is just too much work.

    i hope you understand.

    Plugin Author Shadi Manna

    (@shadim)

    There is no easy way to take “Address 1” and know which part of the address is the street and which is the number, which is why the number should be in “Address 2”. Do you have a suggestion on how to deal with this?

    Thread Starter pandavisuals

    (@pandavisuals)

    before the plugin was also working fine when the “address + no” was in the same “address line field 1”.

    that is also the default woo commerce registration.

    only that the 00 appeared behind the entry of the “Address line 1”

    all you have to do is to hide the 00 when “address line 2” is empty.

    in our shop we are using the “address line 2” for other additional information regarding the address.

    it would bring us in trouble when we have to export now all users in a csv list and manually separate the House number from the Street.

    please consider to find another solution if possible. we are really counting on you.

    we really like your plugin. it is the best and most comfortable solution because we dont have to add weights to all products.

    thanks

    Plugin Author Shadi Manna

    (@shadim)

    We are looking into the best way to handle this and will update you shortly.

    Thread Starter pandavisuals

    (@pandavisuals)

    thanks you very much for your understanding!

    [ Please do not bump. ]

    Plugin Author Shadi Manna

    (@shadim)

    This fix has been released.

    Thread Starter pandavisuals

    (@pandavisuals)

    works fine now. thanks a lot for your effort! 🙂

    Plugin Author Shadi Manna

    (@shadim)

    Great, let us know if there are any other issues.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘non-numeric value warning’ is closed to new replies.