Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter piexxer

    (@piexxer)

    I wasn’t working from the Github files, or seen what’s on there, though once I have time I will look at suggestions, I’ll look out for your update release to see what’s been changed.

    Thread Starter piexxer

    (@piexxer)

    I can confirm ShipStation API team has now confirmed a fix has been released, from the information I provided them, this can be closed.

    Thread Starter piexxer

    (@piexxer)

    I am fully aware of this not being an official add-on by Shipstation.

    What I meant was, I have been made aware very quickly via your company e-mail, this plugin is “free” so go post on here in so many words for “free assistance”. Which is fine, however, even after I replied to e-mail to notify I posted up here, still 2 weeks later, no support, it was pointless of me to post here, when someone could have just given me an answer very quickly in the e-mail to be helpful in regards to the other post/question, doesn’t matter if it’s a free plugin or not, that’s simply a choice in the support provided. I’m sure you don’t treat paying clients like that!

    Anyway, I reached out to the API team at ShipStation before posting this, I was already on the case, like stated in my post. I already knew it’s not an issue with the plugin through tests I ran either way, I wanted to know if anyone else was having the issue as I believed it was an issue between ShipStation & USPS or alike. For all I know, you could have also been aware of the issue and discussing with Shipstatons API team already.

    So just a heads up to save everyone some time: ShipStations API team confirmed they’ve identified the issue affecting USPS international rate estimates. They are aware of the cause and are working on a fix now. I won’t post the internal details here, but a resolution is officially in progress

    • Hopefully this will resolve it.

    You’re welcome,
    All the best.

    Thread Starter piexxer

    (@piexxer)

    Everything in your code clearly shows it’s not related to “Individual Shipping not being able to access the cart hash and is unable to retrieve the quantity”.

    It’s a logic choice, by whoever coded this plugin, I’m guessing to avoid excessive API calls, after running a lot of tests to change this from “per product line” to “full qty per product”, I can see the issues they ran into on the calls, but also, I did re-work it to be much more efficient in it’s calls to avoid any unnecessary, as there are also other hidden areas to consider on this for performance, which your plugin does not if it was to be simply changed to full qty support logic, however it also calls in areas where it’s not ideal in it’s current logic, so there is room for improvements.

    I just wanted a quick answer without digging (Time), the reason why I approached via e-mail to decide my next option for the client, because I am not charging them for this assistance, just a goodwill support for them, though they are changing direction now, so my re-work is no longer required, I did however collect enough information in the end for any future changes if they continue to use this.

    All the best with the updates, I will keep an eye out on changes, I appreciate this is a free plugin and can be used as wished, I will make sure the client is aware of this.

Viewing 4 replies - 1 through 4 (of 4 total)