Flemming
Make sure you have your license numbers entered correctly. In the
Build Application Licenses tab you must have your 4D developer
licenses first, and your Runtime VL license second.
In the generated application, make sure you have a license in the
Licenses folder. On MacOS we have to manually enter it but on
Windows 4D puts it in. Also if you use plugins, verify that they
are correctly copied into the application. Our experience is that
this is not always the case. Same for your A4D key.
I have found this works just fine, but it is moot if I can't store
all the web files OUTSIDE of the application package.
The web folder and Active4D folder both go in the Database folder
of the Final Application. You can probably move the web folder out
of the application if you make the necessary entries for SAFE DOC
DIRS in Active4D.ini. By default A4D looks for the Active4D.ini
file in the database directory but you can move it to the shared 4D
directory or the ~/Library/Preferences or Windows directory. We
have elected to leave the web folder and Active4D folder in the
database directory as we deploy a complete application and not
individual patches. We have moved the database and other
installation specific files outside of the application so that we
can simply replace the application with a new version.
I dont think this will help as I dont want to store WEB files in the
users local Preferences folder. The bottom line is that I need
access to these files from my Web Editing tools remotely (just like
you do with 4D Server, 4D Runtime, etc)
Using port 80 on the MacOS can be a problem. If you're testing on a
Mac try a different port, for example 8080.
I am using 8080 :-)
Regards
Mike
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
