[geeklog-devtalk] geeklog-devel digest, Vol 1 #445 - 10 msgs

[geeklog-devel-request at lists.geeklog.net]

Send geeklog-devel mailing list submissions to
	geeklog-devel at lists.geeklog.net

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.geeklog.net/listinfo/geeklog-devel
or, via email, send a message with subject or body 'help' to
	geeklog-devel-request at lists.geeklog.net

You can reach the person managing the list at
	geeklog-devel-admin at lists.geeklog.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of geeklog-devel digest..."


Today's Topics:

   1. Bugs in 1.3.10 (Dirk Haun)
   2. Framework (Tony Bibbs)
   3. Re: Framework (Blaine Lang)
   4. Re: Framework (Tony Bibbs)
   5. Re: Framework (Blaine Lang)
   6. Re: Framework (Vincent Furia)
   7. Re: Framework (Tony Bibbs)
   8. Re: Framework (Blaine Lang)
   9. Re: Framework (Tony Bibbs)
  10. Re: Framework (Tony Bibbs)

--__--__--

Message: 1
From: "Dirk Haun" <dirk at haun-online.de>
To: <geeklog-devel at lists.geeklog.net>
Date: Fri, 10 Dec 2004 19:21:12 +0100
Organization: Terra Software Systems
Subject: [geeklog-devel] Bugs in 1.3.10
Reply-To: geeklog-devel at lists.geeklog.net

Okay, the first bug reports for 1.3.10 are in. Nothing dramatic, but
quite a few minor things. Looks like our next goal should be a bugfix
release, i.e. 1.3.10-1.

I've already fixed a few "easy" ones in CVS and will start looking into
the others over the weekend. I don't plan to rush this one out and I'm
not opposed to tossing in a few (minor) improvements or new features as well.

Is anyone aware of any problems that are not listed in the bugtracker?

Yes, Vinny, I remember the bit about magic_quotes_qpc and the What's
Related links.

Blaine, I had to undo the change you made to search.php that disallowed
empty search query strings since it broke the "More by <author>" and
"More from <topic>" options. If you'd like to submit another fix for the
problem you originally tried to fix here, please take these into account.

Also, Blaine, I see you mentioned you had a fix for the archive templates
being used prematurely?

And finally, a coding note: Since we've raised the minimum requirements
to PHP 4.1.0 now, all new code should use the $_GET, $_POST, and
$_REQUEST arrays instead of $HTTP_GET_VARS and $HTTP_POST_VARS.

bye, Dirk


-- 
http://www.haun-online.de/
http://www.macosx-faq.de/


--__--__--

Message: 2
Date: Fri, 10 Dec 2004 16:15:15 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

I know you are all busy and that some of you still hope to review the 
code I sent over.  In the interest of getting some sort of feedback I 
have released the code on geeklog.net:

http://www.geeklog.net/article.php/GL2FrameworkCode

Just an FYI

--Tony

--__--__--

Message: 3
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Framework
Date: Fri, 10 Dec 2004 19:07:19 -0500
Reply-To: geeklog-devel at lists.geeklog.net

Tony,

It appears the link to your code in that article is not working.

Blaine
----- Original Message ----- 
From: "Tony Bibbs" <tony at tonybibbs.com>
To: <geeklog-devel at lists.geeklog.net>
Sent: Friday, December 10, 2004 5:15 PM
Subject: [geeklog-devel] Framework


I know you are all busy and that some of you still hope to review the 
code I sent over.  In the interest of getting some sort of feedback I 
have released the code on geeklog.net:

http://www.geeklog.net/article.php/GL2FrameworkCode

Just an FYI

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

--__--__--

Message: 4
Date: Fri, 10 Dec 2004 18:21:42 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

Fixed.  Thanks.

--Tony

Blaine Lang wrote:


>Tony,

>

>It appears the link to your code in that article is not working.

>

>Blaine

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

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

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

>Sent: Friday, December 10, 2004 5:15 PM

>Subject: [geeklog-devel] Framework

>

>

>I know you are all busy and that some of you still hope to review the 

>code I sent over.  In the interest of getting some sort of feedback I 

>have released the code on geeklog.net:

>

>http://www.geeklog.net/article.php/GL2FrameworkCode

>

>Just an FYI

>

>--Tony

>_______________________________________________

>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

>  

>



--__--__--

Message: 5
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Framework
Date: Fri, 10 Dec 2004 22:30:58 -0500
Reply-To: geeklog-devel at lists.geeklog.net

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 


--__--__--

Message: 6
Date: Fri, 10 Dec 2004 22:52:17 -0500
From: Vincent Furia <vfuria at gmail.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

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

>


--__--__--

Message: 7
Date: Sat, 11 Dec 2004 09:29:50 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

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

>  

>



--__--__--

Message: 8
From: "Blaine Lang" <geeklog at langfamily.ca>
To: <geeklog-devel at lists.geeklog.net>
Subject: Re: [geeklog-devel] Framework
Date: Sat, 11 Dec 2004 10:37:21 -0500
Reply-To: geeklog-devel at lists.geeklog.net

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 


--__--__--

Message: 9
Date: Sat, 11 Dec 2004 10:18:19 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

I'll just package propel in with the tarball and redistribute.  Give me 
a little bit.

--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

>  

>



--__--__--

Message: 10
Date: Sat, 11 Dec 2004 10:49:54 -0600
From: Tony Bibbs <tony at tonybibbs.com>
To: geeklog-devel at lists.geeklog.net
Subject: Re: [geeklog-devel] Framework
Reply-To: geeklog-devel at lists.geeklog.net

Ok, the new tarball only requires the path to PEAR be in your 
include_path.  As a result of this, the tarball now includes the propel 
base classes.  In otherwords, this should require no include_path editing.

Please try again:

http://www.tonybibbs.com/HuntingLog.tar.gz

Sorry, should have done this from square one in the interest of time.

--Tony

Tony Bibbs wrote:


> I'll just package propel in with the tarball and redistribute.  Give 

> me a little bit.

>

> --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





--__--__--

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


End of geeklog-devel Digest