CiviCRM Community Forums (archive)

Hi there. After leaving my test installation of the most current versions of Drupal and civicrm (2.2.3) alone for a couple of days, I revisited the site today, and when attempting to get to Civicrm's dashboard, got this error:

Fatal error: Uncaught exception 'Exception' with message 'Please make sure the IDS/tmp folder is writable' in /hsphere/local/home/mysite/drupal.mysite.com/sites/all/modules/civicrm/packages/IDS/Monitor.php:187 Stack trace: #0 /hsphere/local/home/mysite/drupal.mysite.com/sites/all/modules/civicrm/CRM/Core/IDS.php(131): IDS_Monitor->__construct(Array, Object(IDS_Init)) #1 /hsphere/local/home/mysite/drupal.mysite.com/sites/all/modules/civicrm/CRM/Core/Invoke.php(74): CRM_Core_IDS->check(Array) #2 /hsphere/local/home/mysite/drupal.mysite.com/sites/all/modules/civicrm/drupal/civicrm.module(342): CRM_Core_Invoke::invoke(Array) #3 /hsphere/local/home/mysite/drupal.mysite.com/includes/menu.inc(348): civicrm_invoke('dashboard') #4 /hsphere/local/home/mysite/drupal.mysite.com/index.php(18): menu_execute_active_handler() #5 {main} thrown in /hsphere/local/home/mysite/drupal.mysite.comsites/all/modules/civicrm/packages/IDS/Monitor.php on line 187

I did my homework - I checked through the forums and tried all the suggestions, including:

• removing Config.IDS.ini - no effect
• the sql query mentioned in one message (can't remember the specifics, sorry - no effect
• commenting out line 74 of invoke.php - which worked, but from the message, I assumed this needed to be a temporary fix

In the end the solution was to, as others mentioned, make my site files upload directory writable - 777. However, I'm pretty sure I had already done this when installing civicirm and am wondering if there is anything (other than me) that would reset this. I'm concerned that if this is something happening on its own, or at the hosting end, this setup is going to be unreliable.

Incidentally the same problem appears to be happing with my templates_c file. I know that I specifically set this and all its contents (en-US) to 777 - smarty errors? - and resolved the problem, but the directories had all reset to 755. And finally, localization settings were lost - I went from Canada and US back to US exclusively. As I made those settings a while ago, I can't think what would have moved me back to the defaults, unless my hosting service had restored from a backup, and that would've shown up all over the place on my site.

Thanks!
Chris

Thanks for this - I've gone back to my host as well to see if anything is up with them - they asked if I had done anything to reset permissions, apparently this is something I can do in my reseller control panel (I haven't). Cartika, here in Toronto.

I'm keeping an eye on it to see if it recurs, and we'll recheck it then.

Cheers
Chris