Extensions > Manage > Update > select extensions > Update
Message
Updating package was successful.
Warning
Update path does not exist.
Message
Error updating COM_INSTALLER_TYPE_TYPE_.
FTP enabled and joomla install owned by ftp user. Runing LAMP with Ubuntu server, php 5.6.30, apache 2.4.7 and maria db
If I make the tmp directory owned by the ftp user, I have to make it owned by web server group in order to install extensions and I still can't update extensions.
I also can't modify the global configuration. It says Configuration saved, but it doesn't actually write to the configuration.php file. Everything was working fine on Joomla! 3.7.5. I also tried a new 3.8 install and got the same results.
Status | New | ⇒ | Discussion |
This sounds like a server side permission issue, the install routine runs but doesn't allow the files to be overwritten. Can you check the files have been updated when installed?
Yes, I am able to install extensions via the Joomla! interface. (I do the version updates via the patch rather than the upgrade due to the number of sites that I host.) I have tried playing with all sorts of permissions and the only one that helps is to set the tmp directory to 777 or set it to 774 with the user set to the ftp user and the group set the the web server's group, but that only allows me to install stuff fresh, the updates and altering the configuration.php file remain broken and having the tmp directory set to such loose permissions is less than ideal.
Install akeeba admin tools and run a permissions fix
--
Tony Partridge
On 25 September 2017 at 17:49:45, nealrduncan (notifications@github.com)
wrote:
Yes, I am able to install extensions via the Joomla! interface. (I do the
version updates via the patch rather than the upgrade due to the number of
sites that I host.) I have tried playing with all sorts of permissions and
the only one that helps is to set the tmp directory to 777 or set it to 774
with the user set to the ftp user and the group set the the web server's
group, but that only allows me to install stuff fresh, the updates and
altering the configuration.php file remain broken and having the tmp
directory set to such loose permissions is less than ideal.This comment was created with the J!Tracker Application
https://github.com/joomla/jissues at
issues.joomla.org/tracker/joomla-cms/18098.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#18098 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVglhWASCzwuABdcmewf-hgaL9nbFpbks5sl9mpgaJpZM4PiGo8
.
I installed akeeba admin tools and ran a permissions fix. No joy. I got the same error. "Update path does not exist." Global Configuration was not able to write to configuration.php either.
I have the same problem, too
Joomla 3.8.0
PHP Version 7.0.16
Priority | Medium | ⇒ | Urgent |
@tonypartridge See #18024
@nealrduncan @VeghNorbert samuel1201 Whether FTP layer was configured and enabled before update? Please run Forum Post Assistant and post apache2php handler and folder permissions - delete with FTP client.
So if it is saying it can write to the configuration file but doesn't actually work... it sounds to me like the file may have an ownership issue?
@tonypartridge Also see this forum topic
@tonypartridge My theory is simple #18024 caused in same environments an ownership issue.
No, I can't do that. Maybe @mbabker can. But then, if you need the FTP layer and it is broken, you will not be able to update anyway since it's broken. So I'm not sure what an custom updateserver would help to test?
You will have to manually replace the file using an FTP program.
It sounds a lot like the whole FTP layer is broken due to the broken FtpClient class. But if that is the case, you will not be able to use the Joomla Update component to update Joomla, since that one imho uses the FTP layer as well.
So installations that use the FTP layer end up in a dead end. They will need to manually replace some files first using an FTP program.
Can you prepare a custom update server?
Anyone can build an update server, the only thing I "block" is being able to publish it on our domain.
Nobody has answered questions I had, or really provided a clear answer of what specifically the problems are, so that we can best react to it. Until then, I don't want to just arbitrarily put a block in place without understanding what specifically we are blocking, and that understanding will help to be able to address the underlying problem in some way (if it's an issue with trying to run the code from two simultaneous versions, we can document it somewhere and explain why the extra step is needed; if there is a fix we can make in the code we can work on that, etc.).
@mbabker Please see #18020 (comment) plus subscribe this topic https://forum.joomla.org/viewtopic.php?t=955125&view=unread#p3494412
The solution in 18075 worked for us, but we did have to make the tmp directory owned by the ftp user and the web server group.
@nealrduncan Please comment that on the #18075 or even better mark it as a successful test in https://issues.joomla.org/tracker/joomla-cms/18075. That would help a lot.
@nealrduncan How do you fixed it? changed the FtpClient.php and BufferStreamHandler.php?
@samuel1201 Yes, the solution in 18075 worked for us. We use ftp and have the joomla directories owned by the ftp user, but we did have to make the tmp directory owned by the ftp user and the web server group.
@nealrduncan Thanks for your reply!
@samuel1201 If PR #18075 fixes the issue in your case please mark your test results in https://issues.joomla.org/tracker/joomla-cms/18075
@samuel1201 Please post WebServer to PHP Interface value System > System Information > Tabulator "System Information" and screenshot of the permission tab..
and permission tab?
@samuel1201 See this worming above
@nealrduncan Do you you had a warning above like in #18098 (comment) ?
I have no idea to fix this problem.
so I'm considering reverting to the old version (3.7.5)
@Bakual Any idea for #18098 (comment) ?
@samuel1201 you have ssh accces?
Any idea for #18098 (comment) ?
No. I also havent' looked deeper into this issue. I just know that the FtpClient class currently is broken and if that class is used, it will be broken as well. But I don't even know if that class is used here (when FTP layer is enabled). If you don't have the FTP layer enabled, then that shouldn't play a role at all.
Download Full package of 3.8.0, extrackt to to separate folder and fiff this to folders. Look for mising files in site side and existing in there reference folder.
@Bakual This cen be dabe in php but noy updated when really necessary - https://checksums.kubik-rubik.de/#overview-joomla - cen we can contact Victor? - show separately missing file.
Sure, contacting @Kubik-Rubik is easy
Few days ago he was busy with JoomlaDay Germany for sure
@nealrduncan @samuel1201 Because both of you use php-fpm then try please search in the documentation how to run it as user. This is usual 1 line in appropriate config file. The please revert any ownership and permission changes on tmp and retest PR.
Priority | Urgent | ⇒ | Medium |
Status | Discussion | ⇒ | Information Required |
@wojsmol I build my joomla web site on my personal NAS and i am a visual & web designer so i can not to fix the problem with program grammar like PHP or SSL : ( . I install the 3.8.1 release in the morning and the problem still exists (So sad....T_T) . Finally thanks for your great great help!!
Status | Information Required | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-10-05 05:23:29 |
Closed_By | ⇒ | franz-wohlkoenig |
Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/18098
closed as Thread is for Forums - Migrating and Upgrading to Joomla! 3.x.
@jflash please mark your Test at #18075 as successfully:
Hello, I did a clean install of 3.8.1 on Windows 10 and Ubuntu 17.04, both on php 5.6. Ubuntu is having the blank Extensions page. Maybe tha last update of php it's generating the problem.
Thanks.
@VictorRodriguezcl Please ask help on the forums - Migrating and Upgrading to Joomla! 3.x. This repository concerns in first Place Joomla coding. For this Reason closing this Issue, thanks.
I have the same issue in a hosting environment. This is not a Joomla issue but a limitation imposed by the host which I cannot track down. I backed up my site and restored it locally. The error message disappears when run on my test server.
Try this:
youradress.com/administrator/index.php?option=com_installer&task=database.fix
I have the same problem.
Joomla 3.8.0
PHP 5.3.29
Norbert Vegh