Ship .JSON data not importing to Foundry

[Solas67]

Using a custom ship build, I successfully built a ship but I get no messages at all when attempting to import the data into Foundry and am unsure as to what the error might be.
USS_Intrepid-foundry-vtt.json

[bcholmes]

Hm. I'll give that a try. Just to check: you get the JSON file from the website, but it doesn't load into Foundry?

[Solas67]

Yeah. I recreated it and saved it in a second location and still no go.

…

On Tue, 21 Jan 2025 at 1:19 am, BC Holmes ***@***.***> wrote: Hm. I'll give that a try. Just to check: you get the JSON file from the website, but it doesn't load into Foundry? — Reply to this email directly, view it on GitHub <#251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNK32YX4VTEATDLLNQM2RTT2LUHZFAVCNFSM6AAAAABVQTIDXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBZGE4DGMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mprangenberg]

The problem is that the weapons have no names:
"name": "", "type": "starshipweapon", "img": "modules/sta-compendia/assets/icons/starshipweapons-core/weapon-photon-torpedo.svg",
Foundry says
[BaseItem.name]: may not be a blank string

[bcholmes]

Thanks for that.

[bcholmes]

I've tweaked this in the latest version. Give it a try, now?

[Solas67]

Sorry to say still not happening. Tested it twice.

…

On Tue, Jan 21, 2025 at 6:32 AM BC Holmes ***@***.***> wrote: I've tweaked this in the latest version. Give it a try, now? — Reply to this email directly, view it on GitHub <#251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNK32YT2DFAGRZDPP6BX7U32LVMOPAVCNFSM6AAAAABVQTIDXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBZGUYDAOA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bcholmes]

Sorry: I meant to say that I think I fixed this. I apologize for not fully testing my first attempt at a fix.

[Solas67]

I'm not sure why, but I attempted a few times (even starting with a brand new Actor template) to import the same data and I even moved the data to my foundry folder to be sure, and despite getting a message that the data was imported, it doesn't show up. I am using the 2nd Edition sheets with the 2nd Edition Enhanced package, so I'm not sure if that would be a factor. The .JSON file is unchanged.

…

On Mon, Jan 27, 2025 at 3:45 AM BC Holmes ***@***.***> wrote: Sorry: I meant to say that I think I fixed this. I apologize for not fully testing my first attempt at a fix. — Reply to this email directly, view it on GitHub <#251 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNK32YRIA7TZ53FVUJLMSPT2MUNLDAVCNFSM6AAAAABVQTIDXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJWGAZDAMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Solas67]

I wanted to give a quick update to this; making a new .JSON file imported the data correctly, so I may have to stop using the old one. Would that be a reasonable thing to do?

…

On Mon, Jan 27, 2025 at 4:15 PM Ian Tavener ***@***.***> wrote: I'm not sure why, but I attempted a few times (even starting with a brand new Actor template) to import the same data and I even moved the data to my foundry folder to be sure, and despite getting a message that the data was imported, it doesn't show up. I am using the 2nd Edition sheets with the 2nd Edition Enhanced package, so I'm not sure if that would be a factor. The .JSON file is unchanged. On Mon, Jan 27, 2025 at 3:45 AM BC Holmes ***@***.***> wrote: > Sorry: I meant to say that I think I fixed this. I apologize for not > fully testing my first attempt at a fix. > > — > Reply to this email directly, view it on GitHub > <#251 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BNK32YRIA7TZ53FVUJLMSPT2MUNLDAVCNFSM6AAAAABVQTIDXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJWGAZDAMI> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[bcholmes]

Yes. The fix involves creating an updated version of the JSON file, so older JSON files won't work.

[Solas67]

Got it. And thank you for the fix, it's just fantastic. And thanks for all the work you do on the site, too. It's invaluable.

…

On Mon, Jan 27, 2025 at 11:21 PM BC Holmes ***@***.***> wrote: Yes. The fix involves creating an updated version of the JSON file, so older JSON files won't work. — Reply to this email directly, view it on GitHub <#251 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNK32YUXNNVVJGF5FY7EDZ32MYXELAVCNFSM6AAAAABVQTIDXCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJWHE3DKMI> . You are receiving this because you authored the thread.Message ID: ***@***.***>