phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Version Module, Was: Workflow

[Wendall C. <wen...@to...>]

On Thu, 2004-12-02 at 21:28 +0000, chris mcginlay wrote:
> Thanks Matt for the explanation of Version. I have had a look at it on CVS. Am 
> I right in saying that its not in the 0.10.0 stable, but *only* in CVS atm?  

That's right. You'll want to look at fallout in cvs. This is Matt's test
code for a future release.

Wendall

[Phpwebsite-developers] Version Module, Was: Workflow

[chris m. <ro...@as...>]

Hi,

Thanks Matt for the explanation of Version. I have had a look at it on CV=
S. Am=20
I right in saying that its not in the 0.10.0 stable, but *only* in CVS at=
m? =20

Cheers

Chris

--=20
www.lets-sell.it
www.ascentsoftware.org.uk
Standards Compliant Web Design
Open Source Proponents

Re: [Phpwebsite-developers] CVS Restuctured

[Ryan R. <to...@gm...>]

Looks excellent.  Congrats on some serious shuffling skills.  You guys
work weekends in Vegas? :)

Thanks for the work,

Ryan Roland

Indiana University


On Thu, 02 Dec 2004 14:56:31 -0500, Steven Levin
<st...@tu...> wrote:
> Hello Everyone,
> 
>   Mike Noyes and I heavily restructured the phpwebsite repository today
> to clean things up and make it easier to understand.
> 
> Changes include:
> - phpwebsite094 (aka. 1.0.0) moved to fallout
> - fallout will always be the name for unstable code (like Debian Sid)
> - all current modules have been placed in a separate modules directory
> - manual and convert have their own repositories
> 
> The themes repository has stayed the same.
> 
> What this means to you:
> - easier navigation of cvs via horde's chora browser
> - if you have a co of phpwebsite-full, phpwebsite-core, or fallout you
> will need to do a fresh co and copy back over any php files you may have
> modified.
> 
> Cheers!
> 
> --
> Steven Levin
> Computer Systems Admin I
> Electronic Student Services
> Appalachian State University
> http://phpwebsite.appstate.edu
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

[Phpwebsite-developers] CVS Restuctured

[Steven L. <st...@tu...>]

Hello Everyone,

  Mike Noyes and I heavily restructured the phpwebsite repository today
to clean things up and make it easier to understand.

Changes include:
- phpwebsite094 (aka. 1.0.0) moved to fallout
- fallout will always be the name for unstable code (like Debian Sid)
- all current modules have been placed in a separate modules directory
- manual and convert have their own repositories

The themes repository has stayed the same.

What this means to you:
- easier navigation of cvs via horde's chora browser
- if you have a co of phpwebsite-full, phpwebsite-core, or fallout you
will need to do a fresh co and copy back over any php files you may have
modified.

Cheers!

-- 
Steven Levin
Computer Systems Admin I
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu

Re: [Phpwebsite-developers] Rules idea

[Wendall C. <wen...@to...>]

On Thu, 2004-12-02 at 17:34 +0000, Shaun Murray wrote:
> One thought I had was that when you've got the layout panel switched  
> on, as well as being able to change the box style and position, you'd  
> be able to change the rules for that block directly in situ if it was  
> entirely at the layout level. That'd be nice and easy to visually  
> modify the sites rules rather than from inside each modules admin page.

A Layout lib to handle creating the settings would be great. The
settings would be more like how setting categories with fatcat within a
module are now. This would save a ton of coding on the module author's
part and give a standard method for placement. I really like the idea of
being able to change placement by editing the item or straight from
layout.

Wendall

Re: [Phpwebsite-developers] Rules idea

[Shaun M. <sh...@ae...>]

On 2 Dec 2004, at 17:12, Wendall Cada wrote:

> One other item I wanted to discuss is category. I haven't added  
> category
> placement for on major reason.
>
> What do I base the category from? The Web Pages item? The Article
> Manager Article? If any item on the page is in that category? I'm
> assuming you mean if any item on the page is in that category.

That's a good point. Since you can have multiple categories on the page  
that could be a nightmare. I'm not sure how the current category hacks  
work exactly. See  
http://www.phpwebsitemanual.com/index.php? 
module=announce&ANN_user_op=view&ANN_id=181 for the menuman hack. I've  
not used it myself as it interfered with my pagemaster menu hack. ;-)


