This object is in archive!
Unable to update development server to latest version.
Testing the ftp connection gives the error "Not enough permissions to upgrade files!"
However I've checked the permissions and the ftp user i'm using has both ownership and group permissions to write to the entire community directory.
I've even go so far as to sudo chmod 777 ./community -R and I still get the same error. Is it trying to write to somewhere else like /tmp ?
--edit--
Looking through the code it appears to be using the default home directory of the ftp user rather than the ftp directory in the settings to test if 'application' is writable. Is this a bug?
Hello James,
you won't be able to update development server with auto-upgrade tool.
Please use Manual Upgrade of dev server.
Hello James,
you won't be able to update development server with auto-upgrade tool.
Please use Manual Upgrade of dev server.
Hello James,
you won't be able to update development server with auto-upgrade tool.
Please use Manual Upgrade of dev server.
Hello James,
you won't be able to update development server with auto-upgrade tool.
Please use Manual Upgrade of dev server.
Yes, I noticed after I altered the code to force it to use the path I had set in the ftp settings instead of traversing through my ftp users home directory looking for it's own install that it doesn't accept the development domain as valid...
However if this wasn't a development server the same issue would still exist. Surely if it asks you for the install path it should use the install path you give it,... not flail about looking for it in the ftp users home directory?
Yes, I noticed after I altered the code to force it to use the path I had set in the ftp settings instead of traversing through my ftp users home directory looking for it's own install that it doesn't accept the development domain as valid...
However if this wasn't a development server the same issue would still exist. Surely if it asks you for the install path it should use the install path you give it,... not flail about looking for it in the ftp users home directory?
On live server, you need to click on Test Connection, and it should identify the path. Also it checks, if system can write or delete files in /cache folder, and if it can't with provided access, FTP Settings validation will fail.
In 3.0 this process will be simplified
On live server, you need to click on Test Connection, and it should identify the path. Also it checks, if system can write or delete files in /cache folder, and if it can't with provided access, FTP Settings validation will fail.
In 3.0 this process will be simplified
This is my point, i've been through the code and on a live server (or any server for that matter) it fails to identify the correct path if the ftp users home directory is not in it's own install path. At the same time it actually asks for it's own install path in the ftp settings. Why ask for the path if it's going to attempt to find the path on it's own (and fail)?
Anyway this is now a non-issue for me. If anyone else runs into this issue before 3.0 just create an ftp user with it's home directory as the application install path, and upgrade using that ftp user.
Thanks for your response, you may close this issue.
This is my point, i've been through the code and on a live server (or any server for that matter) it fails to identify the correct path if the ftp users home directory is not in it's own install path. At the same time it actually asks for it's own install path in the ftp settings. Why ask for the path if it's going to attempt to find the path on it's own (and fail)?
Anyway this is now a non-issue for me. If anyone else runs into this issue before 3.0 just create an ftp user with it's home directory as the application install path, and upgrade using that ftp user.
Thanks for your response, you may close this issue.
James,
Thank you for your valuable feedback... We'll consider it in 3.0 release to simplify the process. Actually in 3.0 you won't need to enter FTP settings.
James,
Thank you for your valuable feedback... We'll consider it in 3.0 release to simplify the process. Actually in 3.0 you won't need to enter FTP settings.
Replies have been locked on this page!