Jump to content

why

Fixed 2.4.1 2.4.2

Mals
  • in Shop
  • Moderator
Mals

Posted

Why do I have to redo my shop each time you do an update. it throws JSON errors and I have to start over. Massive waste of my time. 😞

  • Moderator
Mals

Posted

(20:11:28) | [Shop] Loading UI Data exception: Newtonsoft.Json.JsonSerializationException: Could not find member 'AnchorMin' on object of type 'UiElement'. Path '['Full Screen UI']['Select Currency Settings'].Background.AnchorMin', line 15, position 20.

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00267] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0015c] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0006d] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue (Newtonsoft.Json.Serialization.JsonProperty property, Newtonsoft.Json.JsonConverter propertyConverter, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, Newtonsoft.Json.JsonReader reader, System.Object target) [0x00061] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00267] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0015c] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0006d] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue (Newtonsoft.Json.Serialization.JsonProperty property, Newtonsoft.Json.JsonConverter propertyConverter, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, Newtonsoft.Json.JsonReader reader, System.Object target) [0x00061] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00267] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0015c] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0006d] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue (Newtonsoft.Json.Serialization.JsonProperty property, Newtonsoft.Json.JsonConverter propertyConverter, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerProperty, Newtonsoft.Json.JsonReader reader, System.Object target) [0x00061] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) [0x00267] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0015c] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateValueInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType, Newtonsoft.Json.Serialization.JsonContract contract, Newtonsoft.Json.Serialization.JsonProperty member, Newtonsoft.Json.Serialization.JsonContainerContract containerContract, Newtonsoft.Json.Serialization.JsonProperty containerMember, System.Object existingValue) [0x0006d] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType, System.Boolean checkAdditionalContent) [0x000d9] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.JsonSerializer.DeserializeInternal (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00053] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.JsonSerializer.Deserialize (Newtonsoft.Json.JsonReader reader, System.Type objectType) [0x00000] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.JsonConvert.DeserializeObject (System.String value, System.Type type, Newtonsoft.Json.JsonSerializerSettings settings) [0x0002d] in <271c58b7a8684db5a2c92be17a81f252>:0

at Newtonsoft.Json.JsonConvert.DeserializeObject[T] (System.String value, Newtonsoft.Json.JsonSerializerSettings settings) [0x00000] in <271c58b7a8684db5a2c92be17a81f252>:0

at Oxide.Plugins.Shop.ReadOnlyDataObject[T] (System.String name) [0x0003f] in <dc0b49e07abf488da24c259bcbaf090f>:0

at Oxide.Plugins.Shop.LoadTemplate () [0x00011] in <dc0b49e07abf488da24c259bcbaf090f>:0

MeventSupport

Posted

Hi! Our plugin has an automatic migration that has been tested many times, especially since it makes a backup of the data before starting, which ensures that the original data is preserved.

Please clarify what exactly happened? What kind of errors? From which version of the plugin did you upgrade to the latest version?

  • Curator
Mevent

Posted

Hey! Totally get how frustrating it is when things break after an update and you have to redo your setup, that’s a huge time sink.

Shop does have automatic template migration, but as mentioned in the 2.4 changelog:

image.png.8d70776f6988e34e7c6d8e2147f1a835.png

So auto‑migration only runs when Expert Mode is turned off – that’s exactly what it was designed for. When Expert Mode is on, the plugin assumes you fully control the JSON layout and it won’t touch your custom template, because trying to auto‑edit it can actually break things even harder.

We do sometimes have to change data structures to keep improving the plugin and add new features, and auto‑migration + backups are there to make that as painless as possible. But with Expert Mode enabled it’s just too risky to modify your template automatically, so manual conversion is required in that case.

If you let me know which version you updated from and which template you’re using, I can point you to what exactly needs to be adjusted.

OgGinja

Posted

I am getting the same errors as Mals (above post) Had to revert back to v2.3.22 for now.  Where do I change template and disable Expert mode? I honestly didn't know there was such an option.

MeventSupport

Posted

34 minutes ago, OgGinja said:

I am getting the same errors as Mals (above post) Had to revert back to v2.3.22 for now.  Where do I change template and disable Expert mode? I honestly didn't know there was such an option.

We're working on that problem

  • Curator
Mevent

Posted (edited)

Hey! Thanks for the extra reports and patience.
We’ve dug into this issue and finally managed to reproduce what OgGinja and Mals were seeing with the template/JSON errors. It turned out to be a bug on our side, not something you misconfigured.

The problem is now fixed in the latest build, so you shouldn’t have to redo your whole shop anymore after updating. This bug didn’t show up during our internal testing (that’s why we initially couldn’t catch it), but your feedback helped us track it down.

Really sorry for the hassle and the time you’ve already spent rebuilding things – that’s exactly what the auto‑migration was supposed to prevent, not cause. If you run into any more issues after updating to the fixed version, please drop your logs/template and we’ll jump on it right away.

Edited by Mevent
  • Curator
Mevent

Posted

Changed Status from Pending to Fixed

Changed Fixed In to 2.4.2

2.1m

Downloads

Total number of downloads.

9.9k

Customers

Total customers served.

143.4k

Files Sold

Total number of files sold.

3m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.