Asked also on Discord, but I really must find a solution: Every time I want to save in Kirby 4 and am on a page that contains a little more content, I am redirected to another page and it just says.
Guess that is an understatement? I have no idea, but if you have a lot of custom blocks, maybe there is an error somewhere, the error message points to calling a property of an object that is not defined.
Itâs actually not even an exaggeration. On the page there is a layout, a block, a structure field with 40 entries. But itâs good to know that it can also be caused by an undefined object.
Would it also be possible that it is because a certain field type is no longer available or something similar?
What I find a bit strange is the redirection to the API URL, Iâve never seen that before. Was this also the case in Kirby 3 or has something been changed here perhaps?
Does this affect only a single page? Does it really have to do with the amount of content? Whatâs the difference between this page/these pages and other pages where it doesnât happen?
I canât tell from here why that is happening. Maybe make a copy if your project and try to rule things out.
I feel like the error message (Cannot read properties of undefined (reading 'json')) doesnât necessarily relate to page content. That error is thrown every time the panel doesnât return a json response, and therefore the panel is redirected.
const { response } = false;
let data = response.json;
Therefore, response is undefined and you canât read json on undefined.
You normally donât notice the error because youâre immediately redirected. However, youâre redirected to the api request url, but without a csrf token (which is normally injected in the ajax requests as header), so you arenât seeing the actual error, but only an âUnauthenticatedâ error.
And, finally, because of the immediate redirect, the body of the original response which caused it isnât even downloaded (you donât see it in the dev tools network tab), therefore the only way to actually get a chance to see the error is to replay the request from the console:
in chromeâs dev tools network tab, activate âPreserve Logâ
Click on save in the panel page that causes the error, wait to be redirected
In the network tab, search for the API request that caused the error (it should be red and immediately before the redirect).
right click on it and choose âCopyâ > âCopy as fetchâ.
In the JS console, paste the fetch command. Donât run it immediately.
to the end of the fetch command add a .then(r => r.text()).then(r => console.log(r));
Run it
You should now see the actual error in the console.
Many thanks for your detailed instructions. I have done all this, but could not find anything special. The error message that comes up is the same as above.
When I copy the actual fetch, everything looks fine so far. Then I send it and after about 10 -20 seconds I get a 500 error and actually a 401 error at the same time.
I have tested it on various pages, it definitely has to do with the number and content of the blocks. Initially everything is ok, the more often I duplicate a block with a âlotâ of content, the higher the probability of the error. I know this is difficult to debug.
but the url is the address of the page I wanted to update and at the end /lock
It doesnât happen when I try to save a modification on the page but when I try to edit text in block and press any letter, and it happens even on blueprints with only one block of text.
Last week my hosting service had a migration to a new infrastructure, and a few days before this happened everything was working fine, I was able to make modifications in my panel without any issues.
I am not really sure what I should be looking at, so any easy idea is welcome
Thank you!
Whatâs your Kirby version and what is your PHP version? Are all required extensions still supported on the new infrastructure? Check here: Requirements | Kirby CMS
Could you temporarily enable debug in the config and see if that surfaces more details about the error? Or check your php logs first to see if you get anything there.
From my experience I can tell you that there is no solution for this. The problem only occurs (for me) if you nest a lot of layouts and blocks inside each other several times. Do you have a lot of custom blocks?
I was able to work around the problem with programmable blueprints that only load the blocks that you need for this website.
Hi, Iâm getting the same error message when saving data in a specific blueprint:
â{âstatusâ:âerrorâ,âmessageâ:âUnauthenticatedâ,âcodeâ:401,âkeyâ:âerror.authâ,âdetailsâ:}â
Weird thing is - when working locally there arenât any problems. I tried using the same PHP version but the error persisted. As soon as I upload the site I canât save data in this specific blueprint. I also tried clearing the content file but it didnât change anything.
Running PHP 8.3 and Kirby 4.6
It is so weird - ok I got it working now with a completely empty content template and I started adding content. I have one field:
instareel:
label: Instagram Reel
type: text
I noticed that this was one of the fields causing errors when I added a url so I changed the type from url to text. The behavior didnât change though so if I put in this link: https://www.instagram.com/ I can save the file. If I add anything beyond that e.g. https://www.instagram.com/p and try to save I get the error from above.
Edit 2: Now itâs getting very weird - For me it looks to be related only to URLs. As soon as I try to save a URL in any field (text, textarea, block, âŚ) the error occurs. Sometimes a short URL is saved but as soon as it has additional infos it wonât save. I made the most simplest blueprint:
title: Startseite
icon: home
fields:
name:
label: Inhalt
type: text
The same error occurs. I can save: (h)ttps://www.instagram.com/ but not (h)ttps://www.instagram.com/p and I also canât save: (h)ttps://test.com âŚ
This is with debug on: {"status":"error","message":"Unauthenticated","code":401,"exception":"Kirby\\Exception\\AuthException","key":"error.auth","file":"..\/kirby\/config\/api\/authentication.php","line":14,"details":[],"route":"pages\/([a-zA-Z0-9\\.\\-_%= \\+\\@\\(\\)]+)"}
This error is thrown when the csrf token does not validate. This can happen for various reasons, e.g a full disk, wrong server configuration and I donât know what.
@scma Does this really only affect 1 single page and then only the url field?
@Chloe You wrote above that your hoster made changes, so you didnât make any changes on your side? And does it affect all type of changes in all pages?
No, it affects every page and multiple field types (text, textarea, link, url, structures). The weird thin is, that a URL isnât a general problem. Like I said:
I donât have the problem locally and I tried one other hoster where I didnât have problems. The problems do occur on a Strato Server though although all settings needed for Kirby are set.
It does seem to affect all pages yes. The last changes I made were a few days before the migration, I added a basic project to the portfolio, directly from the panel, and encountered no issue at all.
