Bug #2043
closed
CB 1.3 RC3 : has install issues on hosts with restricted umask()
Added by nant over 13 years ago.
Updated over 13 years ago.
Start date:
04 November 2010
Description
clean install on a joomla 1.5.21 site on joomlapolis hosting gives:
Cannot create directory error during step one of CB installation and
check database.
/home/cb13/public_html/images/comprofiler/ Successfully added.
/home/cb13/public_html/images/comprofiler/gallery/ Failed to be to be created, please do so manually !
Manually do the following:
1.) create /home/cb13/public_html/images/comprofiler/ directory
2.) chmod it to 755 or if needed to 775
3.) create /home/cb13/public_html/images/comprofiler/gallery/
4.) chmod it to 755 or if needed to 775
5.) copy /home/cb13/public_html/components/com_comprofiler/images/gallery/ and its contents to /home/cb13/public_html/images/comprofiler/gallery/
But if i just install over a second time (without manually doing the above) I get no errors.
i can verify that the images/comprofiler/gallery folder has not been created in first install but is created ok (with contents) after second install
[3:08:30 μμ] Kyle (krileon): looks like it's just a problem with the install script, no chmod is specified with the mkdir; i typically pass $path, 0755 as the variables
[3:09:06 μμ] Nicholas G. Antimisiaris: wondering why this did not appear in previous versions
[3:09:31 μμ] Kyle (krileon): no idea, maybe was once there?
[3:09:53 μμ] Nicholas G. Antimisiaris: so is there a proposed fix?
[3:11:38 μμ] Kyle (krileon): lines 451 and 460 try adding 0755 to the mkdir function in install.comprofiler.php, repack and try to install
[3:18:46 μμ] Nicholas G. Antimisiaris: if ( $adminFS->mkdir( $cbImages ) ) {
[3:18:57 μμ] Nicholas G. Antimisiaris: just add parameter?
[3:19:09 μμ] Nicholas G. Antimisiaris: $cbImages, 0755
[3:19:32 μμ] Kyle (krileon): yes
[3:26:52 μμ] Nicholas G. Antimisiaris: confirmed that this change fixes issue!
[3:26:53 μμ] Nicholas G. Antimisiaris: thx
[3:27:00 μμ] Beat: wierd
[3:27:42 μμ] Beat: that should be what the code right after that is doing
- Target version set to CB 1.3
- Subject changed from CB 1.3 RC4 has install issues on JP hosting to CB 1.3 RC3 : has install issues on hosts with restricted umask()
- Status changed from New to Closed
- Assignee set to beat
- % Done changed from 0 to 100
- Estimated time set to 1:00 h
r1240 fixes this issue differently as suggested in patch: we use the CMS's dirperms settings before falling back to 0755.
Also available in: Atom
PDF
Updated by 
Updated by