Symlinks definitely work on the default folder. But in your case it’s showing 
the default folder as non-symlinked, and in the system /Library. Are you sure 
you weren’t try to symlink from the user library at ~/Library/Application 
Support/4D/com.aparajita/Active4D?

If you’re serving two sites using virtual hosts, you don’t need to (and 
shouldn’t) modify 'safe script dirs’.

All the best,

  - Aparajita

> On Nov 1, 2017, at 12:05 PM, Doug Hall <doughall...@gmail.com> wrote:
> 
> I'm getting Unauthorized Access (403) errors when trying to access my
> Active4D host, when served from 4D Remote. Everything works fine from a
> local database on my development machine, and from a development 4D server.
> 
> I moved all of my library files into the <project_folder>/Active4D folder,
> as required by v7.
> 
> From my Active4D log:
> 
> Nov 01 13:28:14 Active4D: [info] interpreter: default directory:
> /Library/Application Support/4D/com.aparajita/Active4D
> 
> This particular "directory" is actually a symlink to
> ~/Documents/<project_folder>
> 
> Later in the log:
> 
> Nov 01 13:28:39 Active4D: [error] server: requested file not in root or
> safe script dirs:
> /Users/<user>/Documents/<project_folder>/<web_root>/index.a4d
> ...
> 
> My safe scripts, from Active4D.ini:
> safe script dirs = <default>/<web_root1>;<default>/<web_root2>
> 
> As you can see, I'm serving two sites, and both sites give me Unauthorized
> access errors to their web root.
> 
> It's just a guess, but it appears that defining the default folder with a
> symlink does not work like it did in Active4D 6.4.
> 
> Doug
> _______________________________________________
> Active4D-dev mailing list
> Active4D-dev@aparajitaworld.com
> http://list.aparajitaworld.com/listinfo/active4d-dev
> Archives: http://active4d-nabble.aparajitaworld.com/


_______________________________________________
Active4D-dev mailing list
Active4D-dev@aparajitaworld.com
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://active4d-nabble.aparajitaworld.com/

Reply via email to