> I just
> don't know how realistic this would be to do though without a lot of
> thought going into the design. Unless it is done properly, the amount  
> of
> database queries to check categories would be insane. It's almost a
> catch-22. The list of categories for every item sent to layout would
> need to be available before the items were generated for layout on the
> page. I'm not certain how you'd achieve this effectively. My current
> method checks the current module in the $_REQUEST var against each  
> items
> setting. It does the same for webpages. Checks the $_REQUEST var to see
> if a page has been requested and generates a block or body element.  
> This
> is a very weak method. It would be much stronger if, as I think Shawn  
> is
> suggesting. There was a table or set of tables for Layout to check for
> advanced layout and automagically fetched the items from all mods. This
> could even further reduce the impact of inc/runtime.php to mostly be
> used for module administrative tasks, lists and item views. As it is,
> there could be a ton of overhead processing each inc/runtime.php if  
> they
> are all banging against the database to retrieve settings for dynamic
> placement.
>

Yep, I alluded to it being part of layout in the first post but then  
thought it might be useful at a finer grained level than at a block  
level.

One thought I had was that when you've got the layout panel switched  
on, as well as being able to change the box style and position, you'd  
be able to change the rules for that block directly in situ if it was  
entirely at the layout level. That'd be nice and easy to visually  
modify the sites rules rather than from inside each modules admin page.


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Rules idea

[Shaun M. <sh...@ae...>]

On 2 Dec 2004, at 16:38, Wendall Cada wrote:

> Shaun,
>
> This is a great idea. I can code the concept into phpwsRSSFeeds for now
> as a demo.

That would be cool.

> I agree that there needs to be methods for doing this
> consistently across the board. I think the way it is done should be
> planned and not an afterthought for certain. Maybe we could create a
> register table for item placement. So there is just one query to the
> database per page view to determine placement of items for all modules.
>

Yeah, I'd much rather something was done across the board in such a way 
that it's flexible enough for the future but if we can get it going as 
a prototype at least we know what the pitfalls will be.


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Rules idea

[Wendall C. <wen...@to...>]

One other item I wanted to discuss is category. I haven't added category
placement for on major reason. 

What do I base the category from? The Web Pages item? The Article
Manager Article? If any item on the page is in that category? I'm
assuming you mean if any item on the page is in that category. I just
don't know how realistic this would be to do though without a lot of
thought going into the design. Unless it is done properly, the amount of
database queries to check categories would be insane. It's almost a
catch-22. The list of categories for every item sent to layout would
need to be available before the items were generated for layout on the
page. I'm not certain how you'd achieve this effectively. My current
method checks the current module in the $_REQUEST var against each items
setting. It does the same for webpages. Checks the $_REQUEST var to see
if a page has been requested and generates a block or body element. This
is a very weak method. It would be much stronger if, as I think Shawn is
suggesting. There was a table or set of tables for Layout to check for
advanced layout and automagically fetched the items from all mods. This
could even further reduce the impact of inc/runtime.php to mostly be
used for module administrative tasks, lists and item views. As it is,
there could be a ton of overhead processing each inc/runtime.php if they
are all banging against the database to retrieve settings for dynamic
placement.

Wendall

On Thu, 2004-12-02 at 08:38 -0800, Wendall Cada wrote:
> Shaun,
> 
> This is a great idea. I can code the concept into phpwsRSSFeeds for now
> as a demo. I agree that there needs to be methods for doing this
> consistently across the board. I think the way it is done should be
> planned and not an afterthought for certain. Maybe we could create a
> register table for item placement. So there is just one query to the
> database per page view to determine placement of items for all modules.
> 
> Wendall
> 
> On Thu, 2004-12-02 at 04:16 +0000, Shaun Murray wrote:
> > This is an idea that's been kicking about my head for a while so I 
> > thought I'd let it out there.
> > 
> > Currently, some modules allow you to display a block, menu or other 
> > element if another module is on the screen. eg. you can display a menu 
> > with just the linkman module or a block only with announcements.
> > 
> > Some others, allow you to display an element depending on a pagemaster 
> > page - see phpwsRSSFeeds and kCart.
> > 
> > There are hacks from users to display blocks, menus etc depending on 
> > the category, if the user is an admin and other kinds of permission 
> > levels.
> > 
> > These are mostly hacked on afterwards and the interface is often 
> > different and confusing and mixing all the possible conditions in one 
> > interface isn't always simple. In an effort to homogenise these all 
> > into one interface, and perhaps this will fit in with v1.0.0 
> > permissions too,  I thought perhaps we could use a rule based method. 
> > The inspiration was Apple's Mail filtering rules for those familiar 
> > with the idea.
> > 
> > Here's a non-functioning mockup in html
> > 
> > http://www.aegisdesign.co.uk/examples/rules/
> > 
> > To explain,
> > 
> > This would be displayed instead of the 'Allow View' option in 
> > blockmaker for example. You click 'enable rules' to switch on the rules 
> > otherwise the default is to always display the element. You can add or 
> > remove rules using the -/+ buttons allowing quite a complex set. I've 
> > added some examples for common things you'd maybe filter on. The 
> > multi-select lists have to be generated when the user changes the 
> > filter type - eg. if they select category, it fills the list with 
> > categories, if they select pages, it fills with pagemaster pages.
> > 
> > That's the idea. I can see a couple of problems with it already but 
> > maybe they can be overcome.
> > 
> > 1) selecting a user from a list of a couple of thousand is not viable - 
> > see the Notes module for how that was addressed.
> > 
> > 2) you might want to filter on a text field - eg. pagemaster page where 
> > title begins with/contains 'some text'
> > 
> > 
> > For the core, I'd guess this is some part of layout in that it would 
> > keep a list of elements and if they were rule enabled or not. Or 
> > perhaps this is useful at a module level so that individual content is 
> > rule based also. A table somewhere else stores the rules.
> > 
> > For the module developer, it'd be as simple to add in rules editing to 
> > their module as they can with fatcat now.
> > 
> > 
> > Thoughts anyone?
> > 
> > 
> > Shaun
> > aegis design - http://www.aegisdesign.co.uk
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from real users.
> > Discover which products truly live up to the hype. Start reading now. 
> > http://productguide.itmanagersjournal.com/
> > _______________________________________________
> > Phpwebsite-developers mailing list
> > Php...@li...
> > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] Rules idea

[Wendall C. <wen...@to...>]

Shaun,

This is a great idea. I can code the concept into phpwsRSSFeeds for now
as a demo. I agree that there needs to be methods for doing this
consistently across the board. I think the way it is done should be
planned and not an afterthought for certain. Maybe we could create a
register table for item placement. So there is just one query to the
database per page view to determine placement of items for all modules.

Wendall

On Thu, 2004-12-02 at 04:16 +0000, Shaun Murray wrote:
> This is an idea that's been kicking about my head for a while so I 
> thought I'd let it out there.
> 
> Currently, some modules allow you to display a block, menu or other 
> element if another module is on the screen. eg. you can display a menu 
> with just the linkman module or a block only with announcements.
> 
> Some others, allow you to display an element depending on a pagemaster 
> page - see phpwsRSSFeeds and kCart.
> 
> There are hacks from users to display blocks, menus etc depending on 
> the category, if the user is an admin and other kinds of permission 
> levels.
> 
> These are mostly hacked on afterwards and the interface is often 
> different and confusing and mixing all the possible conditions in one 
> interface isn't always simple. In an effort to homogenise these all 
> into one interface, and perhaps this will fit in with v1.0.0 
> permissions too,  I thought perhaps we could use a rule based method. 
> The inspiration was Apple's Mail filtering rules for those familiar 
> with the idea.
> 
> Here's a non-functioning mockup in html
> 
> http://www.aegisdesign.co.uk/examples/rules/
> 
> To explain,
> 
> This would be displayed instead of the 'Allow View' option in 
> blockmaker for example. You click 'enable rules' to switch on the rules 
> otherwise the default is to always display the element. You can add or 
> remove rules using the -/+ buttons allowing quite a complex set. I've 
> added some examples for common things you'd maybe filter on. The 
> multi-select lists have to be generated when the user changes the 
> filter type - eg. if they select category, it fills the list with 
> categories, if they select pages, it fills with pagemaster pages.
> 
> That's the idea. I can see a couple of problems with it already but 
> maybe they can be overcome.
> 
> 1) selecting a user from a list of a couple of thousand is not viable - 
> see the Notes module for how that was addressed.
> 
> 2) you might want to filter on a text field - eg. pagemaster page where 
> title begins with/contains 'some text'
> 
> 
> For the core, I'd guess this is some part of layout in that it would 
> keep a list of elements and if they were rule enabled or not. Or 
> perhaps this is useful at a module level so that individual content is 
> rule based also. A table somewhere else stores the rules.
> 
> For the module developer, it'd be as simple to add in rules editing to 
> their module as they can with fatcat now.
> 
> 
> Thoughts anyone?
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] Rules idea

[Ryan R. <to...@gm...>]

+1  on this one.   Something we've been looking at for awhile.  I like
this approach as well.

Ryan Roland

Indiana University

On Thu, 2 Dec 2004 04:16:36 +0000, Shaun Murray <sh...@ae...> wrote:
> This is an idea that's been kicking about my head for a while so I
> thought I'd let it out there.
> 
> Currently, some modules allow you to display a block, menu or other
> element if another module is on the screen. eg. you can display a menu
> with just the linkman module or a block only with announcements.
> 
> Some others, allow you to display an element depending on a pagemaster
> page - see phpwsRSSFeeds and kCart.
> 
> There are hacks from users to display blocks, menus etc depending on
> the category, if the user is an admin and other kinds of permission
> levels.
> 
> These are mostly hacked on afterwards and the interface is often
> different and confusing and mixing all the possible conditions in one
> interface isn't always simple. In an effort to homogenise these all
> into one interface, and perhaps this will fit in with v1.0.0
> permissions too,  I thought perhaps we could use a rule based method.
> The inspiration was Apple's Mail filtering rules for those familiar
> with the idea.
> 
> Here's a non-functioning mockup in html
> 
> http://www.aegisdesign.co.uk/examples/rules/
> 
> To explain,
> 
> This would be displayed instead of the 'Allow View' option in
> blockmaker for example. You click 'enable rules' to switch on the rules
> otherwise the default is to always display the element. You can add or
> remove rules using the -/+ buttons allowing quite a complex set. I've
> added some examples for common things you'd maybe filter on. The
> multi-select lists have to be generated when the user changes the
> filter type - eg. if they select category, it fills the list with
> categories, if they select pages, it fills with pagemaster pages.
> 
> That's the idea. I can see a couple of problems with it already but
> maybe they can be overcome.
> 
> 1) selecting a user from a list of a couple of thousand is not viable -
> see the Notes module for how that was addressed.
> 
> 2) you might want to filter on a text field - eg. pagemaster page where
> title begins with/contains 'some text'
> 
> For the core, I'd guess this is some part of layout in that it would
> keep a list of elements and if they were rule enabled or not. Or
> perhaps this is useful at a module level so that individual content is
> rule based also. A table somewhere else stores the rules.
> 
> For the module developer, it'd be as simple to add in rules editing to
> their module as they can with fatcat now.
> 
> Thoughts anyone?
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>

[Phpwebsite-developers] Rules idea

[Shaun M. <sh...@ae...>]

This is an idea that's been kicking about my head for a while so I 
thought I'd let it out there.

Currently, some modules allow you to display a block, menu or other 
element if another module is on the screen. eg. you can display a menu 
with just the linkman module or a block only with announcements.

Some others, allow you to display an element depending on a pagemaster 
page - see phpwsRSSFeeds and kCart.

There are hacks from users to display blocks, menus etc depending on 
the category, if the user is an admin and other kinds of permission 
levels.

These are mostly hacked on afterwards and the interface is often 
different and confusing and mixing all the possible conditions in one 
interface isn't always simple. In an effort to homogenise these all 
into one interface, and perhaps this will fit in with v1.0.0 
permissions too,  I thought perhaps we could use a rule based method. 
The inspiration was Apple's Mail filtering rules for those familiar 
with the idea.

Here's a non-functioning mockup in html

http://www.aegisdesign.co.uk/examples/rules/

To explain,

This would be displayed instead of the 'Allow View' option in 
blockmaker for example. You click 'enable rules' to switch on the rules 
otherwise the default is to always display the element. You can add or 
remove rules using the -/+ buttons allowing quite a complex set. I've 
added some examples for common things you'd maybe filter on. The 
multi-select lists have to be generated when the user changes the 
filter type - eg. if they select category, it fills the list with 
categories, if they select pages, it fills with pagemaster pages.

That's the idea. I can see a couple of problems with it already but 
maybe they can be overcome.

1) selecting a user from a list of a couple of thousand is not viable - 
see the Notes module for how that was addressed.

2) you might want to filter on a text field - eg. pagemaster page where 
title begins with/contains 'some text'


For the core, I'd guess this is some part of layout in that it would 
keep a list of elements and if they were rule enabled or not. Or 
perhaps this is useful at a module level so that individual content is 
rule based also. A table somewhere else stores the rules.

For the module developer, it'd be as simple to add in rules editing to 
their module as they can with fatcat now.


Thoughts anyone?


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Modules.

[Matthew M. <ma...@tu...>]

Your best bet would to go through the doc/ directories of the core and
the various modules. There is a lot of information there. I would also
recommend looking at a simple module (like FAQ) to see how they work.
Finally, open up the skeleton module. It is extremely basic and gives a
decent overview of what is required.

On Wed, 2004-12-01 at 03:41, Patrick Twohig wrote:
> Sorry guys if this is a dumb question, but I'm looking to write a module 
> for my phpWebSite driven site, and I was wondering where there may be a 
> HOWTO file of some sort that would ouline exactly how to go about 
> writing a module.  I'm not very good at PHP, but I know other languages 
> failry well and I'd be able to figure it out.  I just would like to know 
> if there is a good place to start.
> 
> Thanks.
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

[Phpwebsite-developers] Modules.

[Patrick T. <pa...@se...>]

Sorry guys if this is a dumb question, but I'm looking to write a module 
for my phpWebSite driven site, and I was wondering where there may be a 
HOWTO file of some sort that would ouline exactly how to go about 
writing a module.  I'm not very good at PHP, but I know other languages 
failry well and I'd be able to figure it out.  I just would like to know 
if there is a good place to start.

Thanks.

[Phpwebsite-developers] Re: Workflow

[chris m. <ro...@as...>]

On Monday 29 November 2004 06:33,=20
php...@li... wrote:

Wendall et. al.: thanks I will go for a look at the CVS next.

Chris


> Send Phpwebsite-developers mailing list submissions to
> =09p...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> =09https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> or, via email, send a message with subject or body 'help' to
> =09p...@li...
>
> You can reach the person managing the list at
> =09p...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Phpwebsite-developers digest..."
>
>
> Today's Topics:
>
>    1. Re: Workflow (Wendall Cada)
>
> --__--__--
>
> Message: 1
> Subject: Re: [Phpwebsite-developers] Workflow
> From: Wendall Cada <wen...@to...>
> To: phpws dev list <php...@li...>
> Date: Sat, 27 Nov 2004 14:34:14 -0800
> Reply-To: php...@li...
>
> Chris,
>
> Matt has completed much of the workflow/approval functionality in cvs
> for the pre 1.0 release. He can explain the functionality much better
> than I can. I'm unsure about edit-locking. The current code base will
> most likely not see any improvements other than bug fixes.
>
> Wendall
>
> On Sat, 2004-11-27 at 12:46 +0000, chris mcginlay wrote:
> > Hello,
> >
> > I am interested to know what plans for improved workflow / 'approval'=
 are
> > in the pipeline. Since I need these features I would be willing to wr=
ite
> > some of the code. I had in mind a transaction database, or at least a
> > transaction table along with an edit-locking mechanism. Upon approval
> > entries in the transaction table would be commited to the database an=
d
> > the edit-lock removed.
> >
> > What I don't know is if there are any plans already that I could disc=
uss.
> >
> > Thanks
> >
> > Chris
>
> --__--__--
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
> End of Phpwebsite-developers Digest

--=20
www.lets-sell.it
www.ascentsoftware.org.uk
Standards Compliant Web Design
Open Source Proponents

Re: [Phpwebsite-developers] Workflow

[Matthew M. <ma...@tu...>]

Ok here is how it works.

There is a module called Version. It handles two main components: 1)
backing up old material, 2) controlling approval.

There are two types of rights in 1.0.0. A user can be restricted or
unrestricted. An unrestricted user can perform all the permissions
assigned to them without impediment. A restricted user's permissions
apply only to items assigned by an unrestricted user.

For example, I am unrestricted. I create a announcement about
phpwebsite. Steven is restricted. He has edit permissions. If I give him
permission to edit the announcement about phpwebsite, he may do so but
ONLY for that item.

If Steven makes an edit of my announcement, Version makes an unapproved
version of the original. Now when I go back in I can:
1) edit his unapproved changes and leave it unapproved,
2) edit (or not) his changes and approve the announcement,
3) decline his changes.

If approved, his version replaces the announcement. Any approved
announcements (including mine which would be pre-approved) are backed up
as versions. If I wish to restore to a previous version, I go to my
version list and pick the one I want to restore.

The above is already written. The next step is coding the Workflow
module. This module will allow you to create a group of individuals who
have 'steps' and will work with Version. As people work on an item, it
is passed to the next person in the chain for approval.
I will reveal more once I get into it.

As a heads up, I am going back to testing under Postgres as I have been
using MYSQL for a bit. Once I get that working (the code isn't lacking,
it's my understanding of postgres), I am returning to work on
Categories. Once finished, it will replace FatCat and I can start
writing the crutch files for it. We will be really close to backward
compatibility at that point.

Matt

On Sat, 2004-11-27 at 19:55, Shaun Murray wrote:
> On 27 Nov 2004, at 12:46, chris mcginlay wrote:
> 
> > Hello,
> >
> > I am interested to know what plans for improved workflow / 'approval' 
> > are in
> > the pipeline. Since I need these features I would be willing to write 
> > some of
> > the code. I had in mind a transaction database, or at least a 
> > transaction
> > table along with an edit-locking mechanism. Upon approval entries in 
> > the
> > transaction table would be commited to the database and the edit-lock
> > removed.
> >
> > What I don't know is if there are any plans already that I could 
> > discuss.
> 
> Matt's been sorting out Workflow and also revision control for v1.0 
> (the release formally known as v0.9.4). I don't know if it's in the 
> phpwebsite094 cvs folder already but Matt's your man to discuss it 
> with.
> 
> 
> Shaun
> aegis design - http://www.aegisdesign.co.uk
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

Re: [Phpwebsite-developers] Calendar

[Matthew M. <ma...@tu...>]

Thank you Wendall for testing.

Calendar can start singing "Tomorrow" because I am definitely orphaning
it. It is bloated and old.

I vote we forget about 0.9.x fully working in php 5.0 and let 1.0.0
accept that responsibility.

Matt

On Sat, 2004-11-27 at 19:56, Wendall Cada wrote:
> Calendar is broken for php5. Everything else I've tested appears to be
> ok. I have a test bed setup for php5. Found a small bug in phpwsRSSFeeds
> and fixed it. Am hoping to not get too many reports on it. Anyway, I can
> spend some time on fixing Calendar. Should I do this, or does someone at
> ASU want the job? It may be best to orphan it for use with php5 and
> focus attention on Matt's release. Thoughts?
> 
> Wendall
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
-- 
Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
http://phpwebsite.appstate.edu
http://ess.appstate.edu

Re: [Phpwebsite-developers] Workflow

[Wendall C. <wen...@to...>]

Chris,

Matt has completed much of the workflow/approval functionality in cvs
for the pre 1.0 release. He can explain the functionality much better
than I can. I'm unsure about edit-locking. The current code base will
most likely not see any improvements other than bug fixes.

Wendall

On Sat, 2004-11-27 at 12:46 +0000, chris mcginlay wrote:
> Hello,
> 
> I am interested to know what plans for improved workflow / 'approval' are in 
> the pipeline. Since I need these features I would be willing to write some of 
> the code. I had in mind a transaction database, or at least a transaction 
> table along with an edit-locking mechanism. Upon approval entries in the 
> transaction table would be commited to the database and the edit-lock 
> removed.
> 
> What I don't know is if there are any plans already that I could discuss.
> 
> Thanks
> 
> Chris
> 

[Phpwebsite-developers] Calendar

[Wendall C. <wen...@to...>]

Calendar is broken for php5. Everything else I've tested appears to be
ok. I have a test bed setup for php5. Found a small bug in phpwsRSSFeeds
and fixed it. Am hoping to not get too many reports on it. Anyway, I can
spend some time on fixing Calendar. Should I do this, or does someone at
ASU want the job? It may be best to orphan it for use with php5 and
focus attention on Matt's release. Thoughts?

Wendall

Re: [Phpwebsite-developers] Workflow

[Shaun M. <sh...@ae...>]

On 27 Nov 2004, at 12:46, chris mcginlay wrote:

> Hello,
>
> I am interested to know what plans for improved workflow / 'approval' 
> are in
> the pipeline. Since I need these features I would be willing to write 
> some of
> the code. I had in mind a transaction database, or at least a 
> transaction
> table along with an edit-locking mechanism. Upon approval entries in 
> the
> transaction table would be commited to the database and the edit-lock
> removed.
>
> What I don't know is if there are any plans already that I could 
> discuss.

Matt's been sorting out Workflow and also revision control for v1.0 
(the release formally known as v0.9.4). I don't know if it's in the 
phpwebsite094 cvs folder already but Matt's your man to discuss it 
with.


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Version Check FYI

[Shaun M. <sh...@ae...>]

On 27 Nov 2004, at 14:31, George Brackett wrote:

> How far back in the phpWS versions is version_compare() available?

version_compare() is a PHP function, not phpwebsite, so any PHP v4.1 or 
later installation will have it.

See http://uk.php.net/manual/en/function.version-compare.php for more 
info.


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Version Check FYI

[George B. <gbr...@lu...>]

How far back in the phpWS versions is version_compare() available?

On 11/11/04 4:18 PM, "Steven Levin" <st...@tu...> wrote:

> I just wanted to let all third party module developers know that the
> next core version of phpwebsite will be going up to 0.10.0   What this
> means is that the old way of checking versions will no longer work and
> you encouraged to start using version_compare()
> 
> Old core version check:
> 
> if ($GLOBALS['core']->version < "0.9.3-2") {
>   echo "You must upgrade to version 0.9.3-2 or greater to install this
> module.";
> }
> 
> This should be updated to:
> 
> if (version_compare($GLOBALS['core']->version, "0.9.3-2") < 0) {
>   echo "You must upgrade to version 0.9.3-2 or greater to install this
> module.";
> }
> 
> You should also start using version_compare() in your update.php files
> if you are going to follow the X.X.X version scheme.
> 
> Thanks to rhalff and rizzo for their help with this issue.

______________________________________
George Brackett, Principal
George Brackett Associates
617 413 4316 / gbr...@lu...
http://www.luceatlux.com/gba/

[Phpwebsite-developers] Workflow

[chris m. <ro...@as...>]

Hello,

I am interested to know what plans for improved workflow / 'approval' are=
 in=20
the pipeline. Since I need these features I would be willing to write som=
e of=20
the code. I had in mind a transaction database, or at least a transaction=
=20
table along with an edit-locking mechanism. Upon approval entries in the=20
transaction table would be commited to the database and the edit-lock=20
removed.

What I don't know is if there are any plans already that I could discuss.

Thanks

Chris

--=20
www.lets-sell.it
www.ascentsoftware.org.uk
Standards Compliant Web Design
Open Source Proponents

Re: [Phpwebsite-developers] Moving PHP Website to another machine

[Shaun M. <sh...@ae...>]

On 22 Nov 2004, at 18:42, Scott Sherrill wrote:

>> That's the problem. I can login to the db just fine from the command 
>> line.
>
> Another thing to check - do you have the php/mysql libraries installed 
> on your machine?  Without them, phpWebsite can look correct but will 
> not connect to the server.

It's not uncommon that a particular OS distribution or version of PHP 
doesn't have MySQL built in to PHP. Could be that you'll need to 
recompile PHP. IIRC PHP5 may not have MySQL built in.

Ruben, have a look at http://www.yoursite.com/setup/phpinfo.php and 
check that MySQL is there and that you're running the same setup as the 
server that works.

Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] Moving PHP Website to another machine

