From: Honza M. <hon...@ec...> - 2003-05-12 14:58:53
|
On Po, 2003-04-28 at 15:58, Mitra wrote: > Honza > > I've been checking in all the odds and ends from different > installations ofAPC-AA , so that you'll have the latest code for your > release. Thanks. > This included making some changes to config.php3 so that it has less > variation between sites. Specifically I've created three variables > ONLY used inside config.php3, > > AA_SITE_PATH e.g. /home/httpd/html/ > AA_HTTP_DOMAIN e.g. http://my.domain.org/ OK, no problem. I see you also add the # URL or URL path to call admin/edititem.php etc. # this is the variable to make _#EDITITEM alias, etc. $AA_INSTAL_EDIT_PATH = AA_INSTAL_URL; lines, which I prefer to not have there. The problem is with the protocol. The admin url in item.php3 is created by: $admin_path = ($AA_INSTAL_EDIT_PATH ? $AA_INSTAL_EDIT_PATH . "admin/itemedit.php3" : "itemedit.php3"); So far the result was "itemedit.php3" for standard AA itemmanager pages which means, that you can access the pages by 'http' or 'https' and both works well. Now you have to specify AA_INSTAL_URL, so only one method is allowed, which is not good. Can I remove it from the config.php3? Honza > These complement AA_BASE_DIR which was already there and means a lot > of sites will have very little to change in that file. > > The down-side is that almost everyone upgrading via CVS will have to > sort out conflicts. > > Old - un-updated versions of config.php3 will work fine, since the > variables defined are only internal to config.php3 > > - Mitra > -- > Mitra Technology Consulting - www.mitra.biz - mi...@mi... > 02-6684-8096 or 0414-648-0722 > > Life is a Mystery to be Lived, not a Problem to be Solved > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Apc-aa-coders mailing list > Apc...@li... > https://lists.sourceforge.net/lists/listinfo/apc-aa-coders > |