ShipStation is implementing a proactive upgrade to accommodate larger order IDs, ensuring continued service and scalability. This update will move our systems from 32-bit to 64-bit. If you use the ShipStation API and do not operate on a system that accommodates 64-bit integer formats, this upgrade could potentially disrupt your workflow.

If you use a custom API integration or programming languages to connect your system to ShipStation, typically to manage orders, this message is for you. ShipStation relies on unique IDs to identify each order. If you've built your own connection, you may need to make some adjustments due to the recent updates.

If your system requires updates, we recommend updating your system by May 30, 2024, to prevent service disruptions. If you have any questions or concerns, please don't hesitate to contact our support team.

Any concerns?

https://help.shipstation...&utm_source=hs_email

Thanks for the notice Ray. It continues to shock me how little time these companies give. It is so frustrating!!

I'll have someone take a look and see if we need to many any changes.

Changes will be required. We are working on it now and will update as soon as possible.

Thanks for letting us know Ray. This could have been a real emergency if you hadn't posted this notice.

Last time I use Support it was through email. Out of curiosity, do any of the patches require a rebuilt?

Yes, all the changes are in the Commercebuilder.dll.

We have documented the changes for AbleCommerce 9. Patches for version 9.0.4 through 9.0.10 will be made available through the Upgrades Manager, as soon as have confirmation from Shipstation.

ShipStation_AC9.pdf (332kb) downloaded 4 time(s). <<<< AbleCommerce version 9 code changes if you have the source.

I will try using email instead. Thanks for the help on that!

Thanks! I also finally received a reply on my ticket from someone else...

It looks like we are good to go with the patches. I should be able to get that started tomorrow. The UPS patches are also happening at the same time. So it's been hectic.

---

Thank you so much for your patience with us, and thank you for clarifying your questions. I will be handling this ticket in behalf of the last agent that you had a conversation with.

To directly answer your question, you can definitely implement the patch that you provided before May 30th. My apologies for the frustration this has caused you, and we are truly sorry for not giving ample notice for this change.

I understand you would prefer to talk with someone over the phone, I am more than happy to help! While I am not currently able to make an outbound call to you, please feel free to call our team at 512-359-3411. We have agents available now to assist you further! In order to ensure they are up to speed, feel free to provide them with your ticket #xxx. Thank you for your understanding.

I hope this helps! If you have any future questions, feel free to reach back! Have a good day.

Take care,
John Denver L.
Merchant Support Advocate

I just compiled and will upload the new DLLs to the production server tonight. If there are any issues, I will let you know. Thank you for getting this out the door so quickly.

-Ray

This is on the development server in my house; I followed the instructions to the letter.

Association references unmapped class: CommerceBuilder.CMS.ChangesetZone

[MappingException: Association references unmapped class: CommerceBuilder.CMS.ChangesetZone]
NHibernate.Cfg.XmlHbmBinding.CollectionBinder.BindCollectionSecondPass(ICollectionPropertiesMapping collectionMapping, Collection model, IDictionary`2 persistentClasses, IDictionary`2 inheritedMetas) +1820
NHibernate.Cfg.XmlHbmBinding.<>c__DisplayClass20_0.<AddCollectionSecondPass>b__0(IDictionary`2 persistentClasses) +50
NHibernate.Cfg.Configuration.SecondPassCompile() +242
CommerceBuilder.Common.DatabaseConfiguration.get_SessionFactory() +181
CommerceBuilder.Common.DatabaseSessionManager.GetSession() +211
CommerceBuilder.DomainModel.NHibernateHelper.QueryOver() +41
CommerceBuilder.Services.StoreLocator.LocateCurrent() +116
CommerceBuilder.Essentials.UpgradeProcessingModule.CheckForUpgrades(HttpContext context, String connectionString) +2229
CommerceBuilder.Essentials.UpgradeProcessingModule.ProcessUpgrades(HttpContext context) +262
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142
System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +75
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +93

What did I miss?

Hi Ray,

I notified the dev team right away last night. Here is what they said -



I have to agree on this based on the error message coming from CommerceBuilder.CMS.ChangesetZone instead of anything related to Shipstation. Do you have the CMS Merge plugin running? Can you please double check everything on your side?

Another dev here reviewed all the changes, implemented them, and tested with no errors.

The problem seems to be that my developer made a change somewhere he wasn't supposed to. I downloaded a previous version of the repo before the modification for ship station was made, Made the modifications myself, and compiled. I copied all modified files—seven of them, not just one dll—to the development site, and everything seems to be running.