Note that there are some explanatory texts on larger screens.

plurals
  1. PONo single directory is writable Joomla
    text
    copied!<p>Some really strange happened to me, while migrating my websites from a hoster to my new VPS with CentOS 6, DirectAdmin (and Jira Image V6, optimized for Magento and Joomla).</p> <p>I migrated one website succesfully, without any problems. The first one. It really works like a charm!</p> <p>All other websites, with the same Joomla! version, I tried to copy, had the same problems of no single directory or file is writable. I checked all settings, everywhere, as far as my knowledge goes, but nothing. The copy method was exactly the same, as the first one.</p> <p>What I did and tried so far: </p> <ul> <li>.htaccess check (what could be wrong?)</li> <li>permissions check (755 and 644) (these are good)</li> <li>ownership check and user / group check (as far as I know they are ok)</li> <li>php.ini check (changed and tried a lot, I really don't know much about this)</li> <li>configuration.php check (all good for sure)</li> </ul> <p>I tried manually uploading, downloading and extracting using SSH, resetting owner via DA. </p> <p>I also tried to put in php.ini > <code>open_basedir = /tmp/</code> , which resulted in a blank page. (possibly something?)</p> <p>I can see the website, I can login into backend, I can use FTP, but I can not modify anything in settings, I can not install anything, I checked the permissions overview and everything is very red, like: Unwritable, really every file and directory. And that is not good.</p> <p>Additional info: </p> <ul> <li>Old server: PHP 5.4.16 > New one: PHP 5.4.15</li> <li>Old server: MySQL 5.5.28 > New one: MySQL 5.5.31</li> <li>Old server: cgi-fcgi > New one: apache2handler</li> <li>Old server: CentOS 6 > New one: CentOS 6</li> <li>need anything to know? ask</li> </ul> <p>I am kind of desperate, while reuploading, VPS reinstalling, etc, etc, doesn't work! Who can point me into the right direction?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload