TYPO3 Core

A note: the form contents get saved, then it throws "not accessible". it happens in any way through the page-module (even with the complete form).

Some log from TV:

GET 200 OK
columnsOnly hidden,title,alias
edit[pages]³⁰¹⁹ edit
returnUrl mod.php?M=web_txtemplavoilaM1&id=3019&updatePageTree=1

the response is the form, when saving:

POST 503 Service Temporarily Unavailable
columnsOnly hidden,title,alias
edit[pages]³⁰¹⁹ edit
returnUrl mod.php?M=web_txtemplavoilaM1&id=3019&updatePageTree=1

the response is the error "not accessible"

---------------------------------------------------------------------------
Some log from "list"-module:

GET 200 OK
edit[pages]³⁰¹⁹ edit
returnUrl db_list.php?id=157&table=

the response is the form, when saving:

POST 200 OK
edit[pages]³⁰¹⁹ edit
returnUrl db_list.php?id=157&table=

the response is the form

---------------------------------------------------------------------------
The post-data looks pretty much the same.

It appears really to be identical, but it shows the error.
It saves the form-content (in both cases), then it throws the error (in "page").
If you just close the new page and re-enter the pages-form getting the complete form, you still get "not accessible".

It is possible to get rid of the error the following way:

- wait for the error to come
- get "back" with the browser's button
- save again (from now on it's behaving well)

These test have been conducted with a "admin"-user who is also userid/groupid of the pages in question. Permitions in the tree are 31/27/0 (xxxxx/xxx-x/-----).

Looks much like something's (a default field for example?) missing in the "$dataArr['pages']['NEW']" process now (was good before).

I found the error in a "process_datamap" after-database-update hook. Unrelated to the core. Please close.

Resolved, no change required. Thanks Niels!