Open new article on backend.
no notice
Notice: Trying to get property 'stage_id' of non-object in C:\wamp\www\j4\administrator\components\com_content\Model\ArticleModel.php on line 602
Labels |
Added:
?
|
Labels |
Added:
J4 Issue
|
Status | New | ⇒ | Discussion |
Was this a fresh installation or an updated one from previous J4 version?
If the latter, please try with a fresh installation.
updated by github, also did a database fix, but it looks like this missing this column on the fix.
Updated by github is not supported. So please use a fresh installation. If it works then, we can close this.
Updated by github is not supported.
We need to inform People what kind of Update on Alpha, Beta, ... is supported. For Example "Nightly on Nightly isn't supported in Alpha, but supported with Beta", ...
I think it's actually already written somewhere. But basically it's still only support for official stable releases. Everything else may or may not work.
For 4.0, the current plan is still to support updates from betas upwards, certainly not alphas.
This Info should be in "J4 on horizon" and/or Nightly-Download.
Currently it's no different from staging.
See https://developer.joomla.org/development-strategy.html point 4.4:
All Alpha, Beta and Release Candidate releases (defined in SemVer as "pre-releases") must always be regarded as unsupported. It is entirely possible that these releases may contain serious bugs, security issues, forwards and backwards incompatibilities, entire features that are subsequently withdrawn, and so on. There will be no supported update or migration paths from a development release to any other release.
In Alpha 6, 7 and 8 blog posts, we have this mention:
To make the life of testers easier, we will be more strict in updating the deleted files and modifying the SQL changes. This will allow updates between Beta / RC and Stable.
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-04-28 01:12:30 |
Closed_By | ⇒ | 810 |
Can you give more information? Did you fix the datebase?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/24727.