phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

Very good article Michael. I'll add my comments on top of Matt's since I
agree with most of his comments and add my own observations.

> Titles
> -------------------
> Currently I am using the Control Panel (which is pure line item CSS)
> wrapped around each of my modules.
> 
> I like this format because:
> 1) You don't have to click on Control Panel every time you want to go
>    to another module. Just click back on Content. 
> 
> 2) It allows us to have the same options on every page in the same
>    place.
> 
> 3) It eliminates the Back to Main junk. The tabs always take you where
>    you want to go.
> 
I have used this system helping with some testing for Matt. It increases
the usability of the control panel incredibly.  It is very expandable
and easy to navigate. It addresses many concerns about consistency since
it wraps all administrative stuff with a common interface.

> In reference to the Add [something], Edit [something], etc. In all my
> new modules 'New' is used to create a new item. I think all my mods
> have that same tab and I would support use of this word for English
> modules. We can discuss whether 'New', 'Create', or 'Add' is the
> better word and whether the name of the item should be suffixed to the
> command.

I don't have any recommendations on English words for basic stuff, but
 we do need to decide on wording for add, save, update, view, edit,
 delete, show, hide, settings, etc. And these should be consistent
 across modules.

*Side Note: It would be nice if Matt added recommendations for
consistent function naming for these in the module creation guide.

> I would also like to agree on a standard for the listing of items. I
> am using Archive in Blog and List in Categories. We can agree on a
> standard for this tab. For editing and deleting however, those options
> are listed along with the items. When chosen, the edit form opens
> within the List tab. 

It would be nice to use the same list for everything. However, the list
does need to be flexible enough to accommodate all uses. For example,
what if I wanted to do list sorting. Not just sort the display order,
but actually change entry order in the database. Currently, there is no
method to do this and List is too inflexible to really allow this. Also,
I wanted to create a list that used different text parsing for a field,
so the only way to change it currently was to create my own List, which
is just a copy of List.php with modifications. I'd like to get away from
that sort of thing entirely. Steven and I have discussed this quite a
bit and I feel it will be resolved in 1.0, so I'm not too worried, just
wanted to give some examples. I don't necessarily think that List should
include everything and the kitchen sink for what just a few mods would
use, but I do think it should be flexible enough to do anything
necessary with the list that is required for the mod, without forcing
the developer to use another List lib. From a layout perspective, I
fully agree that some of the columns need to be fixed and others float. 

> Lists
> ----------------------------
> For empty lists, I vote for showing the column headings basically
> because the DBPager (a new listing class for 1.x) works well with this
> option. Also, DBPager uses only one template file.
> 
Maybe a default message advising the user that there are no items
available for view currently. This leads into another subject, but it
might be nice to have a nice list of canned English phrases for use.
This would come in handy for me. I am sure for those who English isn't
their first language, a list of standardized phrases would be useful as
well.

> Input
> ----------------------
> I have no problem with the first form style:
> 
> Name
> _____________
> |            
> 
> Address
> _____________
> |
> 
> I will say, however that the grid format is, imho, easier to
> navigate. I will leave this open to debate. I could go either way.
> 
> I agree with no background color, no enumeration, no colons,
> and no emphasis on the form labels.

I tried to implement an experimental tableless grid layout in the
phpwsRSSFeeds admin side of things. I know it has problems, and I fully
agree with the recommendations in the article. I also have no problem
with the first form style, assuming that the form is very simple. Once
the interface becomes more complex, it is hard to use many other styles
other than the grid style. I think that some sample forms should be put
together to illustrate some real life examples. I have no problem
implementing any ideas into rssfeeds for testing and feedback if someone
wants to point out changes.

Major problem in implementation for phpwsRSSFeeds was a lack of core
styles to build on and no full support for module level css. I believe
that these have already been addressed in large by Matt in 1.0.

> Checkboxes
> ----------------------
> I agree with everything here. Checkboxes should be placed before
> statement phrased as a question.
> 
> I also agree with only using checkboxes for boolean questions.

I agree here as well.

> 
> Buttons
> ---------------------
> I tend to prefer the button being set flush to the left. Because forms
> are often in a table, I like dropping the submit button after the
> closing of the table. The second example puts the button in the second
> column of a half completed row. I don't like that.

