phpwebsite-developers — For our development team.

[Phpwebsite-developers] Item/Manager README Suggestions

[Don S. <do...@se...>]

I was a little lost when it came to the naming conventions needed in the        
template file, and how they had to match what was in the list columns.          
Perhaps if you could give an example list.tpl and row.tpl and note that         
the column headings in list.tpl need to match the values in the                 
listcolumns array in conf/manager.php, that would be better. 

Don.

Re: [Phpwebsite-developers] Item/Manager troubles

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

Don,

  Yes the doc is wrong.  You do not need to add the WHERE the manager will
handle adding that for you.  I will update that in the documentation. 
Thanks for posting about it.

Steven

> In my conf/manager.php I have this line:
>
> $lists = array("messages"=>"WHERE pid=0");
>
> which is right, according to the ITEM_MANAGER_README.txt example:
>
> /* The name of your lists and their corresponding database constraints */
> $lists = array("mylist"=>"WHERE approved='1' AND saved='1'");
>
> However when I run my getLists function this is printed to the browser
> window:
>
> SQL: SELECT id FROM mod_phpwsbb_messages WHERE (WHERE pid=0)
> syntax error
>
> So I'm thinking the doc might be incorrect?  Of course when have just
> "pid=0" I don't get any items returned, despite them having pid of 0.
>
> Don.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...

[Phpwebsite-developers] Item/Manager troubles

[Don S. <do...@se...>]

In my conf/manager.php I have this line:

$lists = array("messages"=>"WHERE pid=0");

which is right, according to the ITEM_MANAGER_README.txt example:

/* The name of your lists and their corresponding database constraints */
$lists = array("mylist"=>"WHERE approved='1' AND saved='1'");

However when I run my getLists function this is printed to the browser 
window:

SQL: SELECT id FROM mod_phpwsbb_messages WHERE (WHERE pid=0)
syntax error

So I'm thinking the doc might be incorrect?  Of course when have just 
"pid=0" I don't get any items returned, despite them having pid of 0.

Don.

Re: [Phpwebsite-developers] Load Object

[Richard S. <ri...@ri...>]

Thank's 'ol wise one.


On Wednesday, May 21, 2003, at 04:58  AM, Matthew McNaney wrote:

>> I'm trying to have my class load into phpWebsite no matter what page
>> the user on and if they are logged in or not. Below is the
>> configuration I have for in blast.php. Please help :-)
>
>
> Add this and you should be golden.
>
> $allow_view = "all";
>
> Don't forget to take a look at the new controlpanel file in the conf
> directories of CVS.
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Appalachian State University
> Phone: 828-262-6493
> phpwebsite.appstate.edu
> ess.appstate.edu
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ObjectStore.
> If flattening out C++ or Java code to make your application fit in a
> relational database is painful, don't do it! Check out ObjectStore.
> Now part of Progress Software. http://www.objectstore.net/sourceforge
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

[Phpwebsite-developers] Refactor of Pagemaster Search

[Roland, R. M <rmr...@in...>]

I was looking at the search module, (specifically with regard to the =
Pagemaster module) and I noticed that the search performed in Pagemaster =
loops through all pages and sections (with a query PER section).  That =
means if you have N sections in your entire site, that the search =
performs exactly N+1 individual queries to the database. =20

I'm working on a possible replacement for the current pagemaster search =
function, and the only stumbling block is that I get sections, but can't =
easily determine their parent pages from them.  I'm sure this difficulty =
is why the current scheme was used, but I'm trying to get to where there =
are AT MOST N+2 queries issued to the DB (and that's only if every =
single section has a match to the search criteria).

Currently I'm looking at trying to use the 'section_order' field in the =
pages table to determine if a given section is in a page, so I ask if =
anyone can tell me now if that is a dead end or not.=20

Any recommendations would be appreciated.


Thanks,


Ryan Roland

Application Developer
Information Technology Department
Division of Recreational Sports
Indiana University

