TYPO3 Core

Same error occurs, when I try to change other properties, e.g. "Hide in menu" or change the value in the layout field.

Markus Klein wrote:

Please go to the Install Tool and run the Database Analyzer (Important Actions). You DB seems to be outdated.

It was a clean, new installation. So I didn't thought of this. Now I checked it and the result was the following:

Database analyzer
Add tables
1. select/deselect all
2. CREATE TABLE cf_extbase_typo3dbbackend_queries ( id int(11) unsigned NOT NULL auto_increment, identifier varchar(250) NOT NULL default '', expires int(11) unsigned NOT NULL default '0', content mediumblob, PRIMARY KEY (id), KEY cache_id (identifier,expires) ) ENGINE=InnoDB;
3. CREATE TABLE cf_extbase_typo3dbbackend_queries_tags ( id int(11) unsigned NOT NULL auto_increment, identifier varchar(250) NOT NULL default '', tag varchar(250) NOT NULL default '', PRIMARY KEY (id), KEY cache_id (identifier), KEY cache_tag (tag) ) ENGINE=InnoDB;

Add fields to tables
1. select/deselect all
2. ALTER TABLE pages ADD categories int(11) NOT NULL default '0';
3. ALTER TABLE sys_file_metadata ADD categories int(11) NOT NULL default '0';
4. ALTER TABLE tt_content ADD categories int(11) NOT NULL default '0';

I executed the queries and after that, the errors didn't appear anymore.

But - it was a clean, new installation of TYPO3 7.02.

Thx for help.

Thanks for the detailed report. It looks like there's a problem with the SchemaMigrator then, because those two cache-tables should be added automatically.
Will try to do a clean install again.

I tried it just now and couldn't find any issue.

Can you try to reproduce this issue with another new installation?
Otherwise I would close this ticket.

Markus Klein wrote:

I tried it just now and couldn't find any issue.

Can you try to reproduce this issue with another new installation?
Otherwise I would close this ticket.

Hm, it was an automate installation with a software manager of a specialized TYPO3-Hoster. I had contact to the support team and reflected, if it could be a problem with the tool. They called back and told me, that it is a known bug and not a problem with the tool. I think, you can close this ticket.