I tend to drop the button after the closing of the table as well.
However, I usually make the button centered. I do however agree that
flush left may be better. This may depend on what the grid layout is
like. For instance, if my text labels are right justify, and my input
fields are left justify, centering may make sense, as it follows layout.
However, I see no problem using left justify for everything.

> Buttons as links
> --------------------
> Agree 100%. Anything that does not pass form elements, doesn't need
> to be in a button.

Another point of note on this item. If an item does need to pass form
elements, but needs some type of user interaction, I'd like to see the
javascript popup dropped from use. A standardized form for user
confirmation would be very nice to have. Maybe as a part of Form.  

Another comment on the subject of forms. In the button example, there
are a couple samples of multiple forms on the same admin page. I'd like
to see this go away if possible. I made some of my own functions for
addition of fatcat categories in phpwsRSSFeeds so that the form elements
could be included in the item creation and editing forms, instead of an
additional form at the bottom of the page.

Wendall

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

> Matt,
> The one issue I have with the current fallout code is the core module
> css is dynamic. It isn't always available for other modules to use, or
> did I misunderstand something?
> I think core css should be static and persistent; so module and theme
> developers can utilize it, and build on it when necessary.

I'm not sure if I am answering this correctly so get back to me here if
I am wrong.

What exactly should be persistent? Tables? Fonts? I'm not grilling you,
I just need my memory refreshed on this discussion as I know we have had
it before. It would benefit those who read this list to hear it anyway
so please expand upon your question.

thanks,
Matt

-- 
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] Defining and implementing design standards in phpWebSite

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

> Whilst we're on the subject of Layout, is there anything on the radar 
> for allowing more than one theme.tpl (or whatever the basic structure 
> file is) where an admin gets to pick a different one depending on a 
> module/pagemaster page/category.

I am going to say yes because I know it has been requested. I will leave
it up to you to remind me of it though :)

-- 
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] Defining and implementing design standards in phpWebSite

[Mike N. <mh...@us...>]

On Tue, 2005-01-04 at 10:09, Matthew McNaney wrote:
> I would also like to agree on a standard for the listing of items. I
> am using Archive in Blog and List in Categories. We can agree on a
> standard for this tab. For editing and deleting however, those options
> are listed along with the items. When chosen, the edit form opens
> within the List tab. 

Matt,
The one issue I have with the current fallout code is the core module
css is dynamic. It isn't always available for other modules to use, or
did I misunderstand something?

I think core css should be static and persistent; so module and theme
developers can utilize it, and build on it when necessary.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

On 4 Jan 2005, at 18:42, Matthew McNaney wrote:
>
> for 1.x I am developing with just two major tags/columns and 2 minor.
>
> BODY - Unless defined otherwise, content will appear here.
> SIDEPANEL - smaller boxes usually are here
>
> The minors are HEADER and FOOTER. They are used by the Layout module,
> but are not required.
>

Hooray - always thought those were odd things to miss out.

> Other than that you can add as many other areas as you want, in any
> structure that you want.

Whilst we're on the subject of Layout, is there anything on the radar 
for allowing more than one theme.tpl (or whatever the basic structure 
file is) where an admin gets to pick a different one depending on a 
module/pagemaster page/category.

eg. Say I wanted a 3 column links page but just BODY for a pagemaster 
page.

Currently, it's quite a bit of work, and not entirely optimal to hack 
around the one theme.tpl limit using theme.php and a couple of module 
hacks to allow more specific menuman/block positioning. I really want 
to get away from the nuke-esque feel sometimes on some sites.

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

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

> I would also like to add theme "columnization" to the list on Michael's
> page.  How many default columns "should" there be?  Can phpWebSite's
> Layout module seamlessly handle three / two / one column themes?  What
> methodology can be used for those columns?  (left - middle/center -
> right) or (left - main - right) or some other variation?

for 1.x I am developing with just two major tags/columns and 2 minor.

BODY - Unless defined otherwise, content will appear here.
SIDEPANEL - smaller boxes usually are here

The minors are HEADER and FOOTER. They are used by the Layout module,
but are not required.

Other than that you can add as many other areas as you want, in any
structure that you want.

-- 
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] Defining and implementing design standards in phpWebSite

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

After reading Michaels Hjemmeside's article, here are my thoughts and
suggestions as they apply to 1.x. Some of these points will make more
sense when I can get a demo running.

Titles
-------------------
Currently I am using the Control Panel (which is pure line item CSS)
wrapped around each of my modules.

Looks something like the following

----------- ------------------
| Content | | Administration |
|         ---------------------------------------
|                                               |
|  [pic] Blog   [pic]Categories                 |


Once you get into a module, like Blog, you see this:

----------- ------------------
| Content | | Administration |
|         ---------------------------------------
|                                               |
| -------- -----------                          |
| | New  | | Archive |                          |
| |      -------------------------------------- |
| |                                           | |
| | NEW BLOG ENTRY                            | |
| | [form]                                    | |


I like this format because:
1) You don't have to click on Control Panel every time you want to go
   to another module. Just click back on Content. 

2) It allows us to have the same options on every page in the same
   place.

3) It eliminates the Back to Main junk. The tabs always take you where
   you want to go.

As for what is contained IN the embedded panel, it's template looks
like this:

<h1>{TITLE}</h1>
{CONTENT}

This template houses all administration done within the module.
The control panel is common. You CAN have your own control panel for
your module, but I am opting not to.

In reference to the Add [something], Edit [something], etc. In all my
new modules 'New' is used to create a new item. I think all my mods
have that same tab and I would support use of this word for English
modules. We can discuss whether 'New', 'Create', or 'Add' is the
better word and whether the name of the item should be suffixed to the
command.

I would also like to agree on a standard for the listing of items. I
am using Archive in Blog and List in Categories. We can agree on a
standard for this tab. For editing and deleting however, those options
are listed along with the items. When chosen, the edit form opens
within the List tab. 


Submenus
----------------------------
I think this is covered by the Control Panel method.


Lists
----------------------------
For empty lists, I vote for showing the column headings basically
because the DBPager (a new listing class for 1.x) works well with this
option. Also, DBPager uses only one template file.

Pattern
--------------------------
I would say most lists will look like the first example. All the
options for an item should appear together and to the extreme
right. If there are too many options per item, icons can be
substituted.

Also the second example is from Users, which has its own
listing class. Hopefully, we can get everyone to use the one listing
class in 1.x. 

Narrow Lists
-------------------------
Menu is an old module and its interface is definitely clunky. I think
we can steer clear of such things in the future.


Input
----------------------
I have no problem with the first form style:

Name
_____________
|            

Address
_____________
|

I will say, however that the grid format is, imho, easier to
navigate. I will leave this open to debate. I could go either way.

I agree with no background color, no enumeration, no colons,
and no emphasis on the form labels.


Checkboxes
----------------------
I agree with everything here. Checkboxes should be placed before
statement phrased as a question.

I also agree with only using checkboxes for boolean questions.


Buttons
---------------------
I tend to prefer the button being set flush to the left. Because forms
are often in a table, I like dropping the submit button after the
closing of the table. The second example puts the button in the second
column of a half completed row. I don't like that.

Buttons as links
--------------------
Agree 100%. Anything that does not pass form elements, doesn't need
to be in a button.


Tabbed Navigation
--------------------
See Control Panel info above. This has been implemented in 1.x. and
the class is easily accessible by other modules.


Tree Lists
-------------------
Agree here as well. Lists should be lists, not tables.



Conclusion
-------------------
I appreciate Michaels information. In our defense, many of the
examples are from older modules. We have learned a lot about CSS,
organization, interface, etc. since they were written years ago.

Since 1.x is getting closer to release, we have the opportunity to set
new guidelines benefiting developers and users alike.

Thanks,
Matt


-- 
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] Defining and implementing design standards in phpWebSite

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

> That's another one. I'd hope that the new layout engine just completely 
> drops the column thing and allows completely arbitrary areas on the 
> page in which blocks can be placed, with blocks that have no 'home' 
> defaulting to the bottom of the page perhaps rather than disappearing 
> into oblivion if your theme.tpl doesn't have that area defined. Instead 
> of the left/right arrows in layout for moving the block between 
> columns, you just have a pulldown list of the block names in which you 
> want to move it.

That is how it works, except the lost item is put in the BODY tag.

-- 
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] Defining and implementing design standards in phpWebSite

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

On 4 Jan 2005, at 03:09, Ken Nordquist wrote:
> How many times has a module's "theme" clashed with that of the main
> theme?  Where colors were hard-coded in the module instead of 
> defaulting
> to the theme?
>

That's another area that peeves me. Error messages are often hardcoded 
colours in some modules. IIRC there's a function call for displaying 
errors in the core already but it's rarely used. And IIRC there's a 
PEAR error message system too.

> I would also like to add theme "columnization" to the list on Michael's
> page.  How many default columns "should" there be?  Can phpWebSite's
> Layout module seamlessly handle three / two / one column themes?  What
> methodology can be used for those columns?  (left - middle/center -
> right) or (left - main - right) or some other variation?

That's another one. I'd hope that the new layout engine just completely 
drops the column thing and allows completely arbitrary areas on the 
page in which blocks can be placed, with blocks that have no 'home' 
defaulting to the bottom of the page perhaps rather than disappearing 
into oblivion if your theme.tpl doesn't have that area defined. Instead 
of the left/right arrows in layout for moving the block between 
columns, you just have a pulldown list of the block names in which you 
want to move it.

>
> Again, count me in on CSS standardization and I am willing to do any
> grunt work necessary.

Ditto. Alas, I think this should be addressed mostly at the php/design 
level, not perhaps the css/.tpl level. But, usability design is 
something that can be done without any coding skills.

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

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

That's a particularly well observed and informed article Michael.

Some of the issues are being addressed in the new code the team are 
working on. I think we've beaten them on the head enough times in IRC 
about menus at least, and we've had long ranging discussions about CSS 
and how it should be implemented - which I don't entirely agree with. 
Ken noted two links to Xaraya and IMHO they've got the mix right there, 
enforcing some classes without making it overly complex. I just hope 
the 3-tier css method we've chose can largely be ignored at a module 
level and module developers don't try and cram fancy layout in their 
module css. Otherwise we're back to inconsistent look and feel across 
modules.

I hope the team have a good look through the article, and the Xaraya 
ones, and think how they can be addressed.

Personally, I'd like to see more support functions for module 
developers that let them produce menus, submenus, lists, links etc to a 
standard rather than having to build them up manually either in the 
code or in a template. That way there's a set method of doing it that 
can be styled globally. Ie. that we make more use of the box_style type 
of method and expand it to lists, menus, links, tabbed menus with 
appropriate css too... It just appears mad to me that I have to edit 
multiple templates to change the look of menus across a site, if I can 
at all.

So, well done for putting it all together Michael.

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

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

[Ken N. <ke...@co...>]

I would like to jump on the bandwagon.  I believe Mike Noyes brought
this up a few months ago and there was some discussion about CSS
methodology / standards, but no real consensus.

How many times has a module's "theme" clashed with that of the main
theme?  Where colors were hard-coded in the module instead of defaulting
to the theme?

Just recently I perused the Xaraya site to compare and contrast their
efforts with that of phpWebSite.  I found two items which I believe
"should" be incorporated into phpWebSite.

The first is CSS methodology.  Everyone writes code differently...
accomplishing the same results.  Xaraya set up mandatory default CSS
classes:

http://www.xaraya.com/documentation/rfcs/rfc0010.html#rfc.section.2

Establishing standards enables modules to work within the theme instead
of independent of the theme.

Second, here is a "how-to" Xaraya doc for module / theme
interdependence.

http://xaraya.org/index.php/documentation/229

I would also like to add theme "columnization" to the list on Michael's
page.  How many default columns "should" there be?  Can phpWebSite's
Layout module seamlessly handle three / two / one column themes?  What
methodology can be used for those columns?  (left - middle/center -
right) or (left - main - right) or some other variation?

Again, count me in on CSS standardization and I am willing to do any
grunt work necessary.

Ken

On Mon, 2005-01-03 at 15:57, Michael H=C3=B8j Rasmussen wrote:
> Hi all,
>=20
> I have written an article about defining and implementing design standa=
rds
> in phpWebSite. I want to address some of the inconsistency in the inter=
face,
> focusing on usability rather than the actual html code.
>=20
> I believe that a design standard, with examples and guidelines, will be=
nefit
> on the quality of the html code.
> The article is not meant to be the design standard, merely to give some
> inspiration, and most important of all, to give some input for a debate=
 on
> the subject.
>=20
> If you have the time and interests, please look at the article. Feel fr=
ee to
> comment the article directly on the website.
>=20
> Link to the article:
> http://www.michaelshjemmeside.dk/index.php?module=3Dpagemaster&PAGE_use=
r_op=3Dvi
> ew_page&PAGE_id=3D7
>=20
> Please be patient while loading the article. My ISP is V-E-R-Y slow fro=
m
> time to time. It could take up to several minutes before the page is lo=
aded.
>=20
> Another warning - besides the article, the website is in Danish. Please=
 do
