Quote from: antsplace at Apr 22, 2013, 11:32 AMHi Mark,
I tried adding the line to the connector.php but it didn't help. I did as you suggested and the response was A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again.
I've set the folder and files to 777 and it hasn't made the slightest difference. The site which this does work with is hosted on the same server and has the same folder permissions, the only difference being it has been upgraded to 2.2.7-pl and has been running on revolution since 2.0-pl - which means it has a few different system settings but replicating these don't seem to help either.
Adding the line to connector.php was meant for Chris.
This was for you @antsplace:
Quote from: markh at Apr 22, 2013, 10:55 AM@antsplace: using Firebug, inspect the AJAX request to connector.php in the Network tab when you hit save and paste the response of that here.
I want to know the response of the AJAX request that gets sent to connector.php when you hit Save within ClientConfig. If you get the response "A file permissions error has occurred. Please check the permissions on the script and the directory it is in and try again" when you hit save within ClientConfig, that would mean that the permissions on any of the following files or ANY of the directories they are in is wrong:
- assets/components/clientconfig/connector.php
- core/components/clientconfig/processors/mgr/settings/save.class.php (going from memory here; may be named slightly differently)
If setting file permissions to 0777 and directory permissions to 0666 throws that error, you may be running phpsuexec which means the maximum permissions are 0755 and 0644 respectively. If you can't figure out the right permissions, I suggest checking out the install that does work to see what permissions that uses.
Either way, it sounds like a server and not a ClientConfig / MODX 2.2.7 issue to me.