rmr...@in...

Re: [Phpwebsite-developers] Load Object

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

> I'm trying to have my class load into phpWebsite no matter what page
> the user on and if they are logged in or not. Below is the
> configuration I have for in blast.php. Please help :-)


Add this and you should be golden.

$allow_view = "all";

Don't forget to take a look at the new controlpanel file in the conf
directories of CVS.

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu

[Phpwebsite-developers] Load Object

[Richard S. <ri...@ri...>]

Hey All,

I'm trying to have my class load into phpWebsite no matter what page=20
the user on and if they are logged in or not. Below is the=20
configuration I have for in blast.php. Please help :-)

<?

$mod_title =3D "dev_utils";
$mod_pname =3D "Dev Utils";
$mod_directory =3D "dev_utils";
$mod_filename =3D "index.php";
$priority =3D 2;
$user_mod =3D 1;
$admin_mod =3D 1;
$mod_class_files =3D array("dev_utils.php");
$mod_sessions =3D array("OBJ_utils");
$init_object =3D array("OBJ_utils"=3D>"dev_utils");
$active =3D "on";
$version =3D 0.1;
$branch_allow =3D 1;
$uninstall_file =3D "uninstall.php";
$uninstall_allow =3D 1;

?>=00=00=

[Phpwebsite-developers] patch

[Andy H. <ah...@ht...>]

-----BEGIN PGP SIGNED MESSAGE-----

With the latest version from cvs, I actually got a complaint about the number
of params from chmod.  Here's a patch.  It also includes a change for bash,
since it does not use valid bourne shell syntax (not noticeable in Linux which
has sh linked directly to bash).

> cvs diff setup/secure_phpws.sh 
Index: setup/secure_phpws.sh
===================================================================
RCS file: /home/cvsroot/phpwebsite/setup/secure_phpws.sh,v
retrieving revision 1.10
diff -r1.10 secure_phpws.sh
1c1
< #!/bin/sh
- ---
> #!/bin/bash
39,40c39,40
<     chmod 775 `find ../ -type d`
<     chmod 664 `find ../ -type f`
- ---
>     find ../ -type d | xargs chmod 775
>     find ../ -type f | xargs chmod 664
63,64c63,64
<     chmod 775 `find ../ -type d`
<     chmod 664 `find ../ -type f`
- ---
>     find ../ -type d | xargs chmod 775
>     find ../ -type f | xargs chmod 664


~~ 
Andy Harrison
ah##@httpsite.com
ICQ: 123472  AIM/Y!: AHinMaine
[full headers for details]

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8

iQCVAwUBPsmuAVPEkLgodAWVAQExJgP/dOMbPLEEau7fl5mkpz6Yp301aRVcTE/J
1IeJfZoSdKdZKE2AQOt48FDgHwslVkRs8lGonfGm8pgn2j7a/+zSjfzUhaZPCeo/
YXsGvgTjiIRcLOpFJltHUglxqv2sZGN2K6HUja9VJVLOA1ILOw5l56YVyIIx/ORn
3mEBDy82JyM=
=ief3
-----END PGP SIGNATURE-----

Re: [Phpwebsite-developers] Central group authorization table (Option 2)

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

> I think this is a good idea but I wouldn't alter the current FatCat code.
> I am currently rewriting it for 0.9.3.

Arrgh!  That's what I get for thinking about stuff on the weekends.  I'm
done already.  I haven't given it a serious workout, but it seems to be
working fine.  Tell you what -- so it's not completely wasted, I'll just
give you a .zip of the changed files in case you want to use some of the
ideas later on.  In any case I also coded a few optimizations (mostly
because the module was tagging the database too often) and commented in
descriptions of what various functions do as personal reminders.  I put
comments near each of the changes.

> So FatCat is going to need to be 'aware' of what it is categorizing and
> modules need to be 'aware' of what category they are in. Currently, it's
> just not in the code.

