User profile
Profile of Euncheese4 Posts since 29/08/2007 21:02, name
Recent Posts by Euncheese
12/09/2007 21:07
|
Get Help → hard coded paths |
Sorry for disappearing Jake, I've been mad busy. Been using 1.28 for the last week or so, just to get used to the data model and some of the code structure. I think that some of my auto populate problems had to do with the order in which I was creating constructs (ie. you require a person be added to contacts before a user can be created; nothing for nothing but it could be possible to want a user account who is not in the contacts database (a private IT manager accnt, etc.)) I will let you know when I switch back over to 2.xbeta, for now I'm still playing w/ 1.28. Great software overall, -Mike |
|
29/08/2007 23:48
|
Get Help → hard coded paths |
Some additional peculiarities I've seen while working with the beta 1 release of 2.x: When I add a new company account, that company is not available in the company pull down when creating a new person. In addition when creating a new user, the person pull down is not populated either and even though it is not listed as a mandatory field, it throws a php error in apache for a not-null column restraint in the postgre database.... seems to be a pretty fragile beta at this point, I am going to give 1.2.8 a test drive but keep 2.x-b around to play with. Finally, there is a listed 'wiki' functionality on the source forge page, but I've yet to come across it. -cheese |
|
29/08/2007 21:12
|
Get Help → hard coded paths |
It appears that there are at least several hard coded "/?action" etc's in the code which forces the EGS to be installed at the root of apache's document folder. This is not particularly appealing. I've played around with the SERVER_ROOT variable in config.php, but this does not hit every instance and therefore forces to the root. Let me know if I'm missing something, I'm going to play around with the code some. Also let me know if there is some over arching reason you've forced this limitation. Thanks, -cheese |
|
29/08/2007 21:07
|
Get Help → database error and translation |
I've also seen the database schema creation issue. I found and removed the non-printable character from the .sql file and reloaded without errors. Not sure if that was a bug in the file or was intended, but the character clearly contradicts the character set initialized at the top of the file. -cheese |
|