Problems this morning with containers in Catalogs (Legacy)

[compact veldt]

This morning my team logged in to find a confusing change to the hundreds of Container-type items we had set up within our Catalogs (Legacy) content in our SND instance.

It seems like some sort of change has been rolled out introducing the option of choosing "Bundle" in addition to the classic "Container"... but the problem is that our existing contents only re-appear if we set the mode to "Bundle" (the apparently-new one we do not want to use). If we try setting the mode to "Container" (what it was before), then we're presented with an empty item list.

I wasn't really expecting that any kind of change like this (seemingly a breaking change?) to the legacy API, so it has me wondering whether there's been some mixup on the PF side. Is this "Bundle" thing supposed to be here? Was our catalog content intended to be affected in this way?

[sterile anchor]

I seem to be encountering this issue as well.

Seems like attempting to edit items that were previously containers auto converts them into bundles and attempting to keep them as containers and re-add contents converts them into items.

Was this change supposed to be rolled out?

[gray tree]

Thanks for reporting this issue. We're going to roll back the item edit page changes while we investigate.

[sterile anchor]

Thanks for the update! This was causing potentially numerous problems for my team!

It also seems like there are quite a few bugs with the current version as well so hopefully those can be ironed out before this is rolled out again.

Can we potentially get some sort of notice before something like this is pushed out again? Surprised that it seemingly wasn't communicated anywhere.

[compact veldt]

Hello again,

My team logged in at the start of this week to find these same issues recurring for a second time. One of the issues is that:

• the JSON editor window no longer appears for the Custom Data field within Catalogs (Legacy) Items & Containers!

We can work around that problem to some degree by manually editing our custom data constructs in a text editor and pasting them into the Custom Data field... but then there's also the much more serious problem that's recurring as of this week:

• Opening a 'Container'-type item from the Stores tab within the Catalog (Legacy) seems to auto-adjust the item's type from Container to Item (and if we then save changes to when the CMS is in this state, the container contents wind up being erased). Is it possible that the CMS is incorrectly opening the 'item' web view in the case of 'containers' or something? Could it be that this is on some level intended??

This stuff interferes with our ability to run live ops on our project, so I'd greatly appreciate a bit of discussion or some kind of explanation as to what's going on with the CMS here. If there are plans in motion to terminate support for containers in econ v1, alter their functionality in some breaking fashion, or otherwise do something wild like that, we need to know sooner rather than later!

[gray tree]

Hi Bee, seems like we missed the mark again. I apologize for that. We're trying to convert the item editor to our new framework. There are a lot of moving pieces and features that are challenging to test. I've reverted the changes once again and will look into fixes for the issues you described. Sorry for the trouble. Things should be back to normal for now.

[compact veldt]

Thanks for the swift correspondence, glad to have some context for what's happening! I'll relay this message to the team