Have you updated database structure through System -> Database?

@SharkyKZ
thanks for your help. Of course. I'm always checking Database. And if it shows it's not up to date, then I fix it.
Current: Current Database Version: 4.0.0-2019-09-24

Can you reproduce errors with a clean install of nightly build instead of updating?
https://developer.joomla.org/nightly-builds.html

This looks definitely like database was not up to date, because since PR #26295 has been merged, the article table #__content allows NULL values. Please do as @Quy advised and check a clean install. And for testing updates, update a pre-4.0, e.g. 3.9.12 or current staging, to the latest nightly build using the update zip package, and use the "Upload & Update" tab of the Joomla Update component to do the update using the previously downloaded update package. Reinstall core files is something else, it is not a real update.

The PR #25760 you have mentioned is obsolete meanwhile because replaced by #26295 , so #25760 should be closed.

Here you can find a brief description how to test the update path of 4.0-dev: #25467 .

@richard67
OK, I mentioned some PRs, just wanted to tell, what I checked before here & there etc. :-)

Will also try (again) the usual way with: "latest nightly build using the update zip package using the "Upload & Update" tab". This procedure I also did very often in the past. Except last time, when I made the Reinstall function.

Thank you all above. Will inform ....

@ChristineWk No problem, all fine. Just keep us up to date. Thanks for testing.

First of all: thanks for understanding.

Latest News for today:

System > Under Database:

There was a PR: https://issues.joomla.org/tracker/joomla-cms/26458
concerning the word: "Fix". which has been changed to: "Update Structure" > this I have :-)

Just made: latest nightly build using the update zip package from here: https://developer.joomla.org/nightly-builds.html" using Upload & Update" tab"

After OK update, DB has to be updated. It shows:

4.0.0-2019-09-27 ‎4.0.0-alpha12-dev

Above situation still exists.

@Quy I had already a Joomla 4 since last year. Resulting of some problems etc., I installed a (new) clean install of nightly build on september 6th.

I‘m not a programmer, developer etc., just a „normal user“ :-) Just trying, learning & testing of Patches :- ) to put a little input for all your fantastic work.

@ChristineWk Which was the Joomla version before the update, i.e. from which version did you update to 4.0.0-alpha12-dev nightly build?

@richard67 It appears she did a clean install of the nightly build on September 6 and have been updating/upgrading it with the nightly builds.

Yes indeed :-)

@Quy @ChristineWk You can't update from a 4.0-dev nightly built to another or alpha-x to alpha-y. Updates will be supported starting with 4.0-Beta-1. Then it will be possible to update from pre-4.0 to 4.0-Beta-1, and later from 4.0-Beta-1 to 4.0-Beta-2 and so on.

This has been communicated in JBS, too, Quy.

And this is the reason why I was allowed to change existing 4.0.0-yyyy-mm-dd.sql update sql scripts in my PRs in past and until Beta-1, because otherwise I would have had to make new scripts for each change and comment out changes in old scripts so they are being run when updating because having newer schema version in their file name.

So I am 100% sure that when @ChristineWk does the update from 3.9.12 to that 4.0.0-alpha12-dev nightly build, all will work as expected.

You know the changed update sql scripts for 4.0 has not been run again because their schema version number in file name was not greater than db schema version before the update.

I think that explains all ;-)

Sorry, it's too much for me now to understand, but thank you for your investigation.

No problem. But if you find time tomorrow or later this week, it would be nice if you could really do the update test from 3.9.12 to 4.0 nightly build, because we need people who test that and report back issues. That would be really a help.

Can I try with an existing one? (3.9.12)

Btw: I can't understand, see below, because it was fixed in Code Base after of my installation from September 6

There was a PR: https://issues.joomla.org/tracker/joomla-cms/26458
concerning the word: "Fix". which has been changed to: "Update Structure" > this I have :-)
thks.

No problem. But if you find time tomorrow or later this week, it would be nice if you could really do the update test from 3.9.12 to 4.0 nightly build, because we need people who test that and report back issues. That would be really a help.

Exactly what proof is needed?
of a clean installation 3.9.12 to 4.0 nightly build?

Only that or something else to try?

I can now do those tests.

If something more specific is needed, please let me know.

Can I try with an existing one? (3.9.12)

Sure, but you should make a backup of filesystem and database in case if you need that 3.9.12 later again, because after the test it will be a 4.0-alpha12-dev.

concerning the word: "Fix". which has been changed to: "Update Structure" > this I have :-)

You have "Fix" still? Or "Update Structure"? The update of the files should have been ok, so you should have had "Update Structure", as far as I know. It was only the dastabase stuff which failed, as far as I understand what happened. If you have still "Fix" after the update, then something else went wrong, too, or the nightly build does not contain that change (what it should because it was merged 11 days ago).

of a clean installation 3.9.12 to 4.0 nightly build?

Yes. Update this way using the "Upload & Update" tab of the Joomla Update component.

Link to an issue where the update procedure is described in brief words (but with an older 3.9.x): #25467 .

@richard67 >

@Quy @ChristineWk You can't update from a 4.0-dev nightly built to another or alpha-x to alpha-y. Updates will be supported starting with 4.0-Beta-1. Then it will be possible to update from pre-4.0 to 4.0-Beta-1, and later from 4.0-Beta-1 to 4.0-Beta-2 and so on.
etc.

That's why I'm asking concerning PR #26458, because I have: "Update Structure" after a nightly update package :-)

J 3.9.12, will check, what I can do etc.

of a clean installation 3.9.12 to 4.0 nightly build?

Yes. Update this way using the "Upload & Update" tab of the Joomla Update component.

The update from 3.9.12 to 4.0 nightly build was almost perfect, except for the notifications of the lack of template, notices that stopped appearing at the beginning of the session already within 4.0

The update was by using the "Upload & Update" tab of the Joomla Update component.

I will take a look for warnings or errors.

@ChristineWk PR #26458 renames only the button. Function wise, it is the same as before.

Please do a clean install of the full package of the nightly build from October 14 and you will be back in business without these notices.

@Quy or she updates from 3.9.x like I described.

@ChristineWk If after an update test from 3.9.x to current 4.0 nightly build succeeeds according to the description in #25467 and the issues mentioned in the description above have gone, you can close this issue.

@Quy Since this issue here is about the update and not a new install, it needs the update test to verify that this issue can be closed.

About: update from 3.9.12 to 4.0 nightly build etc., this I will try in another task.

FYI: I think I found out, the reason for above notices & checked/made following:
The Main Menue was not set as: default Page. Don't know why.

• Set as Default Page. Response:
  ErrorColumn 'publish_up' cannot be nullMessage
  COM_MENUS_ITEMS_SET_HOME

• Created a new Main Menu > set to: default was successfully! Now everything works (frontend clean). Notices has gone.

• But minutes later: again above response.
  Means: Main Menu could not be (or only for some minutes) set to: default page.
  Result was/is: Main Page: error 404 plus the other Notices.

You could close the Issue, if wanted. Thanks to all for your informations.

@ChristineWk You can close this issue yourself.