Forum Discussion
LoundesM
Contributor
Hi
I've had something very similar, reported to the helpdesk and the issue has been replicated, waiting on a fix, I'll update this post when I hear back from SB
LoundesM
7 years agoContributor
Hiya
ok so it turns out that my JSON file needed to be saved in UTF-8 encoding as opposed to the UTF-8-BOM it was originally in, so worth remembering that one, imported without any apparent errors
still have issues with using the html variant but one step closer
regards
Mike
Related Content
Recent Discussions
- 10 days ago