[geeklog-devel] Framework

[Blaine Lang]

Tony,

I had much better luck with this archive.
I still had to modify your ini set line in the config.php to use a ; instead 
of a : as a path delimiter.

I can now have a look at the code as it's quite a change architecturally but 
I like the concepts.
I'm sure it pays off once you get over the learning curve and have the 
codebase in place.

Blaine
----- Original Message ----- 
From: "Tony Bibbs" <tony at tonybibbs.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Sunday, December 12, 2004 3:24 PM
Subject: Re: [geeklog-devel] Framework


Anybody have better luck with the new tarball?

--Tony

Blaine Lang wrote:


>Tony,

>

>Actually getting propel installed was the easiest of the tasks.

>Read my note all the way - I note the real issues with the archive as I see

>them.

>

>Blaine

>----- Original Message ----- 

>From: "Tony Bibbs" <tony at tonybibbs.com>

>To: <geeklog-devel at lists.geeklog.net>

>Sent: Saturday, December 11, 2004 10:29 AM

>Subject: Re: [geeklog-devel] Framework

>

>

>Yeah, keep in mind that I could have included propel's classes in the

>tarball which would have made most of your battles a mute point.  I'll

>probably do that form now on.  It shouldn't be too hard for dabblers

>until they get to the point they want to start doing their own database

>changes...that's where using Propel in conjunction with Phing comes in.

>Despite that, I think this is something we can document well enough to

>get people moving along.

>

>Fire over any additional questions.

>

>--Tony

>

>Vincent Furia wrote:

>

>

>

>>Blaine, (Tony,)

>>

>>I had to mess around a lot with the paths as well to get things

>>working (though I did finally get things working).  I had to edit

>>config.php and then I had to add the path

>>/path/to/HuntingLog/system/Propel to the include path. I did this by

>>adding it into the ini_set in config.php.

>>

>>Hopefully that will get you up and running.  Once you figure out

>>_everything_ (and that is a lot) things will start to make sense.  I'm

>>kind of afraid we're going to make development too hard for dabblers.

>>If we go this route, we'll need to come up with some simple way to add

>>basic functionality.

>>

>>I have been looking at it Tony.  I'll have more input soon. Promise.

>>

>>-Vinny

>>

>>

>>On Fri, 10 Dec 2004 22:30:58 -0500, Blaine Lang <geeklog at langfamily.ca>

>>wrote:

>>

>>

>>

>>

>>>Tony,

>>>

>>>Well, I after more then an hour I still don't have it running. Been

>>>tracking

>>>down the source of multiple path related issues and there appears to be 

>>>no

>>>end.

>>>

>>>I can't get the include path in php.ini to work and had to edit paths in

>>>the

>>>files.

>>>[edit] source to this is noted at end of this message

>>>

>>>- Install propel and that required the PEAR Log class.

>>>- Install PEAR flexy

>>>

>>>But I've been editing some dozen files in the archive you sent for the 

>>>app

>>>as expected paths are not working and I just restored it as is.

>>>Still more changes need - example:

>>>

>>>Warning: main(HuntingLog/om/BaseHlUser.php) [function.main]: failed to

>>>open

>>>stream: No such file or directory in

>>>g:\www2root\HuntingLog\system\Propel\HuntingLog\HlUser.php on line 2

>>>

>>>Line 2 is:

>>>require_once 'HuntingLog/om/BaseHlUser.php';

>>>

>>>The H1User.php is in the HuntingLog/system/Propel/HuntingLog folder and

>>>the

>>>om folder is below this.

>>>So not sure why the include has the HuntingLog directory

>>>

>>>I made a bunch of changes prior to this as well - I was just trying to

>>>make

>>>it work.

>>>Example:

>>>

>>>Index.php - line 4:

>>>The includes.php is not in the pubic_html folder.

>>>

>>>Fix that and then line 5 has an error.

>>>

>>>I did this as noted for about a dozen files and I'm still not done.

>>>

>>>I set $hlConf['path'] and  $hlConf['site_url']

>>>

>>>So what did I do wrong or is wrong ?

>>>

>>>BTW: This is what was messing up my php.ini setting for the includes

>>>setting:

>>>The line at the end of the config.php to set the include_path - should

>>>that

>>>not be with a ; instead of a :

>>>ini_set('include_path', ini_get('include_path') .

>>>";{$hlConf['path']}:{$hlConf['path_system']}");

>>>

>>>Blaine

>>>

>>>

>>>

>>>_______________________________________________

>>>geeklog-devel mailing list

>>>geeklog-devel at lists.geeklog.net

>>>http://lists.geeklog.net/listinfo/geeklog-devel

>>>

>>>

>>>

>>>

>>>

>>_______________________________________________

>>geeklog-devel mailing list

>>geeklog-devel at lists.geeklog.net

>>http://lists.geeklog.net/listinfo/geeklog-devel

>>

>>

>>

>>

>

>_______________________________________________

>geeklog-devel mailing list

>geeklog-devel at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devel

>

>_______________________________________________

>geeklog-devel mailing list

>geeklog-devel at lists.geeklog.net

>http://lists.geeklog.net/listinfo/geeklog-devel

>

>


_______________________________________________
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
http://lists.geeklog.net/listinfo/geeklog-devel