Well, I know that modules can know what categories they're in by using
PHPWS_Fatcat_Elements::getModulesCategories(), but I'm not sure what you
mean by FatCat being aware of what it's categorizing.  Can you give me an
example of what you'd like it to do?

BTW, in my never-ending quest to reduce the server load I also changed a
function in my users/groups.php.  Before it was executing 1 query per group.
Now it does everything in one query using listAllGroups().  SourceForge is
down right now, but I'll submit the bug report when it comes back.

-Eloi George-

Re: [Phpwebsite-developers] Central group authorization table (Option 2)

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

> What if we implemented the group-based restrictions by category instead?
> That way the user has one choice to make -- "what category(ies) does the
> announcement belong to? " That way, they don't -have- to know that
> announcements in "Financial Reports" can only be seen by users that are
> members of the Accounting, Oversight, and Investors groups.  The
> application
> immediately becomes more idiot-proof!

I think this is a good idea but I wouldn't alter the current FatCat code.
I am currently rewriting it for 0.9.3.

The problem is we have to look at the way we currently are using FatCat.
When we wrote many of these modules, FatCat wasn't considered a 'core'
module. Therefore, FatCat works independently from all modules. Module's
have no idea what category they are in and FatCat doesn't really know the
significance of the information it receives from the module.

So FatCat is going to need to be 'aware' of what it is categorizing and
modules need to be 'aware' of what category they are in. Currently, it's
just not in the code.

So I agree with your idea but I would hold off trying to alter the current
code. Stay tuned though and jump in the chat room so you can offer input
when we start restructuring it.

Thanks,
Matt

-------------------

Matthew McNaney
Internet Systems Architect
Electronic Student Services
Appalachian State University
Phone: 828-262-6493
phpwebsite.appstate.edu
ess.appstate.edu

[Phpwebsite-developers] Central group authorization table (Option 2)

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

OK, 2 days later I came up with an idea that's better from both a user
interface and module development point of view.

Using Announce as an example, the old grouping concept would've forced the
user to make 2 extra desicions when creating an announcement - what category
to assign and what groups should be able to view the announcement.  That
would mean extra listboxes on the page and more complexity in terms of
useability.

What if we implemented the group-based restrictions by category instead?
That way the user has one choice to make -- "what category(ies) does the
announcement belong to? " That way, they don't -have- to know that
announcements in "Financial Reports" can only be seen by users that are
members of the Accounting, Oversight, and Investors groups.  The application
immediately becomes more idiot-proof!

I d/l'ed a CVS tarball yesterday and I'm in the process of modifying the
FatCat code to see if this'll work.  Essentially I'm thinking that Group
Ownership would be managed in categoryForm().  Then all category-based
accesses would be filtered based on group membership.  If modules need to
generate their own lists of stuff, they can use much the same method as
Idea#1.  The table would just be managed via FatCat.

But don't wait 'til I'm finished, let me know what you think of this plan.

-Eloi-

Re: [Phpwebsite-developers] PostgreSQL

[Don S. <do...@se...>]

Some people have tried.  If you want to try and report any and all bugs to 
the bug tracker on our sourceforge page that would be great.  Otherwise it 
will have to wait until I get a chance to test it out which I don't have 
much time right now.

Don.

On Fri, 16 May 2003, Richard Sumilang wrote:

> Has anyone tested PHPWS with PostgreSQL?... Just curious....
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> 

[Phpwebsite-developers] PostgreSQL

[Richard S. <ri...@ri...>]

Has anyone tested PHPWS with PostgreSQL?... Just curious....

[Phpwebsite-developers] Central group authorization table

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

Hey all!

While working on TalkBox (I finally named it!) I again ran into a conceptual
problem of how to implement group-based display authorizations.  The
string-based approach causes a severe memory problem when you have to load
10,000 rows of  _id and _groups and then start unset()ing the unauthorized
ones.