[Scott S. <sc...@ha...>]

>That's the problem. I can login to the db just fine from the command line.

Another thing to check - do you have the php/mysql libraries 
installed on your machine?  Without them, phpWebsite can look correct 
but will not connect to the server.

On Redhat, Fedora or other rpm based linux you need the package php-mysql

rpm -qi php-mysql


will tell you if it's installed.


Had the same problem happen, everything fine on the command line, 
but when I ran phpwebsite just wouldn't connect, and the solution was 
I didn't have the php-mysql libraries installed.


Scott




-- 
--
Scott Sherrill
Technology Coordinator Hancock Public Schools
Hancock, MI
http://www.hancock.k12.mi.us

Re: [Phpwebsite-developers] Moving PHP Website to another machine

[Ruben F. <rfa...@np...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Timothy, <br>
<br>
That's exactly what I needed to know. I had not been able to find where
the username was stored, and once you pointed this out, I resolved the
problem. Thanks so much for your help. I really appreciate it. <br>
<br>
Ruben<br>
<br>
Timothy Pearson wrote:
<blockquote cite="mid...@mw..." type="cite">
  <pre wrap="">When you set up the initial configuration, did you specify "localhost"
or a domain name or an IP address?  Localhost should work if you created
a user on the new box from "localhost" with permissions to the database.
 If it was a domain name, then you would have to modify your DNS server
so that that name now pointed to the IP address of the new machine.  If
it was by IP address, then the new machine would have to have the same
IP address as the original one.

However, it is *really* easy to simply edit the configuration files to
match your current setup.  You will find there are two places you should
look at: 

One is in the website's conf directory, a file called config.php.  Open
it with your favorite ASCII text editor and check that everything is
correct.  I mean everything, including the source-http and source-dir
keywords as well as the database stuff.

The other is in the core directory called core.php.  Open it the same
way and check that the path information is correct for your new setup.

If you're still having problems, try creating a user from % as well as
one from "localhost" (same user name and password and permissions - just
allow the user to be from anywhere (%) instead of restricting them to be
only from "localhost").

Good luck!



Timothy Pearson
Midwestern Telephone, Inc.

E-mail: <a class="moz-txt-link-abbreviated" href="mailto:ti...@mw...">ti...@mw...</a>
Web: <a class="moz-txt-link-freetext" href="http://mwtel.com/">http://mwtel.com/</a> -or-
          <a class="moz-txt-link-freetext" href="http://InformationTransportation.com/">http://InformationTransportation.com/</a>
Phone: 417-673-1977 Ext. 2203
Fax: 417-673-1978

  </pre>
  <blockquote type="cite">
    <blockquote type="cite">
      <blockquote type="cite">
        <pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:rfa...@np...">rfa...@np...</a> 11/19/2004 9:28:04 AM &gt;&gt;&gt;
        </pre>
      </blockquote>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->I have what should be a very simple problem, but I just have not been 
able to figure this out.

I wanted to move a PHP Website site to another machine, and I dumped
the 
database, and copied all the files. I placed everything in the same 
directory structure as the original setup.

I have the same logins for MySQL on both boxes, and I created a 2nd 
level domain name to the new box, but every time I try and access the 
2nd box, I get this message.

Unable to load database indicated by configuration file.

The databases have exactly the same name. So, what am I doing wrong in

trying to move this web site to a new box ? I must be missing something

simple ? Any suggestions on where to start debugging this. I'm not 
seeing any useful errors in the apache log files. I'm running MySQL 4
on 
both boxes. Old box is Redhat 9 and new box is Fedora C 2

Thanks for your help,
Ruben





-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. <a class="moz-txt-link-abbreviated" href="http://www.intersystems.com/match8">www.intersystems.com/match8</a> 
_______________________________________________
Phpwebsite-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Php...@li...">Php...@li...</a> 
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers">https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers</a>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest &amp; candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
<a class="moz-txt-link-freetext" href="http://productguide.itmanagersjournal.com/">http://productguide.itmanagersjournal.com/</a>
_______________________________________________
Phpwebsite-developers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Php...@li...">Php...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers">https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers</a>


  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
Ruben Fagundo
NPV Corporation

Tel: 617-848-0890 x100
Fax: 617-249-1994


</pre>
</body>
</html>