Talk:How to solve Installation errors Extension Manager
(New page: As you can see you still need to use your FTP files, so why not use them as the default setting. (This line needs clarification). I didn't understand it although I got the gist of the res...) |
m (→Page information can be dangerous - needs major revisions and additional explanations.: comment) |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | As you can see you still need to use your FTP files, so why not use them as the default setting. | + | [The following is the very last line of this article] |
| − | (This line needs clarification | + | "As you can see you still need to use your FTP files, so why not use them as the default setting. |
| + | |||
| + | (This line needs clarification in my opinion. I did not understand it although I got the gist of the rest of the page. | ||
| + | |||
Furthermore, I must admit that as an "advanced novice" I'm confused about the relationship between and purpose of the following: | Furthermore, I must admit that as an "advanced novice" I'm confused about the relationship between and purpose of the following: | ||
FTP "layer, ways files are uploaded and installed without FTP, relationship between site users and FTP'ing files. | FTP "layer, ways files are uploaded and installed without FTP, relationship between site users and FTP'ing files. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | Propose to add some variation on the following to this page: | ||
| + | It is not very helpful to chmod from ftp when you don't have the privilege from ftp to chmod... | ||
| + | |||
| + | I took the script and changed it so that the action was performed directly rather than through an ftp layer. That way it actually makes the changes. Code snippet to force these directories to 777 follows(replace the other for loop): | ||
| + | <source lang='php'> | ||
| + | $ftp_chmod='777'; | ||
| + | foreach( $dirs as $dir ){ | ||
| + | $cmd='chmod '.$ftp_chmod.' '.$base.$dir; | ||
| + | print(" $cmd \n"); | ||
| + | system($cmd); | ||
| + | } | ||
| + | </source> | ||
| + | |||
| + | This has solved my ftp layer problems for my new 1.6 joomla site. Now, to find some extensions that work with 1.6... | ||
| + | --[[User:Cwg|Cwg]] 07:51, 5 April 2010 (UTC) | ||
| + | |||
| + | |||
| + | I wasn't sure where else to put this, however i feel that having a script that is web accessible and able to change file permissions is a bit risky. I think it would be better to 'chown' the folders to the proper web users that runs Apache or whichever web server the user uses. If you would like i can write up a little diddy about it. | ||
| + | --[[User:Chuckles87|Chuckles87]] 14:03, 15 January 2012 (EST) | ||
| + | |||
| + | == Page information can be dangerous - needs major revisions and additional explanations. == | ||
| + | |||
| + | ''This page contains recommendations on setting a number of files/directories to 777, without sufficient reason or explanation why this would be necessary. | ||
| + | |||
| + | Page Recommends enabling the ftp layer in the Joomla config file without explanation of the reason why. | ||
| + | |||
| + | Page does not explain the reasons why there are/may be issues with certain server setups. | ||
| + | |||
| + | The page does not recommend removal of the php script(s) used after use. This can be a security risk. | ||
| + | |||
| + | A better read to understand the issues would be to start here: | ||
| + | |||
| + | [[Security Checklist/Hosting and Server Setup]] | ||
| + | |||
| + | After reading the page, pay attention to the "Articles in this series" section for additional articles on permissions (which includes file/directory ownership explanations) proper setup and testing of Joomla and so on. | ||
| + | |||
| + | :Totally agree! The article fails on suggestions to find underlying cause of failures, incorrect server settings, which is probably using DSO vs. suPHP or FastCGI. Marked for deletion unless it is improved. [[User:Hutchy68|Tom Hutchison]] ([[User talk:Hutchy68|talk]]) 07:17, 21 December 2012 (CST) | ||
Latest revision as of 08:17, 21 December 2012
[The following is the very last line of this article] "As you can see you still need to use your FTP files, so why not use them as the default setting.
(This line needs clarification in my opinion. I did not understand it although I got the gist of the rest of the page.
Furthermore, I must admit that as an "advanced novice" I'm confused about the relationship between and purpose of the following:
FTP "layer, ways files are uploaded and installed without FTP, relationship between site users and FTP'ing files.
Propose to add some variation on the following to this page: It is not very helpful to chmod from ftp when you don't have the privilege from ftp to chmod...
I took the script and changed it so that the action was performed directly rather than through an ftp layer. That way it actually makes the changes. Code snippet to force these directories to 777 follows(replace the other for loop):
$ftp_chmod='777'; foreach( $dirs as $dir ){ $cmd='chmod '.$ftp_chmod.' '.$base.$dir; print(" $cmd \n"); system($cmd); }
This has solved my ftp layer problems for my new 1.6 joomla site. Now, to find some extensions that work with 1.6... --Cwg 07:51, 5 April 2010 (UTC)
I wasn't sure where else to put this, however i feel that having a script that is web accessible and able to change file permissions is a bit risky. I think it would be better to 'chown' the folders to the proper web users that runs Apache or whichever web server the user uses. If you would like i can write up a little diddy about it.
--Chuckles87 14:03, 15 January 2012 (EST)
[edit] Page information can be dangerous - needs major revisions and additional explanations.
This page contains recommendations on setting a number of files/directories to 777, without sufficient reason or explanation why this would be necessary.
Page Recommends enabling the ftp layer in the Joomla config file without explanation of the reason why.
Page does not explain the reasons why there are/may be issues with certain server setups.
The page does not recommend removal of the php script(s) used after use. This can be a security risk.
A better read to understand the issues would be to start here:
Security Checklist/Hosting and Server Setup
After reading the page, pay attention to the "Articles in this series" section for additional articles on permissions (which includes file/directory ownership explanations) proper setup and testing of Joomla and so on.
- Totally agree! The article fails on suggestions to find underlying cause of failures, incorrect server settings, which is probably using DSO vs. suPHP or FastCGI. Marked for deletion unless it is improved. Tom Hutchison (talk) 07:17, 21 December 2012 (CST)
