?
avatar rgmears
rgmears
7 Dec 2017

Steps to reproduce the issue

Attempt to update alpha1 to alpha2

Expected result

update to version 2

Actual result

Errors:
Warning: array_filter() expects parameter 2 to be a valid callback, class 'JoomlaupdateModelDefault' not found in /opt/lampp/htdocs/j4dev/administrator/components/com_joomlaupdate/Model/UpdateModel.php on line 1315

Warning: Invalid argument supplied for foreach() in /opt/lampp/htdocs/j4dev/administrator/components/com_joomlaupdate/Model/UpdateModel.php on line 1317

System information (as much as possible)

running on xampp on Linux Mint

Additional comments

I was directed to use the "dev releases" as the Option. There is no such option.

avatar rgmears rgmears - open - 7 Dec 2017
avatar joomla-cms-bot joomla-cms-bot - change - 7 Dec 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 7 Dec 2017
avatar brianteeman
brianteeman - comment - 7 Dec 2017

As with every joomla pre-release there is no upgrade path between pre-releases

avatar rgmears
rgmears - comment - 7 Dec 2017

@C-Lodder asked me to report this.

avatar C-Lodder
C-Lodder - comment - 7 Dec 2017

@brianteeman I thought you could update alphas via the update manager?

Either way, there shouldn't be a PHP error being thrown.

avatar brianteeman
brianteeman - comment - 7 Dec 2017

Functionally you can use the install BUT we never do the update scripts to handle changed files or changed database stuff so it is unlikely to work.

avatar mbabker
mbabker - comment - 7 Dec 2017

Duplicate of #18670 and #19005

avatar mbabker mbabker - change - 7 Dec 2017
Status New Closed
Closed_Date 0000-00-00 00:00:00 2017-12-07 12:41:35
Closed_By mbabker
avatar mbabker mbabker - close - 7 Dec 2017
avatar rgmears
rgmears - comment - 7 Dec 2017

Thanks @mbabker
So, how does one update to alpha 2?

avatar mbabker
mbabker - comment - 7 Dec 2017

One does not update an existing install at this time.

avatar rgmears
rgmears - comment - 7 Dec 2017

So, if one has been working on some things and has to do a fresh install that would mean the altered files would have to be copied over to the new installation.

avatar dgt41
dgt41 - comment - 7 Dec 2017

@rgmears if you are supposed to work on the alpha then you should use git. There are plenty articles how to set this up correctly! Also even in this scenario you’ll have to do a new install for the db, but will not affect the files

avatar brianteeman
brianteeman - comment - 7 Dec 2017

There is nothing new about this. This has been the practice for 13 years

avatar rgmears
rgmears - comment - 10 Dec 2017

@dgt41 Is this the right place to start: https://github.com/joomla/joomla-cms/tree/4.0-dev

avatar stell
stell - comment - 20 Dec 2017

There is nothing new about this. This has been the practice for 13 years

So let's keep going that way, right? Sounds like an arguments for a change to me.

mbabker:

For what it is worth, there is zero technical reason why upgrades between anything but stable releases cannot be supported.

#13660

avatar brianteeman
brianteeman - comment - 20 Dec 2017

Are you volunteering to do the required work?

avatar stell
stell - comment - 20 Dec 2017

So it can be done.

Add a Comment

Login with GitHub to post a comment