> not get lost :-)
>=20
> - Michael Rasmussen (TechElephant)
>=20
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
--=20
Ken Nordquist
"Community Marketing for the Next Generation"
Call Us Toll Free: 866-621-4043
http://communitygems.com

Re: [Phpwebsite-developers] Defining and implementing design standards in phpWebSite

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

Thanks for the write up. I saw this kind of late in the day so I will
read more about it tomorrow.

Also, please take a look at 1.0.0 alpha code if you have a chance. We
are trying to take the road you are pointing us down. It currently uses
a tableless design and relies on CSS more than its predecessor. Stay
with us as we move forward and make sure to come by the chat room.

P.S. I am close to getting 0.x modules working in the new core. Once I
do, I will update the demo.

~ Matt

On Mon, 2005-01-03 at 15:57, Michael H=C3=B8j Rasmussen wrote:
> Hi all,
>=20
> I have written an article about defining and implementing design standa=
rds
> in phpWebSite. I want to address some of the inconsistency in the inter=
face,
> focusing on usability rather than the actual html code.
>=20
> I believe that a design standard, with examples and guidelines, will be=
nefit
> on the quality of the html code.
> The article is not meant to be the design standard, merely to give some
> inspiration, and most important of all, to give some input for a debate=
 on
> the subject.
>=20
> If you have the time and interests, please look at the article. Feel fr=
ee to
> comment the article directly on the website.
>=20
> Link to the article:
> http://www.michaelshjemmeside.dk/index.php?module=3Dpagemaster&PAGE_use=
r_op=3Dvi
> ew_page&PAGE_id=3D7
>=20
> Please be patient while loading the article. My ISP is V-E-R-Y slow fro=
m
> time to time. It could take up to several minutes before the page is lo=
aded.
>=20
> Another warning - besides the article, the website is in Danish. Please=
 do
> not get lost :-)
>=20
> - Michael Rasmussen (TechElephant)
>=20
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
--=20
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] Defining and implementing design standards in phpWebSite

[<po...@mi...>]

Hi all,

I have written an article about defining and implementing design =
standards
in phpWebSite. I want to address some of the inconsistency in the =
interface,
focusing on usability rather than the actual html code.

I believe that a design standard, with examples and guidelines, will =
benefit
on the quality of the html code.
The article is not meant to be the design standard, merely to give some
inspiration, and most important of all, to give some input for a debate =
on
the subject.

If you have the time and interests, please look at the article. Feel =
free to
comment the article directly on the website.

Link to the article:
http://www.michaelshjemmeside.dk/index.php?module=3Dpagemaster&PAGE_user_=
op=3Dvi
ew_page&PAGE_id=3D7

Please be patient while loading the article. My ISP is V-E-R-Y slow from
time to time. It could take up to several minutes before the page is =
loaded.

Another warning - besides the article, the website is in Danish. Please =
do
not get lost :-)

- Michael Rasmussen (TechElephant)

[Phpwebsite-developers] Filtering what the Manager actually lists

[<re...@ki...>]

Hello there!
=20
As it's my first post, I'd like to introduce myself. My name is Ren=E9
Kiesler, I'm student of the technical university in Vienna, Austria. =
I've
been hacking my way through phpwebsite since about march 2004, you can =
find
my main site on http://www.kiesler.at/
=20
About my question. I've hacked the manager core class to be able to work
with a where-clause. While this works almost the way I want it to, there =
are
two drawbacks:
=20
- the first call of $this->getList() gives me everything the way I want =
it.
From the second call on, the calculated fields aren't calculated =
anymore.
For example, I get the raw output of a date instead of the one processed =
by
getDate() or whatever I call my method.
=20
- also, I've figured out that there already is a method, that should =
filter
stuff the way I intended it to. It's called "setSort". But when I use =
it, I
don't get any output.
=20
So. Can you give me some advice on what to do?
=20
Thank you,
=20
Ren=E9!

Re: [Phpwebsite-developers] Question about sendmail...

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

On 27 Dec 2004, at 06:53, Patrick Twohig wrote:

> I don't run PHP in safe mode....But I'll have a look into it.  And 
> yes, both forgotten password and new signup are broken.
>