As a test, I reconfigured ArticleManager to utilize a lookup table-based
system.  It worked a lot better in terms of memory outlay.  However, there
was still a problem in how other modules like FatCat and TalkBox would be
able to access the group restrictions for all other modules in 1 sql
statement.

The solution I came up with is a central table with 3 columns:

# --------------------------------------------------------
# TABLE DESCRIPTION:
# A summary table listing all groups that are authorized to
# access a specific module's item.
# If all groups can access/view a particular item then
# no entry will exist in this table for that item_id
# & module_title.
#
# NORMAL USAGE:
# group_id is compared against a string containing
# comma-delimited group ids.
#
# EXAMPLE SQL:
# 'WHERE item_id='.$item.' AND module_title='.$module
# .'AND group_id IN ('
# .implode(',', array_keys($_SESSION['OBJ_user']->groups))
# .')'
#
CREATE TABLE mod_authgroups (
    group_id int unsigned NOT NULL default '0',
    module_title varchar(20) NOT NULL default '',
    item_id int unsigned NOT NULL default '0',
    key (item_id),
    key (group_id)
  );

This way, if any module needs to access the group requirements of any other
module, they'll automatically know where to look and they won't have to
generate a separate sql query for each module scanned.  copies of Group
strings won't have to get stored in fatcat or approval or whatever else
comes down the road.

Approval? Criticism? Any thoughts?

-Eloi George-

Re: [Phpwebsite-developers] Security Suggestion

[Jeremy A. <ja...@tu...>]

One point i would like to add. Even a restricted user can cause problems.
With what is proposed, the account would still have delete options.  Any
malicious user can just have it cycle through and delete all the content. 
True it is harder but you get a false seance of security even with a
restricted sql user. Bots can batch attack and you are still out of luck. 
The code should be the main line of security not the sql user.  This
doesn't mean you should not separate different sites to restricted users. 
Each not allowed to see/use each other.

> I think there should be a configuration option to set up 3 SQL users.
> One user that has the ability to create and drop databases, one user
> who has the ability to read/insert/update/delete rows from tables, and
> another user who has the ability to create/drop tables. The reason for
> this is what is malicious user where to type into a form field SQL code
> to drop a table? Even better yet, drop a database! That wouldn't be
> very fun... So my suggestion is when using the core's sqlInsert
> function for example should use the user account that can
> read/insert/and only update tables. When installing a mod and usually
> using sqlImport function should call upon the user who can only create
> and drop databases. Of course since some people on their hosting
> providers can only have one SQL user on databases like MySQL that has
> full control over their database which means the system should
> automatically check if the other users exist and if not, use the the
> default user account provided. Many companies practice this as a
> security rule of thumb and I think this CMS should do so also.
>
> Let me know you feed back :-)
>
> Best Regards,
>
> Richard Sumilang
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


