HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options
Keep getting the "Could not parse addon info array." Error
Hi all, I was trying to upload an entire new addon, and keep getting the error message: "Could not parse addon info array.". Can someone help me to take a look on this? Thank You.
Note: for the "key" attribute, I had tried both "MailboxValidator" and "mailboxvalidator" but still cannot work.
1
Comments
Can somebody help??
I would post the addon JSON
Put it through a SON validator first to make sure it is valid JSON.
grep is your friend.
I had validate it through JSONLint, and it shows valid json. BTW, the json file is there in the attachment zip file though.
Here is the json string:
{
"name": "MailboxValidator Email Validator",
"description": "This plugin enables user to block invalid, disposable, free or role based email from sign up in your forum.",
"version": "1.0.0",
"mobileFriendly": true,
"icon": "",
"key": "MailboxValidator",
"type": "addon",
"documentationUrl" : "",
"license": "GNU GPL2",
"authors": [
{
"name": "MailboxValidator",
"email": "support@mailboxvalidator.com",
"homepage": "https://www.mailboxvalidator.com"
}
],
"require": {
"vanilla": ">=2.5"
}
}
https://open.vanillaforums.com/discussion/comment/255232/#Comment_255232
What are using to save the file? Notepad?
You might have a Byte order Mark at the top of the file, which is not printed. This will mean the file will not parse becuase the BOM is not valid JSON.
I suggest using an editor like Visual Studio Code.
Use LF line sequence and UTF-8 encoding without BOM.
grep is your friend.
I am using Notepad++, and I had checked the encoding, it is UTF-8 without BOM. I had also converted the EOL to LF but it is still not working. Can you help me to test it out?
Already tried that solution, but still not working....
Alright, after I had created another parent folder with the same name as the key, and put the contents in zip file into the parent folder, zip it again and upload it, it finally pass through the error. The error message was not clear enough to lead me to find out the real issue. Is any chances the error message can be enhance more in future?
You can make the sugeestion here
grep is your friend.