phpSUexec also causes problems. Mail won't work as that'll stop mail 
going out as 'nobody'.

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

Re: [Phpwebsite-developers] Question about sendmail...

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

Greg Tassone wrote:

>There is a recent bug that may be causing this.  I have posted it (along
>with a patch to fix it) in the project site on Sourceforge earlier this
>week.
>
>Does your PHP server by chance run with Safe Mode enabled?  If so, then
>this bug is causing it - two problems specifically:
>
>1) No users can register with the site
>
>2) The "lost password" functionality will be broken as well.
>
>Please see two of the most recent bug filings at the project Bug
>Tracker:
>https://sourceforge.net/tracker/?group_id=15539&atid=115539
>
># 1089617
># 1086940
>
>Hopefully one of the project devs can submit my patches to the tree
>soon!  The problem has to do with "safe mode" restrictions to the PHP
>mail() function.
>
>Let me know if you have any questions.
>
>Greg T.
>
>
>On Sat, 2004-12-25 at 12:41 +0000, Shaun Murray wrote:
>  
>
>>On 25 Dec 2004, at 01:49, Patrick Twohig wrote:
>>
>>    
>>
>>>I have a client on my webserver who is complaining that users aren't 
>>>able to sign up for access to his phpwebsite forums.  What does 
>>>phpwebsite need to have to play nicely with sendmail.  I'm using exim, 
>>>but there is a command /usr/bin/sendmail there for backwards 
>>>compatibility with exim. (Mailwrapper scripts) when I just type 
>>>sendmail at the prompt I get:
>>>      
>>>
>>I'm using exim also with the same sendmail compatibility so it's not 
>>that. The account signup uses the PHP Mail function or PEAR Mail class. 
>>Check you can signup yourself, Check you've not disabled sending mail 
>>in your php config. Some hosts don't allow sending mail from php.
>>
>>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
>  
>
I don't run PHP in safe mode....But I'll have a look into it.  And yes, 
both forgotten password and new signup are broken.

Thanks.

Re: [Phpwebsite-developers] Question about sendmail...

[Greg T. <gt-...@ta...>]

There is a recent bug that may be causing this.  I have posted it (along
with a patch to fix it) in the project site on Sourceforge earlier this
week.

Does your PHP server by chance run with Safe Mode enabled?  If so, then
this bug is causing it - two problems specifically:

1) No users can register with the site

2) The "lost password" functionality will be broken as well.

Please see two of the most recent bug filings at the project Bug
Tracker:
https://sourceforge.net/tracker/?group_id=15539&atid=115539

# 1089617
# 1086940

Hopefully one of the project devs can submit my patches to the tree
soon!  The problem has to do with "safe mode" restrictions to the PHP
mail() function.

Let me know if you have any questions.

Greg T.


On Sat, 2004-12-25 at 12:41 +0000, Shaun Murray wrote:
> On 25 Dec 2004, at 01:49, Patrick Twohig wrote:
> 
> > I have a client on my webserver who is complaining that users aren't 
> > able to sign up for access to his phpwebsite forums.  What does 
> > phpwebsite need to have to play nicely with sendmail.  I'm using exim, 
> > but there is a command /usr/bin/sendmail there for backwards 
> > compatibility with exim. (Mailwrapper scripts) when I just type 
> > sendmail at the prompt I get:
> 
> I'm using exim also with the same sendmail compatibility so it's not 
> that. The account signup uses the PHP Mail function or PEAR Mail class. 
> Check you can signup yourself, Check you've not disabled sending mail 
> in your php config. Some hosts don't allow sending mail from php.
> 
> 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] Question about sendmail...

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

On 25 Dec 2004, at 01:49, Patrick Twohig wrote:

> I have a client on my webserver who is complaining that users aren't 
> able to sign up for access to his phpwebsite forums.  What does 
> phpwebsite need to have to play nicely with sendmail.  I'm using exim, 
> but there is a command /usr/bin/sendmail there for backwards 
> compatibility with exim. (Mailwrapper scripts) when I just type 
> sendmail at the prompt I get:

I'm using exim also with the same sendmail compatibility so it's not 
that. The account signup uses the PHP Mail function or PEAR Mail class. 
Check you can signup yourself, Check you've not disabled sending mail 
in your php config. Some hosts don't allow sending mail from php.

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

[Phpwebsite-developers] Question about sendmail...

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

