Stuck on "Update temporary item data" (post installation)

micker wrote:

hello
can you test and repair your table via phpmyadmin ? like this topic : www.flexicontent.org/forum/21-troublesho...item-data.html#75655
 

Ok, good and bad news:

Good news: I solved the 'post-installation-screen' like so:
1)  In phpmyadmin, I manually compared tables '_content' and '_flexicontent_items_tmp'.
All my items have no publish_down date, so table '_content' -> field 'publish_down' was NULL in all rows.
But table '_flexicontent_items_tmp' -> field 'publish_down' had '0000-00-00 00:00:00'.
Neither of those values were accepted by my db, so I entered ~today ('2022-09-30 00:00:00') in both tables, all rows. That fixed the screen.

Bad news: Now all my items are published down. A CMS-user can not change that, because the above mentioned publish_down date can not be removed via CMS.

you can select all item and use change state ?

micker wrote:

you can select all item and use change state ?
 

Nope, No effect when I try, and the message "0 records changed to Published".

you have a problem in your bdd ...
try change state of content via phpmyadmin (published is state 1)

micker wrote:

you have a problem in your bdd ...
try change state of content via phpmyadmin (published is state 1)

 

Problem is: content items' state was and is 1 ("published").
It's the 'publish_down' field that makes the problem:
in table '_content', field 'publish_down' cannot be set to NULL. Thus, CMS correctly takes the items as published, but expired.
See my ealier post:
"
[...]
Good news: I solved the 'post-installation-screen' like so:
1)  In phpmyadmin, I manually compared tables '_content' and '_flexicontent_items_tmp'.
All my items have no publish_down date, so table '_content' -> field 'publish_down' was NULL in all rows.
But table '_flexicontent_items_tmp' -> field 'publish_down' had '0000-00-00 00:00:00'.
Neither of those values were accepted by my db, so I entered ~today ('2022-09-30 00:00:00') in both tables, all rows. That fixed the screen.

Bad news: Now all my items are published down. A CMS-user can not change that, because the above mentioned publish_down date can not be removed via CMS.
"

EDIT:
[setup]
- Joomla! 4.2.3
- FC 4.1.3   Release date: 2022-09-13
- php 8.0.23
- sql 8.0.30
- Database Collation: utf8mb4_unicode_ci
- Database Connection Collation: utf8mb4_unicode_ci

Ok, I re-installed everything, and now the error is gone.
Although I believe I did the same steps, there was one possibly important difference on the way:
First I used Akeeba kickstart to help me install joomla.
Now I "manually" ran the installer.
Both fill the database. Maybe something went differently at that point – in case others want to explore more...

Thanks anyway for helping here, Micker