I am trying to change values in my self hosted control panel on the send email plugin. I can create a screen, but whenever I try to save (even without changing anything), I see the above error. I tried a custom / html page, just a a test, no issues. Seems like something has changed, but I can't fathom what it could be...

Could it be that you have entered an invalid character somewhere? Farcat

If you run your data on the Json validator it may come back with something: http://jsonlint.com/

You might want to look at this post too: http://www.buzztouch.com/forum/thread.php?fid=0516F3A4051C6EE7058E4C9&tid=0516F3A4051C6EE7058E4C9

Promise I'll shut up now. :)

Hi @Farcat, thanks for the ideas. It isn't JSON related, as the app works fine. The problem could be a corrupted plugin - I'll see if I can reinstall it.

OK, I went into my Buzztouch hosted control panel, created a screen of type 'send email', opened it, saved, not problem. I then did the same thing in a different app on my self hosted control panel and I still seeing the same error. Conclusion so far, it is something to do with my self hosted control panel. But, the instructions say to removed a plugin, you have to remove all references to it from all apps and I don't want to do that...

I see... maybe an update of the plugin needs to be done? I am guessing you checked that but just in case. Could this be somehow related to the changes made on BT-side for the V3 core? On the forum the post just below yours mention the same issue. Farcat

I have held back on changing my control panel until v 3.0 comes out - I am still on 2.1.8., but I believe magic happens in the background.

That must be it. A few weeks ago I updated all the plugins whilst still on 2.1.8 and I got an error message when saving on my CP. I can't remember the error message, it could have been the same. Anyway, I updated to 2.1.9 and all was good again. I just remembered now, it's funny how easily one forget issues once they get solved... Farcat

Just to say there was a happy ending - I updated to 2.1.9 and it fixed the problem.

Yeah! Glad to hear :)