--
Jeremy Agee
phpWebSite Development Team (http://phpwebsite.appstate.edu)
Appalachian State University
SF.net id: jagee or 94756

Re: [Phpwebsite-developers] Security Suggestion

[<ad...@tu...>]

A big issue with creating multiple database users to access different
database functions is the fact that a lot of our users host with hosting
companies that only allow them one database/user/pass.  The core's
PHPWS_TExt::parseInput function could be updated to check for submitted
sql queries and remove them without too much fuss and it's already in
place on most input fields.  This would allow ALL users to take advantage
of this added security.  Just my 2 cents.

Adam

> I think it would be more efficient for people who have access to create
> more than one SQL user to stop the process from the SQL server rather
> than taking up any more resources with php. It will be more work to
> create another function to make sure you don't feature that code in
> your queries however it's a good idea for people who just have one
> possible SQL user.
>
> Regards,
>
> Richard Sumilang.
>
> On Tuesday, May 13, 2003, at 05:17  AM, Don Seiler wrote:
>
>> I don't think this is really necessary.  If phpWebSite is somehow
>> tricked
>> into entering SQL code that is entered into a form, then that is the
>> real
>> problem and we need to capture that and exit the save function and
>> give a
>> stern error to the user.
>>
>> Don.
>>
>> On Mon, 12 May 2003, Richard Sumilang wrote:
>>
>>> I think there should be a configuration option to set up 3 SQL users.
>>> One user that has the ability to create and drop databases, one user
>>> who has the ability to read/insert/update/delete rows from tables, and
>>> another user who has the ability to create/drop tables. The reason for
>>> this is what is malicious user where to type into a form field SQL
>>> code
>>> to drop a table? Even better yet, drop a database! That wouldn't be
>>> very fun... So my suggestion is when using the core's sqlInsert
>>> function for example should use the user account that can
>>> read/insert/and only update tables. When installing a mod and usually
>>> using sqlImport function should call upon the user who can only create
>>> and drop databases. Of course since some people on their hosting
>>> providers can only have one SQL user on databases like MySQL that has
>>> full control over their database which means the system should
>>> automatically check if the other users exist and if not, use the the
>>> default user account provided. Many companies practice this as a
>>> security rule of thumb and I think this CMS should do so also.
>>>
>>> Let me know you feed back :-)
>>>
>>> Best Regards,
>>>
>>> Richard Sumilang
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>>> The only event dedicated to issues related to Linux enterprise
>>> solutions
>>> www.enterpriselinuxforum.com
>>>
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>>
>>>
>>
>>
>> -------------------------------------------------------
>> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>> The only event dedicated to issues related to Linux enterprise
>> solutions
>> www.enterpriselinuxforum.com
>>
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


-- 
Adam Morton
Developer - Electronic Student Services
http://phpwebsite.appstate.edu
Founder - Appalachian Linux Users Group
http://alug.appstate.edu

Re: [Phpwebsite-developers] Security Suggestion

[Richard S. <ri...@ri...>]

I think it would be more efficient for people who have access to create 
more than one SQL user to stop the process from the SQL server rather 
than taking up any more resources with php. It will be more work to 
create another function to make sure you don't feature that code in 
your queries however it's a good idea for people who just have one 
possible SQL user.

Regards,

Richard Sumilang.

On Tuesday, May 13, 2003, at 05:17  AM, Don Seiler wrote:

> I don't think this is really necessary.  If phpWebSite is somehow 
> tricked
> into entering SQL code that is entered into a form, then that is the 
> real
> problem and we need to capture that and exit the save function and 
> give a
> stern error to the user.
>
> Don.
>
> On Mon, 12 May 2003, Richard Sumilang wrote:
>
>> I think there should be a configuration option to set up 3 SQL users.
>> One user that has the ability to create and drop databases, one user
>> who has the ability to read/insert/update/delete rows from tables, and
>> another user who has the ability to create/drop tables. The reason for
>> this is what is malicious user where to type into a form field SQL 
>> code
>> to drop a table? Even better yet, drop a database! That wouldn't be
>> very fun... So my suggestion is when using the core's sqlInsert
>> function for example should use the user account that can
>> read/insert/and only update tables. When installing a mod and usually
>> using sqlImport function should call upon the user who can only create
>> and drop databases. Of course since some people on their hosting
>> providers can only have one SQL user on databases like MySQL that has
>> full control over their database which means the system should
>> automatically check if the other users exist and if not, use the the
>> default user account provided. Many companies practice this as a
>> security rule of thumb and I think this CMS should do so also.
>>
>> Let me know you feed back :-)
>>
>> Best Regards,
>>
>> Richard Sumilang
>>
>>
>>
>> -------------------------------------------------------
>> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
>> The only event dedicated to issues related to Linux enterprise 
>> solutions
>> www.enterpriselinuxforum.com
>>
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise 
> solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] Security Suggestion

[Don S. <do...@se...>]

I don't think this is really necessary.  If phpWebSite is somehow tricked 
into entering SQL code that is entered into a form, then that is the real 
problem and we need to capture that and exit the save function and give a 
stern error to the user.

