1.4.4 CHMOD update

In the past I never ever had a issue with Zenphoto ... my server does NOT support 311, 0600 and other permissions that Zenpoto security conscious setup wants to add and their needs to be a option to turn it off because it tool me SEVERAL HOURS to do chmod by hand over several directories just to get my system to normal.

Most Directories were change to "311" and some files were some changed to "00" or "000".

Then the setup log would go over 2 gb in size with errors like ..

WARNING: opendir(/home1/??????/public_html/???????.com/signature/themes/default
----------------------and

/home1/glamwor2/public_html/philbertphotos.com/signature/zp-core/setup/setup-functions.php on line 31
opendir called from getResidentZPFiles (setup-functions.php [31])
from getResidentZPFiles (setup-functions.php [37])
------------------------------

To by pass this and install Zenphoto after changing all the files. was to HACK out the file permission stuff to it would ignore or bypass it ... was NOT a happy time for me.

Comments

  • Sorry for your troubles. However, servers not supporting the reasonable security settings are going to be a problem.

    BTW, Zenphoto does not wish to use 0311 for anything, so where that came from is questionable. Such a setting would mean that no one can read the file and only the owner can write it. 0600 means that only the owner can read or write the file. Clearly if Zenphoto cannot own its files there are going to be issues.
  • Zenphoto Setup v1.4.5-DEV[9b04ddf31a]: Tue, 05 Feb 2013 18:36:19 -0700
    Query error: MySQLi not connected
    NOTICE: Undefined variable: _zp_resident_files in /home1/glamwor2/public_html/philbertphotos.com/signature/zp-core/setup/index.php on line 1150

    WARNING: array_search() expects parameter 2 to be array, null given in /home1/glamwor2/public_html/philbertphotos.com/signature/zp-core/setup/index.php on line 1150
    array_search called from index.php [1150]
    NOTICE: Undefined variable: _zp_resident_files in /home1/glamwor2/public_html/?????.com/signature/zp-core/setup/index.php on line 1152

    Setting permissions (00) for Zenphoto package.
    NOTICE: Undefined variable: _zp_resident_files in /home1/glamwor2/public_html/???????.com/signature/zp-core/setup/index.php on line 1191
  • My mistake "0600" is fine but "0311" screws up even MY access to the folder or the files and I have to go to the command line to fix it ...and if the folder has nested directories guess what .. GEEZ

    and this "00" this is SOOO upsetting.
  • My mistake "0600" is fine but "0311" screws up even MY access to the folder or the files and I have to go to the command line to fix it ...and if the folder has nested directories guess what .. GEEZ

    and this "00" this is SOOO upsetting.

    I admit I am not best programer but in the setup folder of Zenphoto has quite a bit of "0311" in it for something that does not change ANYTHING to "0311"

    -----------------------------
    function setupLog($message, $anyway=false, $reset=false) {
    global $debug, $_zp_mutex, $chmod;
    if ($debug || $anyway) {
    if (is_object($_zp_mutex)) $_zp_mutex->lock();
    if (!file_exists(dirname(SETUPLOG))) {
    mkdir_recursive(SETUPLOG, $chmod & 0311);
    ---------------------------
    if (is_dir($component)) {
    if ($updatechmod) {
    @chmod($component,$chmod | 0311);
    clearstatcache();
    $perms = fileperms($component)&0777;
    if ($permissions==1 && !checkPermissions($perms, $chmod | 0311)) {
    if (checkPermissions($perms&0755, 0755) || TEST_RELEASE) { // could not set them, but they will work.
    -------------------------------
    $chmod = fileperms(dirname(dirname(__FILE__)))&0666;

    $en_US = dirname(dirname(__FILE__)).'/locale/en_US/';
    if (!file_exists($en_US)) {
    @mkdir(dirname(dirname(__FILE__)).'/locale/', $chmod | 0311);
    @mkdir($en_US, $chmod | 0311);
  • acrylian Administrator, Developer
    Best you open a ticket with this so my colleague later easily spots it.
  • Your problems stem mostly from the first error--MySQLi not connected. That is probably from the DEV build not having all the bug-fix changes migrated. You should try again with the current builds.

    In the mean time, if you happen to have any stack traces of these errors it would help us in making these downstream failures less of an issue.
Sign In or Register to comment.