-
- 24,544 Posts
Did you set the files to 644? That would be the next thing to try.
And do make sure the core/cache directory exists and the paths in the config.core.php files are correct.
---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone:
http://bobsguides.com/MODx.html
-
- 47 Posts
Okay going to do a fresh install to test if I can install a working fresh Revo. Also going to compare config-files.
Is there a change to put specific folders/files along with old db on the new install so it's actually previous configuration?!
edit: uploaded extracted install with FTP. tried run setup; no go! "jada jada permissions /core/cache jada" changed permissions to recursively to 775 no go, to 755 same. Set /core/cache to 777 with dashboard triggered a bunch of errors;
Warning: mkdir() [function.mkdir]: SAFE MODE Restriction in effect. The script whose uid is 535 is not allowed to access /home/housecube/domains/housecube.nl/public_html/core/cache/setup owned by uid 101 in /home/housecube/domains/housecube.nl/public_html/setup/includes/parser/modinstallsmarty.class.php on line 88
Warning: mkdir() [function.mkdir]: SAFE MODE Restriction in effect. The script whose uid is 535 is not allowed to access /home/housecube/domains/housecube.nl/public_html/core/cache/setup owned by uid 101 in /home/housecube/domains/housecube.nl/public_html/setup/includes/parser/modinstallsmarty.class.php on line 93
Warning: mkdir() [function.mkdir]: SAFE MODE Restriction in effect. The script whose uid is 535 is not allowed to access /home/housecube/domains/housecube.nl/public_html/core/cache/setup owned by uid 101 in /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 28
Warning: tempnam() [function.tempnam]: SAFE MODE Restriction in effect. The script whose uid is 535 is not allowed to access /home/housecube/domains/housecube.nl/public_html/core/cache/setup owned by uid 101 in /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 31
Warning: file_put_contents() [function.file-put-contents]: Filename cannot be empty in /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 33
Fatal error: Uncaught exception 'SmartyException' with message 'unable to write file ' in /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_write_file.php:35 Stack trace: #0 /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_template.php(271): Smarty_Internal_Write_File::writeFile('/home/housecube...', '<?php /* Smarty...', Object(modInstallSmarty)) #1 /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_template.php(412): Smarty_Internal_Template->compileTemplateSource() #2 /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_template.php(554): Smarty_Internal_Template->renderTemplate() #3 /home/housecube/domains/housecube.nl/public_html/core/model/smarty/Smarty.class.php(335): Smarty_Internal_Template->getRenderedTemplate() #4 /home/housecube/domains/housecube.nl/public_html/setup/includes/request/modinstallrequest.class.php(83): Smarty->fetch('header.tp in /home/housecube/domains/housecube.nl/public_html/core/model/smarty/sysplugins/smarty_internal_write_file.php on line 35
What's the problem guys?
[ed. note: jambek2003 last edited this post 12 years, 2 months ago.]
UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
-
- 47 Posts
safe_mode On Off
safe_mode_exec_dir no value no value
safe_mode_gid Off Off
safe_mode_include_dir no value no value
sendmail_from no value no value
Looks like SAFE MODE = ON is the problem. MODx requirements states safe mode = off.
UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
-
- 47 Posts
Okay probably handy to post the solution! Set the applicable folders and files, which during setup MODx is complaining about, to 777 (read,write and execute) and job done. According to the hosting-provider It's because of vhosting architecture. Setting permissions right open doesn't hurt security according to hosting-provider.
UI /UX designer + bit of Front-End Developer. Getting around with MODx Revolution
