Error code 32

[Pebble]

As soon as I get some time I'll get the up's & down's checked out and see what I can find.

[baratheon]

I am receiving the same error. In my case, I am trying to write to a super forum key. It seems like the Admin can do so without a problem, but regular users can't.

[Wormopolis]

did you create a userinterface tab for your key settings?

and did you switch to "manage" on the plugin and check what settings they were set to for your test site? default settings that you establish in the build area, doesnt change they way you have it on the site you are testing it on

[baratheon]

I'm talking about keys not variables or the user interface. I do use both, the variables and the keys in my plugin, but only the keys seem to be giving me a problem - the one super forum key specifically.

[Wormopolis]

there is a key setting IN the user interface

[baratheon]

Sorry, I don't think I know what setting you're referring to. In my admin panel, "Keys" and the "User Interface" have their separate tabs.

[Wormopolis]

when you build a plugin, in the user interface there is a field you can add for key permissions.

[Pebble]

Dec 24, 2013 23:57:14 GMT -8 Wormopolis said:

when you build a plugin, in the user interface there is a field you can add for key permissions.

Got to say that I have no idea either, where this field for key permissions is

[Pebble]

OK, it was bugging me so I had a root around and found this : 


So , I've never looked at this... 
If this isn't set then the default is read only?  That means a user(private) key is useless without this being set ? 
I haven't got time to play about with this today, but maybe the solution to my problem. It does seem a bit odd that a user key(private)  would be read only by default as others shouldn't be able to write to it, so it would never contain anything.

Cheers Wormopolis for this info and hopefully I'll get back here in a day or two with news that it solved my problem!

[Wormopolis]

yeah that. think it defaults to staff on read and write

[P̌̓aͧś̀t̀u͒le͆o͂2̀3̃̓]

It does default to staff for read and write and the rest can just read. And you just add it and change it to read/write.

[Wormopolis]

All the keys default to staff only I believe

[baratheon]

Thanks for the fast response. It seems like it worked

[Pebble]

I just had a quick fiddle (ooh errr!!!) and adding this to the manage tabs and setting it to read and write for everyone, seems to have cured the error 32....
I'll get back to this when my head is a bit clearer, but it does seem odd that this key has that option. Also , and there's probably a very good explanation why, but why would you have this in the manage tabs? Though ... I'll think it through.

But maybe I'm just a bit fuddled over the holiday period!

EDIT: Just thinking about it...   For the user key (private) if a user (admin) changed this setting, then those people excluded would get the error message? Or maybe , it depends on the plugin and what it's doing... like I said, fuddled!