I have a client on my webserver who is complaining that users aren't 
able to sign up for access to his phpwebsite forums.  What does 
phpwebsite need to have to play nicely with sendmail.  I'm using exim, 
but there is a command /usr/bin/sendmail there for backwards 
compatibility with exim. (Mailwrapper scripts) when I just type sendmail 
at the prompt I get:

patrick@bender patrick $ sendmail
Exim is a Mail Transfer Agent. It is normally called by Mail User Agents,
not directly from a shell command line. Options and/or arguments control
what it does when called. For a list of options, see the Exim documentation.
patrick@bender patrick $

Is this right, or is there something else I need to set up.

Thanks for the help and Happy Holidays!

Patrick Twohig.

Re: [Phpwebsite-developers] Wordpress in phpwebsite?

[Eloi G. <el...@re...>]

Jonah wrote:

>I am currently using Wordpress (but not against changing to something else
>with better functionality) and would like to use it in phpwebsite.  I was
>wondering if anyone on here has had any success in doing that?
>  
>

Article Manager supports a lot of blog-related features, including 
support for the MetaWeblog and MovableType APIs.   RSS capability is 
offered via the phpwsRSS module.  The only thing I guess you'd be 
missing is Trackback, and Rck has implemented a solution for that at 
http://www.kiesler.at

Re: [Phpwebsite-developers] Wordpress in phpwebsite?

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

On 12 Dec 2004, at 16:41, Jonah wrote:

> I am currently using Wordpress (but not against changing to something 
> else
> with better functionality) and would like to use it in phpwebsite.  I 
> was
> wondering if anyone on here has had any success in doing that?

No, but Matt has a working blog module in the Fallout development for 
phpWebSite v1.0 which would do pretty much the same thing for you. 
You'd maybe miss the Wordpress plugins perhaps.

>
>
> Another (probably blue-sky) idea - is it possible to get the branching
> technology to use the same database?  My thought is to use it as a 
> community
> portals, with different communities broken into 'branches'.
> Just a thought.
>

Robert Kennedy ex of phpwebsitemanual.com is doing something similar 
sharing the user tables and logins between branches. I don't think 
there's any content shared in what he's doing - ie. no shared 
announcements.

You could also use phpwsRSSfeeds to share announcements and a few other 
parts of the sites. Not ideal use of resources possibly but a practical 
work around perhaps for now.

But yes, a shared system where the branch sites feed a central hub site 
with data and vice versa would be very, very, very useful.

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

[Phpwebsite-developers] Wordpress in phpwebsite?

[Jonah <jbr...@cy...>]

I am currently using Wordpress (but not against changing to something =
else
with better functionality) and would like to use it in phpwebsite.  I =
was
wondering if anyone on here has had any success in doing that?


Another (probably blue-sky) idea - is it possible to get the branching
technology to use the same database?  My thought is to use it as a =
community
portals, with different communities broken into 'branches'.
Just a thought.

Any sage advice on these is *TRULY* appreciated.
-Jonah

Re: [Phpwebsite-developers] Rules idea

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

On 3 Dec 2004, at 13:12, Matthew McNaney wrote:

> Sorry to get back so late on this.
>
> I am still rolling this idea around in my head. What Steven and I had
> come up with was a block module that allowed you to put the block where
> ever you want. So they could go inside announcements, pages, etc. as
> well as on the side of a page.
>
> I think this system would fit well as one of the ways to decide where a
> block appears. We can get into it more when I get started on that
> module.
>

It's more like it's an extra piece in deciding 'why' something is 
displayed, not just 'where' so I think it'd match up even if you can 
display blocks inside pages - which would be damned useful btw. The 
idea is to be wider than just a block module so that anything with a 
content variable is able to be told 'why' it should display.

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

Re: [Phpwebsite-developers] Rules idea

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

Sorry to get back so late on this.

I am still rolling this idea around in my head. What Steven and I had
come up with was a block module that allowed you to put the block where
ever you want. So they could go inside announcements, pages, etc. as
well as on the side of a page.

I think this system would fit well as one of the ways to decide where a
block appears. We can get into it more when I get started on that
module.

Matt

On Wed, 2004-12-01 at 23:16, 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
-- 
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] CVS Restuctured

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

All changes appear to be working well on my end.

Wendall

On Thu, 2004-12-02 at 14:56 -0500, Steven Levin 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!
>