• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

SugarCRM and Plesk - Solutions (Query Failed: AND users.id = '1'::MySQL error 1064:)

K

kenzo.matuzawa

Guest
Hello everyone,

After spending some time on SugarCRM 5.0d installation I finally made it through on a Plesk 8.3 install.

The problem was that after finishing the installation and selecting the timezone, SugarCRM crashed and gave a "Query Failed: AND users.id = '1'::MySQL error 1064:" error message.

After researching on Sugar forums I found a lot of possible solutions, but the only one that really worked was setting the permissions of all Sugar folders and files to 777 and making the user and group apache (apache:apache) owner of them.

If anyone has a better solution please feel free to share with us.

Best regards,
Kenzo
 
even if its already owned as ftpuser:psacln having it set to 777 would be the same thing as setting it to apache:apache and setting to 777

When the files and folders are 777 it really doesn't matter who the owner is at that point since its world writable.
 
Problems with 777

The problem is that although the initial setup runs and works when you set 777 to the entire sugar directory, on any customization of fields in sugar or when you add extensions it will rewite these files, give them lesser permissions, write them as apache:apache and sugar starts to stop working.
 
We have a server where is running around 10 Sugar CRM and we have no issue with it, BUT we use suphp, so this solve the issue.
 
Can you show me the configuration of your suphp ( ofcoarse without the paths )
 
Back
Top