Don.

On Mon, 12 May 2003, Richard Sumilang wrote:

> I think there should be a configuration option to set up 3 SQL users. 
> One user that has the ability to create and drop databases, one user 
> who has the ability to read/insert/update/delete rows from tables, and 
> another user who has the ability to create/drop tables. The reason for 
> this is what is malicious user where to type into a form field SQL code 
> to drop a table? Even better yet, drop a database! That wouldn't be 
> very fun... So my suggestion is when using the core's sqlInsert 
> function for example should use the user account that can 
> read/insert/and only update tables. When installing a mod and usually 
> using sqlImport function should call upon the user who can only create 
> and drop databases. Of course since some people on their hosting 
> providers can only have one SQL user on databases like MySQL that has 
> full control over their database which means the system should 
> automatically check if the other users exist and if not, use the the 
> default user account provided. Many companies practice this as a 
> security rule of thumb and I think this CMS should do so also.
> 
> Let me know you feed back :-)
> 
> Best Regards,
> 
> Richard Sumilang
> 
> 
> 
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
> 
> 
> 

[Phpwebsite-developers] Security Suggestion

[Richard S. <ri...@ri...>]

I think there should be a configuration option to set up 3 SQL users. 
One user that has the ability to create and drop databases, one user 
who has the ability to read/insert/update/delete rows from tables, and 
another user who has the ability to create/drop tables. The reason for 
this is what is malicious user where to type into a form field SQL code 
to drop a table? Even better yet, drop a database! That wouldn't be 
very fun... So my suggestion is when using the core's sqlInsert 
function for example should use the user account that can 
read/insert/and only update tables. When installing a mod and usually 
using sqlImport function should call upon the user who can only create 
and drop databases. Of course since some people on their hosting 
providers can only have one SQL user on databases like MySQL that has 
full control over their database which means the system should 
automatically check if the other users exist and if not, use the the 
default user account provided. Many companies practice this as a 
security rule of thumb and I think this CMS should do so also.

Let me know you feed back :-)

Best Regards,

Richard Sumilang

[Phpwebsite-developers] PHPWS 0.9.1 Memory Readings

[Don S. <do...@se...>]

I took some updated readings.  My methods may have differed from those 
used before but here are my results, listing the module, the total memory 
read by xdebug and my hand-calculated totals.  I might have fat-fingered 
in xcalc so forgive me if my diffs are off.

I included my two modules at the bottom as well.  Look like phpwslistings 
might give calendar a run for it's money.  Numbers are in bytes, so divide 
by one million to get megabytes.

module              total       difference
------------------  ----------  ----------
core                5520712     5520712
poll                5967160     446448
faq                 6645568     678408
announcements       6909952     264384
notes               7020704     110752
file manager        7120488     99784
phpws debugger      7123312     2824
form generator      8114288     990976
link manager        8311248     196960
module maker        8312392     1114
menu manager        8985320     672928
textpad             8986088     768
calendar            10634912    1648824
branch creator      10819304    184392
comment manager     11152944    333640
photo album         11416688    263744
pagemaster          11417792    1104
blockmaker          11579280    161488
teamsite            12394000    814720
phpwslistings       13740432    1346432

Re: [Phpwebsite-developers] Form Class

[Richard S. <ri...@ri...>]

Where can I get a copy of your most recent updated version? Thanks btw!

On Monday, May 5, 2003, at 12:58  PM, Steven Levin wrote:

