Some Notices after Joomla 4.00-alpha12-dev-Development-Update Package

[ChristineWk]

Steps to reproduce the issue

After Joomla 4.00-alpha12-dev-Development-Update Package on october 09th & tried again on october 13th.
Last update was via Reinstall Joomla Core Files & DB on october 2nd

Expected result

Actual result

Main Page:
Notice: Trying to get property 'id' of non-object in xxx/modules/mod_menu/Helper/MenuHelper.php on line 44 Notice:
Trying to get property 'tree' of non-object in /xxx/modules/mod_menu/Helper/MenuHelper.php on line 56
Notice: Trying to get property 'id' of non-object in /xxx/modules/mod_menu/mod_menu.php on line 19 Notice:
Trying to get property 'id' of non-object in /xxx/modules/mod_menu/mod_menu.php on line 20 Notice: Trying to get property 'tree' of non-object in /xxx/modules/mod_menu/mod_menu.php on line 21
Warning: in_array() expects parameter 2 to be array, null given in /xxx/modules/mod_menu/tmpl/default.php on line 41

**When searching in frontend a menue:
**
Notice: Trying to get property 'id' of non-object in /xxx/modules/mod_menu/mod_menu.php on line 20 and:

Notice: Trying to get property 'id' of non-object in /xxx/modules/mod_breadcrumbs/Helper/BreadcrumbsHelper.php on line 71

System information (as much as possible)

Current Database Version: 4.0.0-2019-09-24
Database Version: MySQLi
Manifest Version: 4.0.0-alpha12-dev
PHP Version: 7.3.8
Webserver: Apache / cgi-fcgi
Joomla Patchtester: 3.0.0-beta5-dev

Additional comments

After saving an article, I got also:
Save failed with the following error: Column 'publish_up' cannot be null > this was on october10th.

Tried some actions, such as rebuild menues etc.

Found this: #21901
and: #25760
and #26460
not sure, if belongs to Issue.

Had also:
Correcting Notice in menu modal
Notice: Trying to get property 'input' of non-object in /xxx/administrator/components/com_menus/layouts/joomla/searchtools/default.php on line 98

this PR: https://issues.joomla.org/tracker/joomla-cms/26590 will solve it.

[SharkyKZ]

Have you updated database structure through System -> Database?

[ChristineWk]

@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

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26591.}

[Quy]

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

[richard67]

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.

[richard67]

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

[richard67]

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

[ChristineWk]

@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 ....

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26591.}

[richard67]

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

[ChristineWk]

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.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26591.}

[richard67]

@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?

[Quy]

@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.

[ChristineWk]

Yes indeed :-)

[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.

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.

[richard67]

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.