Extensions > Manage > Update > select extensions > Update
Updating package was successful.
Update path does not exist.
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.
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
On 25 September 2017 at 17:49:45, nealrduncan (email@example.com)
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
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
or mute the thread
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?
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.
@samuel1201 If PR #18075 fixes the issue in your case please mark your test results in https://issues.joomla.org/tracker/joomla-cms/18075
I have no idea to fix this problem.
so I'm considering reverting to the old version （3.7.5)
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.
@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!!
|Closed_Date||0000-00-00 00:00:00||⇒||2017-10-05 05:23:29|
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.
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.