> Richard,
>
>   I just recently updated the photoalbum module to use ezform if you 
> want
> to check that out.
>
> Steven
>
>> Hmmmm... I looked at it for a while and read the comments briefly but
>> could not figure out how to completely use it like the original form
>> class which was very strait forward and to the point. Are  there any
>> mods already using EZForm to create their forms so I can take a look
>> under the skirt to see what's going on and how it works or maybe a
>> documentation? I am using phpWS 9.1...
>>
>> Regards,
>> Richard S.
>>
>>
>> On Monday, May 5, 2003, at 04:40  AM, Matthew McNaney wrote:
>>
>>>> The form class has a lot of great stuff for generating a form real
>>>> quick however I feel it is very limited.
>>>
>>> We are trying to phase out the current core class to the more 
>>> flexible
>>> EZform class. Please take a look and let us know if there are options
>>> you
>>> would like to see in it.
>>>
>>> Matthew McNaney
>>> Internet Systems Architect
>>> Electronic Student Services
>>> Appalachian State University
>>> Phone: 828-262-6493
>>> phpwebsite.appstate.edu
>>> ess.appstate.edu
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by:ThinkGeek
>>> Welcome to geek heaven.
>>> http://thinkgeek.com/sf
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>
>
> -- 
> Steven Levin
> Electronic Student Services
> Appalachian State University
> Phone: 828.262.2431
> PhpWebsite Development Team
> URL: http://phpwebsite.appstate.edu
> Email: st...@NO...
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] Form Class

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

Richard,

  I just recently updated the photoalbum module to use ezform if you want
to check that out.

Steven

> Hmmmm... I looked at it for a while and read the comments briefly but
> could not figure out how to completely use it like the original form
> class which was very strait forward and to the point. Are  there any
> mods already using EZForm to create their forms so I can take a look
> under the skirt to see what's going on and how it works or maybe a
> documentation? I am using phpWS 9.1...
>
> Regards,
> Richard S.
>
>
> On Monday, May 5, 2003, at 04:40  AM, Matthew McNaney wrote:
>
>>> The form class has a lot of great stuff for generating a form real
>>> quick however I feel it is very limited.
>>
>> We are trying to phase out the current core class to the more flexible
>> EZform class. Please take a look and let us know if there are options
>> you
>> would like to see in it.
>>
>> Matthew McNaney
>> Internet Systems Architect
>> Electronic Student Services
>> Appalachian State University
>> Phone: 828-262-6493
>> phpwebsite.appstate.edu
>> ess.appstate.edu
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


-- 
Steven Levin
Electronic Student Services
Appalachian State University
Phone: 828.262.2431
PhpWebsite Development Team
URL: http://phpwebsite.appstate.edu
Email: st...@NO...

Re: [Phpwebsite-developers] Form Class

[Richard S. <ri...@ri...>]

Hmmmm... I looked at it for a while and read the comments briefly but 
could not figure out how to completely use it like the original form 
class which was very strait forward and to the point. Are  there any 
mods already using EZForm to create their forms so I can take a look 
under the skirt to see what's going on and how it works or maybe a 
documentation? I am using phpWS 9.1...

Regards,
Richard S.


On Monday, May 5, 2003, at 04:40  AM, Matthew McNaney wrote:

>> The form class has a lot of great stuff for generating a form real
>> quick however I feel it is very limited.
>
> We are trying to phase out the current core class to the more flexible
> EZform class. Please take a look and let us know if there are options 
> you
> would like to see in it.
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Appalachian State University
> Phone: 828-262-6493
> phpwebsite.appstate.edu
> ess.appstate.edu
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] Poor IE

[Jeremy A. <ja...@tu...>]

Blast, had a typo. Missing word from previous post second paragraph.

After all if you can NOT publish spec/problems with technology your free
speech is already gone.


