I’m running three Kirby’s on localhost, in my case XAMPP 3.2.4 - only Apache enabled. I’m using the Plainkit 3.4.4.
One of three instances in individual folders is showing
“The JSON response from the API could not be parsed. Please check your API connection.”
And I don’t know why. I copied a untouched Kirby-folder to that instance, but it did not help. I’ve tried to search the forum, but I’ve found nothing that could match my problem (for my poor understanding of Kirby, PHP & Co).
Thank you in advance!
Where does this error show up, in the Panel?
It often has to do with faulty code somewhere or
dump() statements in context that are used within the Panel.
Yes, in the panel: https://localhost/rcmc/panel/site shows the error.
Strange thing: https://localhost/rcmc/panel/pages/impressum works for example.
Edit: I’ve not touched the panel (site.yml) so far.
Have you touched any other files? If it does not happen in a fresh Plain- or Starterkit, than it is likely something in your code.
Not from the Kirby-folder, if that’s the question.
No, I’m not talking about the Kirby folder, but stuff in the site folder (templates, models, config, controllers etc.)
The kirby folder should never be modified, anyway.
Yes, I’m trying to build a site. I’ve some templates, snippets, blueprints and config.
The config is looking good. I’ve renamed this files, so Kirby can’t see them. No changes to the panel. Where should I look first?
Edit: I’ve now tried to rename all possible files (tiny, simple site) to get ignored by Kirby. Did not help.
Do you use any hooks? When exactly does the error appear? Is there any more information in the browser console that might help to find out where the error is coming from? Also check the network tab.
Again: When does this error appear? When loading the Panel after login? When you do something specific?
I guess it doesn’t happen with a freshly installed kit? Because your other two instances seem to work flawlessly?
Oh, sorry. Yes, when I’m logging in to that panel it appears. It’s only the /panel/site - that’s not working.
The other sites and the plainkit are working well.
Sonja helped a lot behind the scenes - thank you, @texnixe, and we finally found my mistake. In my site.txt we found german umlaute (“ü” instead of “ue”) in front of the colon.
Now it’s working… until my “tiny mistake”…