?
avatar jojo12
jojo12
4 Aug 2016

Steps to reproduce the issue

I repared the database

trying to update via joomla actualisation

So I am not able to update

Expected result

Should be updated

Actual result

via akeeba: I get "Unerwarteter HTTP-Statuscode 404"
via direct-hybrid and direct: I get:
0 Argument 3 passed to JClientFtp::getInstance() must be of the type array, null given, called in /srv/www/vhosts/mysite.ch/httpdocs/libraries/joomla/filesystem/file.php on line 488

System information (as much as possible)

PHP erstellt für Linux server46.hostfactory.ch 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64
Datenbankversion 5.5.5-10.0.25-MariaDB-0+deb8u1
Datenbankzeichensatz utf8_general_ci
Datenbankverbindungszeichensatz utf8mb4_general_ci
PHP-Version 7.0.7
Webserver Apache
PHP-Interface für den Webserver fpm-fcgi
Joomla!-Version Joomla! 3.6.0 Stable [ Noether ] 12-July-2016 21:14 GMT
Joomla!-Plattform-Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
Browsererkennung Mozilla/5.0 (Windows NT 10.0; rv:47.0) Gecko/20100101 Firefox/47.0

Additional comments

avatar jojo12 jojo12 - open - 4 Aug 2016
avatar ggppdk
ggppdk - comment - 4 Aug 2016

This and 2 more cases

  • were fixed in J3.6.1

See here:
b7b37ce

#11325

So you should be able to update from J3.6.1 to J3.6.2 or later version when using FTP (?and PHP 7?)
but it seems that you can not update with FTP active from J3.6.0 to J3.6.1 ?

Maybe apply the patches manually ?

avatar jojo12
jojo12 - comment - 4 Aug 2016

thanks, I changed the first one, now I get:
35 JFTP: :append: Unerwartete Antwort

avatar ggppdk
ggppdk - comment - 4 Aug 2016

Try getting new Joomla Update Component
(click download link in the description)
https://github.com/joomla/joomla-cms/releases/tag/3.6.1

Someone with better knowledge on upgrading sites that use JClientFtp should comment

avatar jojo12
jojo12 - comment - 4 Aug 2016

this I uploaded and installed before my problems

avatar ggppdk
ggppdk - comment - 4 Aug 2016

So you

  • need FTP layer to be active (i mean if you do not then disable it and upgrade)
  • a question (since you patched files, and still it does not work) have configured it properly ?

Can you change title of this thread to ?:

Can not upgrade to J3.6.1 if FTP layer is active

avatar brianteeman brianteeman - change - 4 Aug 2016
Labels Added: ?
avatar brianteeman brianteeman - change - 4 Aug 2016
Title
FTP Layer errors updating from 3.6.0 to 3.6.1
errors updating from 3.6.0 to 3.6.1
avatar brianteeman brianteeman - edited - 4 Aug 2016
avatar brianteeman brianteeman - change - 4 Aug 2016
Category Installation
avatar brianteeman brianteeman - change - 4 Aug 2016
Title
errors updating from 3.6.0 to 3.6.1
FTP Layer errors updating from 3.6.0 to 3.6.1
avatar brianteeman brianteeman - change - 4 Aug 2016
Title
Can not upgrade to J3.6.1 if FTP layer is active
FTP Layer errors updating from 3.6.0 to 3.6.1
avatar brianteeman brianteeman - edited - 4 Aug 2016
avatar brianteeman brianteeman - change - 4 Aug 2016
Title
errors updating from 3.6.0 to 3.6.1
Can not upgrade to J3.6.1 if FTP layer is active
avatar brianteeman
brianteeman - comment - 4 Aug 2016

Edited title


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11432.

avatar mbabker
mbabker - comment - 4 Aug 2016

Can not upgrade to J3.6.1 if FTP layer is active

There isn't anything that can be done at a code level without providing something installable via the extension manager. The bug blocking this was fixed in 3.6.1, yes, but the only way to get there if you need to use the FTP layer would be to manual update or install a special package into the extension manager (assuming that's actually functional with the FTP layer enabled) with the needed revisions to make an update possible.

avatar brianteeman brianteeman - change - 7 Aug 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-08-07 11:15:45
Closed_By brianteeman
avatar brianteeman brianteeman - close - 7 Aug 2016
avatar brianteeman
brianteeman - comment - 7 Aug 2016

I am going to close this based on the comments above - nothing we can do


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11432.

Add a Comment

Login with GitHub to post a comment