I'm trying to upload my plugin to adapt authoring without success.
Its says:
"There was an error uploading the plugin:
Failed to parse schema for package adapt-beswift-character"
Any ideas?
I'm attaching a screenshot and my plugin zip file.
Failed to parse schema for package
Re: Failed to parse schema for package
Hi Fabian,
Is it possible that you are "overcomplicating" the properties.schema? Looks like you have chosen to reproduce the model.schema in your properties.schema. If I am reading your code correctly, it appears that you want to set characterId in addition to the standard component attributes (layout, title, body, etc). Compare your properties.schema with the one found in adapt-contrib-text. It is providing a means for setting an additional property called instruction. Does it make sense in your situation to imitate it with something like this:
"properties":{
"characterId": {
"type":"string",
"required":true,
"title": "Character ID",
"minLength": 1
}
If I have misread your code, can you summarize what you are attempting with your code?
Chuck
Re: Failed to parse schema for package
Hi Chuck.
I need to have the characterId property be of type enum os it displays a list of possible values (at least that's what I understand the enum does in this case, correct me if Im wrong).
Attached is my properties.schema file.
Any idea?
Re: Failed to parse schema for package
BTW: Ive tried with the propertiesyou shared but it gives me the same error.
Re: Failed to parse schema for package
Hi Fabian,
To my eyes the properties.schema you provided looks pretty good. My guess, however, is that the editorOnly line (and the preceding comma) should come out of the characterId object.
Chuck
Re: Failed to parse schema for package
I tried but still same problem :S
I'm starting to think that it has nothing to do with the properties.schema as I tried switching the file with the one used in adapt-contrib-text and the problem was the same... any ideas what else could it be? Any other schema related file?
Re: Failed to parse schema for package
Yes, Fabian, it seems to be something other than the properties.schema. I successfully uploaded it in my local installation of the authoring tool. I took the zip file you provided, extracted it, replaced the properties.schema with the version you had provided but amended it as I had recommended (deleted "editorOnly" from "characterId), zipped it again, and uploaded through the Plugin Manager. I did not get the "failed to parse" error.
Once in the component editor, however, no fields were available for configuration. So, expect that you still have some issues to confront once you get passed the "failed to parse" error.
Re: Failed to parse schema for package
OK, one more change to the properties.schema that made the fields display in the component editor: delete your enum line and add in the inputType as shown below:
"characterId": {
"type": "string",
"required": true,
"inputType": {"type": "Select", "options":["Mario", "Luigi"]},
"default": "Mario"
}Re: Failed to parse schema for package
Seems like I'm not having any luck with this :(
I tried removing again the editorOnly property from charcterId and even changing the enum line to an inputType as you said in the last comment but still I'm receiving the failed to parse schema error message.
Could you please share the zip file containing the plugin you were able to upload?
BTW: I'm running the Adapt Authoring under Win7 64 bit, not sure if this has something to do with it but just wanted to let you know just in case.
My node version is v0.10.33
Thanks a LOT for your time Chuck!
Re: Failed to parse schema for package
Hey Adapt Community, I'm running out of ideas. Can anyone think of something else that Fabian can check?
I can't speak to any issues with your OS, I'm not running Win7 64. But your node version is what's recommended.
Attached is the zip you requested.
Chuck
Re: Failed to parse schema for package
Great! It worked and I compared my properties.schema (with the change you said) against the properties.schema you had zipped in your computer. The interesting thing is that (at least on Notepad++) the encoding of my schema is "UTF-8" and yours is "UTF-8 without BOM".
Is that the issue?
Re: Failed to parse schema for package
Glad you appear to be over that hump, and glad you had the insight to check the encoding. Personally, this is the first time I'm hearing of someone with Adapt running into the BOM issue, but it seems a reasonable cause to me. I had a similarly frustrating experience several years back when working with some XML.