Thread: [Phpslash-devel] RC2 testing: manage block types/more Win98 woes
Brought to you by:
joestewart,
nhruby
From: Peter C. <li...@kr...> - 2003-02-10 18:15:02
|
More stuff: The 'Manage block types' option at the foot of the blockAdmin screen needs altered to allow for the fact that Block_render_***.class has to be manually registered with the resource engine by editing config.php. I cant think of a neat way round it, short of storing block classnames in the database/cache, or dropping it altogether + replacing with a HOWTO doc. Another Win98Special The new slashSess gives problems with session save path (giving error "Failed to write session data (files)."*) - solved by swapping in the old slashSess from PSL 0.6.5 (so it's not down to php.ini settings). But then of course, the class lists arent loaded using the old slashSess, so I cant do anything... google brought up loads of unresolved problems with this, so I've switched to developing in Unix. But it would be interesting to know if there are any other Windows users out there to find if this is a real problem, or specific to my config. P |
From: Joe S. <joe...@us...> - 2003-02-10 18:32:13
|
On Mon, Feb 10, 2003 at 06:25:13PM +0000, Peter Cruickshank wrote: > More stuff: > > The 'Manage block types' option at the foot of the blockAdmin screen needs altered to allow for the fact that Block_render_***.class has to be manually registered with the resource engine by editing config.php. I cant think of a neat way round it, short of storing block classnames in the database/cache, or dropping it altogether + replacing with a HOWTO doc. > Already addressed in cvs: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpslash/phpslash-ft/class/Block.class.diff?r1=1.24&r2=1.25 > Another Win98Special > The new slashSess gives problems with session save path (giving error "Failed to write session data (files)."*) - solved by swapping in the old slashSess from PSL 0.6.5 (so it's not down to php.ini settings). But then of course, the class lists arent loaded using the old slashSess, so I cant do anything... google brought up loads of unresolved problems with this, so I've switched to developing in Unix. > So the php install doesn't have write access to a default session save path? 1) set it where it can save it. or 2) Change config.php to call session.inc, auth.inc, page.inc instead. They are just commented out. This would revert to previous sessions. http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpslash/phpslash-ft/public_html/config-dist.php3.diff?r1=1.30&r2=1.26 or 3) Change config.php and session.inc to use session4_custom.inc so phplib can store php4 sessions in the db. > But it would be interesting to know if there are any other Windows users out there to find if this is a real problem, or specific to my config. > > tobozo has been running winders too. > P > > |
From: Peter C. <li...@kr...> - 2003-02-10 21:15:45
|
At 12:41 10/02/03 -0600, Joe Stewart wrote: >On Mon, Feb 10, 2003 at 06:25:13PM +0000, Peter Cruickshank wrote: >> More stuff: >> >> The 'Manage block types' option at the foot of the blockAdmin screen needs altered to allow for the fact that Block_render_***.class has to be manually registered with the resource engine by editing config.php. I cant think of a neat way round it, short of storing block classnames in the database/cache, or dropping it altogether + replacing with a HOWTO doc. >> > >Already addressed in cvs: > >http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpslash/phpslash-ft/class/Block.class.diff?r1=1.24&r2=1.25 OK. > Another Win98Special >> The new slashSess gives problems with session save path (giving error "Failed to write session data (files)."*) - solved by swapping in the old slashSess from PSL 0.6.5 (so it's not down to php.ini settings). But then of course, the class lists arent loaded using the old slashSess, so I cant do anything... google brought up loads of unresolved problems with this, so I've switched to developing in Unix. >> > >So the php install doesn't have write access to a default session save >path? <snip> Fair points all... I'll have a look sometime to see what fixes it. >> But it would be interesting to know if there are any other Windows users out there to find if this is a real problem, or specific to my config. >> >> > >tobozo has been running winders too. ... so it's only a problem with my setup, not an issue. Cool. Peter |