Thursday, March 7, 2013 1:20:06 AM Hi Aparajita,
> Did you put "debug" in the file? Yup. > Aliases won't work for folders in the path up to Active4D, that's why those > error messages are there. Use symlinks instead. Aha, just Googled this; never heard of them before. Alas, might be a bit tricky to do at the client's location; not sophisticated users, and it looks like you either need to do this via the Terminal or install a plugin/service to handle it. As some other users lamented, bummer that Apple doesn't have an easy way to generate these (unless I'm missing something--please chime in if there's a simple way for non-techie users for generating them). I'll try my plan of removing the alias at the user library location and see if things work OK. If so, then no need for this. (Or maybe just move all the real files there--although it's a bit of a pain to access, as Apple has hidden this folder in Mountain Lion and you have to jump a few hoops to get at it.) Once again, thanks! Michael --------------------- On Mar 7, 2013, at 12:39 AM, Aparajita Fishman wrote: >> Also, I created a "log_level" file and put it in the Active4D log directory, >> but I didn't see any change to the logging. > > Did you put "debug" in the file? > > >> One thing that was mentioned in the previous discussion on this error was >> that aliases were being used > > Aliases won't work for folders in the path up to Active4D, that's why those > error messages are there. Use symlinks instead. > > Regards, > > Aparajita > www.aparajitaworld.com > > "If you dare to fail, you are bound to succeed." > - Sri Chinmoy | www.srichinmoy.org > > _______________________________________________ > Active4D-dev mailing list > [email protected] > http://list.aparajitaworld.com/listinfo/active4d-dev > Archives: http://active4d-nabble.aparajitaworld.com/ _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
