The title asks it all :)

Not really. I can't seem to figure out what the problem is. Not too many examples have rolled in yet. I have checked a few apps for folks that emailed and all of the ones I've checked seemed OK. Very strange. Any insights would be helpful.

Maybe this can help: If I refresh the app the message says: There was a problem parsing some data. Please make sure that it is well-formed.

Oh and most of the screens say: Screen not found - at the navbar. Only a small amount of screens work. I'm not sure but I think, only the screens which are edited with the new WYSIWYG HTML editor has problems. Hope this helps.

Yes, for sure related to the Editor. 100%. When get the error, you can copy-n-paste the config.txt data for your app (use the Show Configuration Data link in Core Settings) in this very cool JSON validator: http://jsonlint.com/ It helps isolate what's wrong with the JSON configuration data. Still not sure what's happening to the editor?

Under the results it says: Parse error on line 1: ...ler_bu_dükkanda__ , dataURL:http:// -----------------------^ Expecting ':'

oh and the up-arrow like thing shows the comma

What app, what screen?

I've copied and pasted config.txt to JSON validator, I guess I've done right. alacati gezgini app by the way. dükkanislabonita screen

when I edit dükkanislabonita screen, it doesn't save the things I've done.

Looking.

I've found it but I don't know why. I had an empty line(pushed enter one more time) on one of my screens - mekantapu- after deleting it app worked fine.

But I still can't save the edited info of the screen dükkanislabonita

Ok.... I'm having hard time understanding the text in the configuration file because of our langauge difference. Because we've been getting reports for a day or two about the editor, maybe it's related to something that's been updated / added in the last day or two? Have you added any new screens or updated any screen content in the last day or two? This could help find the issue?

I think I'm onto somthing: The screen with dükkanislabonita as the nav bar title text is showing VERY STRANGE characters in the configuration file output. The database shows that (what I pasted) but the output in the 'Show Confirugation Data' link is not the same - like it's not showing the UTF-8 Unicode output. May be the entire problem. Still looking...

I've added the screen dukkanislabonita 5 or 6 days ago. But the screen dukkaneasy that I've added today works fine.

Should I change dükkan to dukkan and see what happens?

Probably not, you have lots of these types of files and they are all showing this way. I'm looking at the raw data in the master database and all looks OK. However, it looks like the backend is not outputting data in Unicode / UTF-8 like it needs to. We may need to restart a few servers. Sigh... Doesn't take long but really really hate to do it. However, may not have a choice if we can't get this figured out. Super strange.

I think the and sign & has a problem. If I don't use it, it saves.

I've replaced & with a word and... it works :)

I guess that's good but there still should be an explanation. I'm going to issue a restart shortly. Don't be surprised if your access is limited or gone for a few minutes ;-)

OK :)