?
avatar max123kl
max123kl
11 Mar 2017

Steps to reproduce the issue

given J! 3.4.8 installation
Hoster's PHP restrictions (disabled): disk_free_space, diskfreespace, disk_total_space, dl, exec, fsockopen, get_current_user, get_headers, getrusage, headers_list, leak, link, openlog, passthru, pfsockopen, popen, proc_close, proc_get_status, proc_nice, proc_open, proc_terminate, shell_exec, stream_socket_client, stream_socket_server, symlink, syslog, system

No "File Upload" option at Components -- Joomla Update (see attached img: Joomla-Update_348_cleared_cache.png

screen shot 2017-03-11 at 14 58 17

Expected result

1st Step: update to J!v3.5.1 via Extension Manager by file upload
2nd Step: update to J!v3.5.6 via Update Component by file upload

Actual result

1st Step fails - none fo the following packages are working:
Joomla_3.5.1-Stable-Update_Package.zip
Joomla_3.5.1-Stable-Full_Package.zip
Joomla_3.5.0-Stable-Update_Package.zip
Joomla_3.5.0-Stable-Full_Package.zip
see attched img: Joomla-Update_351_file_upload.png

screen shot 2017-03-11 at 14 58 17

2nd Step not done because of Step 1 failure

System information (as much as possible)

PHP Built On x86_64
Database Version 5.5.33a-MariaDB
Database Collation utf8_general_ci
Web Server Apache/2.4
PHP Version 5.5.21
WebServer to PHP Interface cgi-fcgi
Joomla! Version: Joomla! 3.4.8 Stable [ Ember ] 24-December-2015 19:30 GMT
Joomla! Platform: Version: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
PHPinfo see attached txt file
PHPinfo.txt

Additional comments

On Components Joomla Update there is definitely no tab or button that can be used to upload the update package.
see attached 1st img above

1st Step alternative fails too: update to J!v3.5.1 via Extension Manager by "Install from URL"
see attached img files
Joomla-Update_351_from_URL1.png
Joomla-Update_351_from_URL2.png

screen shot 2017-03-11 at 14 58 17

screen shot 2017-03-11 at 14 58 17

avatar max123kl max123kl - open - 11 Mar 2017
avatar joomla-cms-bot joomla-cms-bot - labeled - 11 Mar 2017
avatar max123kl max123kl - change - 11 Mar 2017
The description was changed
avatar max123kl max123kl - edited - 11 Mar 2017
avatar max123kl max123kl - change - 11 Mar 2017
The description was changed
avatar zero-24
zero-24 - comment - 11 Mar 2017

There is no need for a step between updates. You can do a direct update using the normal update component.

avatar zero-24
zero-24 - comment - 11 Mar 2017

BTW. The last error indicates that there is not transport driver for downloading a package. Please contact your host to enable curl on the server. Please use the forum if you have more questions.

avatar zero-24 zero-24 - change - 11 Mar 2017
The description was changed
Status New Closed
Closed_Date 0000-00-00 00:00:00 2017-03-11 15:29:57
Closed_By zero-24
avatar zero-24 zero-24 - close - 11 Mar 2017
avatar zero-24
zero-24 - comment - 11 Mar 2017

Closing as server issue ;) (missing transport driver ;))

avatar max123kl
max123kl - comment - 11 Mar 2017

You see my problem now
The hoster is not willing to enable transport driver :((

avatar brianteeman
brianteeman - comment - 11 Mar 2017

get a real host then

On 11 March 2017 at 15:32, Dieter Ziller notifications@github.com wrote:

You see my problem now
The hoster is not willing to enable transport driver :((


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#14489 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8cw0wy6EWWFe32ciEa_T91Bia1SXks5rkr6HgaJpZM4MaOeB
.

--
Brian Teeman
Co-founder Joomla! and OpenSourceMatters Inc.
https://brian.teeman.net/ http://brian.teeman.net/

avatar zero-24
zero-24 - comment - 11 Mar 2017

The hoster is not willing to enable transport driver :((

If there is no transport driver (e.g. curl) there is no way that joomla can connect to the update server to check for and update and download the package.

I suggest to change the hoster than.

A workarround could be the folowing.

https://docs.joomla.org/J3.x:Upgrading_from_Joomla_3.4.x_to_3.5 but this should not be a constant solution just a short time workarround.

avatar max123kl
max123kl - comment - 11 Mar 2017

That's what I am looking for! Did not find it yet.
The affected site is for testing only.
A producting site will be hosted elsewhere.

Add a Comment

Login with GitHub to post a comment