Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author Shiptimize

    (@shiptimizeplugins)

    Are you trying to reprint a label? or create a new one?
    From the messages you pasted there looks like that order was:
    1) Exported in October
    2) A label was created in the app for that order in October
    3) You tried to create a label for that same order in december
    4) It cannot find the shipment, will have to check, but probably because it’s already delivered and archived

    Currently it’s not possible to print 2 different labels for the same order in woocommerce as the order name is a unique in our system.

    Was this what you were trying to do?

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    We mean line 684 of that class, in the version associated with your keys, contains
    ‘Type’ => 4, // 1 – Gift, 2 – Documents, 3 – Sample , 4 – Other

    which could never trigger a foreach error. So it could be for ex that the indication of the version in your keys is not up to date.
    Would help imensely if you could either paste the line, or provide a more detailed description of the error. Example there should be a backtrace associated with that error, what other classes or functions are referred?

    This information will help us find a way to reproduce the error.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Hi ??

    Thank you for reaching out, we could not reproduce.

    What does that line of code contain? Or at least what function is it? We checked with the version associated with your keys and it would be impossible for that error to be triggered there, so perhaps you pasted the error before an update?

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    We detected a bug in the way we filter rates, we were returning an incorrect format and therefore the shipping cost was not added.

    If this was the issue you where experiencing, a fix has been published. V 3.1.57

    We’ve also added a github repo which we will maintain going forward with all the subsequent versions
    https://github.com/shiptimize/shiptimize-for-woocommerce

    If your error does not match the above description, please provide more details.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Can you please tells us what version of the plugin/woocommerce you are using and if you have “Hide Shipping Methods” enabled, so we can investigate?

    “where selecting other shipment methods no longer works as it should on checkout”
    What’s the expected behaviour and the current behaviour?

    Thank you very much.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    We do not remove tags. We also don’t explicitly add them.

    There’s no github repo at the moment. If you contact support we can send you the zip file. Specify the version or the reason you’re downgrading so we can know what to send you.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Issue: invalid characters in carrier file name

    Fixed in version 3.1.26. Please confirm if this resolves the reported issue

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    The issue was with invalid characters in the carrier filename. Thank you so much for your comments which helped us to identify and fix the issue.

    Fixed in version 3.1.26.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Issue invalid characters in carrier file name

    Fixed in version 3.1.26.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Thank you for reporting this error.

    Should be fixed in v3.1.25
    Changed it from a breaking error to just a log message. This will allow you to continue to use the plugin, but it may hide other issues.

    The error you are describing happens when the plugin tries to write the shipping method Class. It does this for each carrier in your contract.
    class files are written to <shiptmize_plugin_folder>/includes/shipping-methods/

    The strange thing is that “can’t write to please” should be “can’t write to <classname> please”, so there is something else that’s strange about this bug.

    Would you be so kind as to send us what shows up under
    “Carriers Available In your contract”
    on your Shiptimize settings page? If you don’t feel comfortable pasting it here, please forward that info to [email protected] and tell them the plugin developer asked to be forwarded this info.

    Are you using any custom wordpress install like bedrock?
    Can the plugin write to the shipping methods folder referred above? It should be owned by the same user as your webserver’s user.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Fixed in 3.1.18.

    bedrock uses different directory roots for wp-admin and other content. Therefore site_url() return the backend url which ends in /wp and get_home_url() returns the actual front end domain.

    Create new keys and copy them to your shiptimize settings. Should send the correct url for updates to the api

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Hi dessainsaraiva ??

    Thank you for reaching out, indeed we found an incompatibility issue. Should be fixed in version 3.1.17.

    Can you confirm please?

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Hi Ivo,

    Just checked your keys and the stated callback url for app updates, is of the format
    https://{yoursite}/wp/
    I tried loading it and see this is no longer valid. Was your wordpress installed in a subdirectory when you configured shiptimize?

    If that was the case, just delete the old keys, create new ones. Insert those in the shiptimize settings of your woocommerce and save a new token will be requested and the callback url will be sent.

    If that was not the case, is there anything particular about your wordpress install that could explain why site_url() returns {domain}/wp/? Check what value is defined in your wordpress “Settings” > “General” under “WordPress Address (URL)” and “Site Address (URL)”

    If none of these solve your problem please contact our support team and we’ll help you find a solution.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Free shipping
    Currently all our declared shipping methods in Woocomerce extend the Flat rate, which means it’s not possible to set a limit after which there’s no cost.

    Weight Based Rules
    We are compatible with the WooCommerce Weight Based Shipping plugin, if you use that you’ll be able to set weight based rules and assign a Shiptimize carrier to the shipping method.

    How I can manage this with Shiptimize? (export to shiptmize, without charging the client)
    You can export any order in your woocommerce backoffice to Shiptimize. If the shipping method is not known to the plugin, that means that no carrier will be sent with the order and your default carrier will be assigned instead.
    You can set your default carrier in your Shiptimize settings in “Settings” > “Carrier” > “Settings” under “Default Carrier”.

    After the shipment is in the Shiptimize application, you can always change the carrier associated by manually editing the shipment.

    Plugin Author Shiptimize

    (@shiptimizeplugins)

    Hi ??

    The messages that are displayed in the Shiptimize column relate only to communication between WordPress and the Shiptimize Application. They do not reflect the order status in woocommerce.

    To configure what status you’d like to send back to woocommerce when certain events occur, go to your shop settings in shiptimize “settings” > “connect” > “shop details”

    then choose a status under each even that you care about. By your description it seems like you’re looking for “What Status Will Be Set After Label Is Printed?”
    if you want the tracking code to also be sent to woocommerce, check the “Update Track Code To Shop” checkbox.

    If this does not answer your question please let us know what you are trying to do in more detail, ex. what status would you like to set in what moment of the shipment life cycle.

Viewing 15 replies - 1 through 15 (of 18 total)