> Ok, normally i would not hit the list with common place M$ b**ching but
> this was too hard to pass up.
>
>> Holly shit! That is just sooo rude!
>>
>> But anyways, how does Microsoft plan to rule the world if they keep
>> crashing?
>
> This question is easy.  You first force everyone to buy your product at
> $400USD (home price) a copy. You then use that money to pay off(Oops i
> always get that wrong "lobby") lawmakers for DRM and other ways to
> monopolize the tech market.(Already convicted of this, monopoly any way.)
> After a "secure" place is setup and the trustworthy M$ has the only key
> you then take it when M$ wants to give it.
>
> Any way! Good thing its not illegal to mention the DMCA.  But it could be.
>  After all if you can publish spec/problems with technology your free
> speech is already gone.
>
> OK, OK all rants aside for the W2K, XP people out there, see if you have
> installed Q811493 patch.  It brought my win box down to a crawl,  no
> gaming(command & conqour - generals) for me until i removed the "Security
> Fix" or do nothing loop.
>
> http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS03-013.asp
>
>>
>>
>> On Saturday, May 3, 2003, at 08:37  AM, Steven Levin wrote:
>>
>>> Hello all,
>>>
>>>   Check out this article running on /.  Seems as though you can wreck
>>> shop
>>> for IE with just a little HTML.  I was able to view it just fine in
>>> Phoenix :)
>>>
>>> http://slashdot.org/articles/03/05/02/
>>> 1845241.shtml?tid=126&tid=95&tid=128&tid=113
>>>
>>>
>>> --
>>> Steven Levin
>>> Electronic Student Services
>>> Appalachian State University
>>> Phone: 828.262.2431
>>> PhpWebsite Development Team
>>> URL: http://phpwebsite.appstate.edu
>>> Email: st...@NO...
>>>
>>>
>>> -------------------------------------------------------
>>> This sf.net email is sponsored by:ThinkGeek
>>> Welcome to geek heaven.
>>> http://thinkgeek.com/sf
>>> _______________________________________________
>>> Phpwebsite-developers mailing list
>>> Php...@li...
>>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>
>
> --
> Jeremy Agee
> phpWebSite Development Team (http://phpwebsite.appstate.edu)
> Appalachian State University
> SF.net id: jagee or 94756
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


--
Jeremy Agee
phpWebSite Development Team (http://phpwebsite.appstate.edu)
Appalachian State University
SF.net id: jagee or 94756

Re: [Phpwebsite-developers] Poor IE

[Jeremy A. <ja...@tu...>]

Ok, normally i would not hit the list with common place M$ b**ching but
this was too hard to pass up.

> Holly shit! That is just sooo rude!
>
> But anyways, how does Microsoft plan to rule the world if they keep
> crashing?

This question is easy.  You first force everyone to buy your product at
$400USD (home price) a copy. You then use that money to pay off(Oops i
always get that wrong "lobby") lawmakers for DRM and other ways to
monopolize the tech market.(Already convicted of this, monopoly any way.) 
After a "secure" place is setup and the trustworthy M$ has the only key
you then take it when M$ wants to give it.

Any way! Good thing its not illegal to mention the DMCA.  But it could be.
 After all if you can publish spec/problems with technology your free
speech is already gone.

OK, OK all rants aside for the W2K, XP people out there, see if you have
installed Q811493 patch.  It brought my win box down to a crawl,  no
gaming(command & conqour - generals) for me until i removed the "Security
Fix" or do nothing loop.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS03-013.asp

>
>
> On Saturday, May 3, 2003, at 08:37  AM, Steven Levin wrote:
>
>> Hello all,
>>
>>   Check out this article running on /.  Seems as though you can wreck
>> shop
>> for IE with just a little HTML.  I was able to view it just fine in
>> Phoenix :)
>>
>> http://slashdot.org/articles/03/05/02/
>> 1845241.shtml?tid=126&tid=95&tid=128&tid=113
>>
>>
>> --
>> Steven Levin
>> Electronic Student Services
>> Appalachian State University
>> Phone: 828.262.2431
>> PhpWebsite Development Team
>> URL: http://phpwebsite.appstate.edu
>> Email: st...@NO...
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by:ThinkGeek
>> Welcome to geek heaven.
>> http://thinkgeek.com/sf
>> _______________________________________________
>> Phpwebsite-developers mailing list
>> Php...@li...
>> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>>
>>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>


--
Jeremy Agee
phpWebSite Development Team (http://phpwebsite.appstate.edu)
Appalachian State University
SF.net id: jagee or 94756