phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Auto Increment SQL problem

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

On Mon, 2003-08-25 at 13:13, Richard Sumilang wrote:
> Great, I look forward to it. What about the auto incrementing? Are you 
> going to remove all the auto increment commands after the id column 
> type in the setup SQL files?
> 
> - Richard S.

Yes we will take out all the index designations from the CREATE TABLE
query.


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] Auto Increment SQL problem

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

> PS, lets not forget to indexes on a separate command. I don't know if 
> there is a sql standard for creating indexes during creation of tables 
> so I can possible be wrong. Tried google but no luck...
> 
> - Richard S.

I will help facilitate this by building it into the export function in
the new DB class for 0.9.4.

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] Auto Increment SQL problem

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

Great! Works for me

+1 for removing database specific auto increment columns and having=20
columns that are integer's and primary keys as the auto increment=20
column.

PS, lets not forget to indexes on a separate command. I don't know if=20
there is a sql standard for creating indexes during creation of tables=20=

so I can possible be wrong. Tried google but no luck...

- Richard S.



On Wednesday, August 20, 2003, at 02:03  PM, Eloi George wrote:

> CREATE  TABLE  test (
>   id int NOT NULL PRIMARY KEY
> );
>
> This -should- work for all db's.  The PEAR routines that phpWS appear=20=

> to
> search for the primary index and will automatically set up a _seq=20
> table if
> you enable autoincrementing in the core->sqlInsert() parameters.
>
> Eloi George
>
>
> ----- Original Message -----
> From: "Richard Sumilang" <ri...@ri...>
> To: <php...@li...>
> Sent: Wednesday, August 20, 2003 1:37 PM
> Subject: [Phpwebsite-developers] Auto Increment SQL problem
>
>
> As I looked for what is the common standard for creating auto =
increment
> columns in a table I found that there isn't one. I know the built in
> sequencing PWS has in play for auto increment has some play in this =
but
> not completely sure how it works when setting up a table?
>
> What do you guys  think will be the best way to create tables with an
> AUTO INCREMENT column with PWS? I currently don't care for too much
> support for Oracle right now as you can see with the example below.
>
>
>
>
> Syntax for MySQL
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> CREATE  TABLE  test (
>   id INT NOT  NULL AUTO_INCREMENT,
>   PRIMARY  KEY ( id)
> );
>
>
> Syntax for PostgreSQL
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> CREATE TABLE test (
>   id SERIAL ,
>   PRIMARY KEY (id)
> );
>
>
> Syntax for Oracle9i
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
> --
> --Create sequence called demo
> --
> CREATE SEQUENCE "DEMO"."SEQ_INSERT" INCREMENT BY 1 START WITH
> 1780229 MAXVALUE 1.0E28 MINVALUE 1 NOCYCLE
> CACHE 20 ORDER
>
> --
> -- Next place a trigger for that column you want to auto increment --
> --
> CREATE OR REPLACE TRIGGER "DEMO"."TRG_EMP_INSERT" BEFORE
> INSERT ON "DEMO"."EMP"
> FOR EACH ROW BEGIN
>
>   SELECT seq_insert .nextval -- get the new seq number
>
>   INTO :NEW.emp_no -- :NEW missed
>   FROM DUAL;
> END;
>
> # Found source for Oracle at
> http://www.experts-exchange.com/Databases/Q_20412293.html
>
>
>
> Best Regards,
> - Richard S
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Dice.com.
> Did you know that Dice has over 25,000 tech jobs available today? From
> careers in IT to Engineering to Tech Sales, Dice has tech jobs from =
the
> best hiring companies. http://www.dice.com/index.epl?rel_code=104
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a single =
machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines
> at the same time. Free trial click=20
> here:http://www.vmware.com/wl/offer/358/0
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] Auto Increment SQL problem

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

CREATE  TABLE  test (
  id int NOT NULL PRIMARY KEY
);

This -should- work for all db's.  The PEAR routines that phpWS appear to
search for the primary index and will automatically set up a _seq table i=
f
you enable autoincrementing in the core->sqlInsert() parameters.

Eloi George


----- Original Message -----
From: "Richard Sumilang" <ri...@ri...>
To: <php...@li...>
Sent: Wednesday, August 20, 2003 1:37 PM
Subject: [Phpwebsite-developers] Auto Increment SQL problem


As I looked for what is the common standard for creating auto increment
columns in a table I found that there isn't one. I know the built in
sequencing PWS has in play for auto increment has some play in this but
not completely sure how it works when setting up a table?

What do you guys  think will be the best way to create tables with an
AUTO INCREMENT column with PWS? I currently don't care for too much
support for Oracle right now as you can see with the example below.




Syntax for MySQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
CREATE  TABLE  test (
  id INT NOT  NULL AUTO_INCREMENT,
  PRIMARY  KEY ( id)
);


Syntax for PostgreSQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
CREATE TABLE test (
  id SERIAL ,
  PRIMARY KEY (id)
);


Syntax for Oracle9i
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
--
--Create sequence called demo
--
CREATE SEQUENCE "DEMO"."SEQ_INSERT" INCREMENT BY 1 START WITH
1780229 MAXVALUE 1.0E28 MINVALUE 1 NOCYCLE
CACHE 20 ORDER

--
-- Next place a trigger for that column you want to auto increment --
--
CREATE OR REPLACE TRIGGER "DEMO"."TRG_EMP_INSERT" BEFORE
INSERT ON "DEMO"."EMP"
FOR EACH ROW BEGIN

  SELECT seq_insert .nextval -- get the new seq number

  INTO :NEW.emp_no -- :NEW missed
  FROM DUAL;
END;

# Found source for Oracle at
http://www.experts-exchange.com/Databases/Q_20412293.html



Best Regards,
- Richard S


-------------------------------------------------------
This SF.net email is sponsored by Dice.com.
Did you know that Dice has over 25,000 tech jobs available today? From
careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
best hiring companies. http://www.dice.com/index.epl?rel_code=104
_______________________________________________
Phpwebsite-developers mailing list
Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

Re: [Phpwebsite-developers] Auto Increment SQL problem

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

On Wed, 2003-08-20 at 13:37, Richard Sumilang wrote:
> As I looked for what is the common standard for creating auto increment 
> columns in a table I found that there isn't one...

> Syntax for MySQL
> ===========================
> CREATE  TABLE  test (
>   id INT NOT  NULL AUTO_INCREMENT,
>   PRIMARY  KEY ( id)
> );

> 
> Syntax for PostgreSQL
> ===========================
> CREATE TABLE test (
>   id SERIAL ,
>   PRIMARY KEY (id)
> );

These should be easy to identify with the current process: look for an
integer that is the primary key.

> 
> Syntax for Oracle9i
> ===========================
> --
> --Create sequence called demo
> --
> CREATE SEQUENCE "DEMO"."SEQ_INSERT" INCREMENT BY 1 START WITH
> 1780229 MAXVALUE 1.0E28 MINVALUE 1 NOCYCLE
> CACHE 20 ORDER
> 
> --
> -- Next place a trigger for that column you want to auto increment --
> --
> CREATE OR REPLACE TRIGGER "DEMO"."TRG_EMP_INSERT" BEFORE
> INSERT ON "DEMO"."EMP"
>     FOR EACH ROW BEGIN
> 
>     SELECT seq_insert .nextval  -- get the new seq number
> 
>       INTO :NEW.emp_no -- :NEW missed
>       FROM DUAL;
> END;
> 
> # Found source for Oracle at 
> http://www.experts-exchange.com/Databases/Q_20412293.html

I wouldn't even know where to begin. What are the parameters of the
column to be auto incremented in Oracle? Is it labeled as the primary
key?

There are some other possible solutions if getting the column from
Oracle is too difficult:

1) If you are using an auto incremented column, it must be called "id".
Could work although I think a few might be annoyed by this.

2) A table could track the incremented columns (  TABLE_NAME | ID_COLUMN
). It would get loaded when the database is first accessed.
The cons here are that you would have to indicate what that column is on
install. And it would be another table accessed when the page is created
unless we session it.

3) Everytime the database object is called, the developer would specify
a column requiring auto_incrementing.
Another minor pain. You would just have to remember to enter it
everytime.

These are just a few suggestions, which you are welcome to add to. AFAIK
Pear does NOT have a function to figure out an incremented column, you
have to tell it each time insert is called (which make sense).

One quick note, one of the above versions MAY be better than the current
implementation. Currently, the insert function has to figure out the
index on its own. Getting told the column right off the bat would save a
little time, although inserts are certainly less common than say select.


-- 
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] Auto Increment SQL problem

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

I agree identifying the auto incrementing column for MySQL and Postgres 
is easy.

The way Postgres and Oracle create auto incrementing columns are not 
different, they both use sequencing but Postgres has a wrapper for 
creating the sequence which is by setting the column to a SERIAL 
column. When you do that Postgres automatically creates all the code 
you see for creating an auto increment column on Oracle and sets the 
column to primary key if it is not.

I think it is fair to assume when creating a table and you have a 
column that is a integer and setting it to primary key that it should 
be auto incremented, and yes Oracle has a primary key field and used 
when auto incrementing.

So at any rate, I think looking for the primary key is the best idea 
however column types might now be the next issue. Postgres supports 
doing stuff like "create table test(col1 varchar(5) not null);" and 
"create table test(col1 varchar[5] not null);" but it acts a little 
different for integers (I don't know why). If you would like to specify 
a column size for an integer you have to use square brackets, eg: 
"create table test1(col1 int[5] not null);" and it wont accept "()" so 
that is just some extra parsing...

- Regards
Richard Sumilang



On Thursday, August 21, 2003, at 05:55  AM, Matthew McNaney wrote:

> On Wed, 2003-08-20 at 13:37, Richard Sumilang wrote:
>> As I looked for what is the common standard for creating auto 
>> increment
>> columns in a table I found that there isn't one...
>
>> Syntax for MySQL
>> ===========================
>> CREATE  TABLE  test (
>>   id INT NOT  NULL AUTO_INCREMENT,
>>   PRIMARY  KEY ( id)
>> );
>
>>
>> Syntax for PostgreSQL
>> ===========================
>> CREATE TABLE test (
>>   id SERIAL ,
>>   PRIMARY KEY (id)
>> );
>
> These should be easy to identify with the current process: look for an
> integer that is the primary key.
>
>>
>> Syntax for Oracle9i
>> ===========================
>> --
>> --Create sequence called demo
>> --
>> CREATE SEQUENCE "DEMO"."SEQ_INSERT" INCREMENT BY 1 START WITH
>> 1780229 MAXVALUE 1.0E28 MINVALUE 1 NOCYCLE
>> CACHE 20 ORDER
>>
>> --
>> -- Next place a trigger for that column you want to auto increment --
>> --
>> CREATE OR REPLACE TRIGGER "DEMO"."TRG_EMP_INSERT" BEFORE
>> INSERT ON "DEMO"."EMP"
>>     FOR EACH ROW BEGIN
>>
>>     SELECT seq_insert .nextval  -- get the new seq number
>>
>>       INTO :NEW.emp_no -- :NEW missed
>>       FROM DUAL;
>> END;
>>
>> # Found source for Oracle at
>> http://www.experts-exchange.com/Databases/Q_20412293.html
>
> I wouldn't even know where to begin. What are the parameters of the
> column to be auto incremented in Oracle? Is it labeled as the primary
> key?
>
> There are some other possible solutions if getting the column from
> Oracle is too difficult:
>
> 1) If you are using an auto incremented column, it must be called "id".
> Could work although I think a few might be annoyed by this.
>
> 2) A table could track the incremented columns (  TABLE_NAME | 
> ID_COLUMN
> ). It would get loaded when the database is first accessed.
> The cons here are that you would have to indicate what that column is 
> on
> install. And it would be another table accessed when the page is 
> created
> unless we session it.
>
> 3) Everytime the database object is called, the developer would specify
> a column requiring auto_incrementing.
> Another minor pain. You would just have to remember to enter it
> everytime.
>
> These are just a few suggestions, which you are welcome to add to. 
> AFAIK
> Pear does NOT have a function to figure out an incremented column, you
> have to tell it each time insert is called (which make sense).
>
> One quick note, one of the above versions MAY be better than the 
> current
> implementation. Currently, the insert function has to figure out the
> index on its own. Getting told the column right off the bat would save 
> a
> little time, although inserts are certainly less common than say 
> select.
>
>
> -- 
> 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] Auto Increment SQL problem

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

As I looked for what is the common standard for creating auto increment=20=

columns in a table I found that there isn't one. I know the built in=20
sequencing PWS has in play for auto increment has some play in this but=20=

not completely sure how it works when setting up a table?

What do you guys  think will be the best way to create tables with an=20
AUTO INCREMENT column with PWS? I currently don't care for too much=20
support for Oracle right now as you can see with the example below.




Syntax for MySQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
CREATE  TABLE  test (
  id INT NOT  NULL AUTO_INCREMENT,
  PRIMARY  KEY ( id)
);


Syntax for PostgreSQL
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
CREATE TABLE test (
  id SERIAL ,
  PRIMARY KEY (id)
);


Syntax for Oracle9i
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
--
--Create sequence called demo
--
CREATE SEQUENCE "DEMO"."SEQ_INSERT" INCREMENT BY 1 START WITH
1780229 MAXVALUE 1.0E28 MINVALUE 1 NOCYCLE
CACHE 20 ORDER

--
-- Next place a trigger for that column you want to auto increment --
--
CREATE OR REPLACE TRIGGER "DEMO"."TRG_EMP_INSERT" BEFORE
INSERT ON "DEMO"."EMP"
=A0 =A0 FOR EACH ROW BEGIN

  =A0 SELECT seq_insert .nextval =A0-- get the new seq number

  =A0 =A0 INTO :NEW.emp_no -- :NEW missed
  =A0 =A0 FROM DUAL;
END;

# Found source for Oracle at=20
http://www.experts-exchange.com/Databases/Q_20412293.html



Best Regards,
- Richard S=

Re: [Phpwebsite-developers] postgresql errors

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

Yes, a one liner after creating the table should be compliant... CREATE 
INDEX indexname ON tablename (column, ...);

Let me know when this is done and i'll give the installation another 
shot.

- Richard S.


On Tuesday, August 19, 2003, at 10:53  AM, Matthew McNaney wrote:

> On Tue, 2003-08-19 at 04:03, Richard Sumilang wrote:
>> With postgre, index's are not created within the "create table" syntax
>> and since it's not the SQL standard then it probably wont work with
>> Oracle and other databases (I think). With using a primary key you
>> don't need to index since primary keys are always indexed and I think
>> mod_title and id are never exactly the same correct?
>
> Primary keys are unique and not needed for cache. It needs to index the
> mod_title and id because those are the columns searched under.
>
> So then, if we need an index, I am guessing we will need to leave its
> creation out of the table creation and instead make a CREATE INDEX 
> line.
> Is that Postgres compatible and will it work cross platform?
>
>
>> I would like to have pws working on postgre since I am porting most of
>> my applications to it so if you guys want me to do any tests of 
>> setting
>> up pws and using some of the mods let me know.
>
> What we mainly need are posts like this. We need to know which formats
> are MySQL specific. I would like 0.9.4 to be truly compliant.
>
>
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Appalachian State University
> Phone: 828-262-6493
> http://phpwebsite.appstate.edu
> http://ess.appstate.edu
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Dice.com.
> Did you know that Dice has over 25,000 tech jobs available today? From
> careers in IT to Engineering to Tech Sales, Dice has tech jobs from the
> best hiring companies. http://www.dice.com/index.epl?rel_code=104
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>
>

Re: [Phpwebsite-developers] postgresql errors

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

Yes, a one liner after creating the table should be compliant... CREATE 
INDEX indexname ON tablename (column, ...);

Let me know when this is done and i'll give the installation another 
shot.

- Richard S.


On Tuesday, August 19, 2003, at 10:53  AM, Matthew McNaney wrote:

> On Tue, 2003-08-19 at 04:03, Richard Sumilang wrote:
>> With postgre, index's are not created within the "create table" syntax
>> and since it's not the SQL standard then it probably wont work with
>> Oracle and other databases (I think). With using a primary key you
>> don't need to index since primary keys are always indexed and I think
>> mod_title and id are never exactly the same correct?
>
> Primary keys are unique and not needed for cache. It needs to index the
> mod_title and id because those are the columns searched under.
>
> So then, if we need an index, I am guessing we will need to leave its
> creation out of the table creation and instead make a CREATE INDEX 
> line.
> Is that Postgres compatible and will it work cross platform?
>
>
>> I would like to have pws working on postgre since I am porting most of
>> my applications to it so if you guys want me to do any tests of 
>> setting
>> up pws and using some of the mods let me know.
>
> What we mainly need are posts like this. We need to know which formats
> are MySQL specific. I would like 0.9.4 to be truly compliant.
>
>
> 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] Help Module Images

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

The help module images still use absolute paths rather than relative. 
Is it still a fix needed with some theme variables or is that the help 
module writing them?

Re: [Phpwebsite-developers] postgresql errors

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

On Tue, 2003-08-19 at 04:03, Richard Sumilang wrote:
> With postgre, index's are not created within the "create table" syntax  
> and since it's not the SQL standard then it probably wont work with  
> Oracle and other databases (I think). With using a primary key you  
> don't need to index since primary keys are always indexed and I think  
> mod_title and id are never exactly the same correct?

Primary keys are unique and not needed for cache. It needs to index the
mod_title and id because those are the columns searched under.

So then, if we need an index, I am guessing we will need to leave its
creation out of the table creation and instead make a CREATE INDEX line.
Is that Postgres compatible and will it work cross platform?


> I would like to have pws working on postgre since I am porting most of  
> my applications to it so if you guys want me to do any tests of setting  
> up pws and using some of the mods let me know.

What we mainly need are posts like this. We need to know which formats
are MySQL specific. I would like 0.9.4 to be truly compliant.


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] postgresql errors

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

I tried setting up a copy of phpwebsite with a postgre db and I got the  
following error trying to setup the core only.

Bad....
------------------------------------------------------------------------ 
-------------

DB Error: syntax error
CREATE TABLE cache ( mod_title varchar(30) NOT NULL default '', id  
varchar(32) NOT NULL default '', data text NOT NULL, ttl int NOT NULL  
default '0', index (mod_title, id) ) [nativecode=ERROR: parser: parse  
error at or near "(" at character 166 ]




Good...
------------------------------------------------------------------------ 
-------------
CREATE TABLE cache ( mod_title varchar(30) NOT NULL default '', id  
varchar(32) NOT NULL default '', data text NOT NULL, ttl int NOT NULL  
default '0', primary key (mod_title, id) )



With postgre, index's are not created within the "create table" syntax  
and since it's not the SQL standard then it probably wont work with  
Oracle and other databases (I think). With using a primary key you  
don't need to index since primary keys are always indexed and I think  
mod_title and id are never exactly the same correct?

I would like to have pws working on postgre since I am porting most of  
my applications to it so if you guys want me to do any tests of setting  
up pws and using some of the mods let me know.

- Richard S.

[Phpwebsite-developers] postgresql errors

[Richard S. <rsu...@ex...>]

I tried setting up a copy of phpwebsite with a postgre db and I got the  
following error trying to setup the core only.

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

phpWebSite Version 0.9.3 - Installation Utility

DB Error: syntax error
CREATE TABLE cache ( mod_title varchar(30) NOT NULL default '', id  
varchar(32) NOT NULL default '', data text NOT NULL, ttl int NOT NULL  
default '0', index (mod_title, id) ) [nativecode=ERROR: parser: parse  
error at or near "(" at character 166 ]

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

I would like to have pws working on postgre since I am porting most of  
my applications to it so if you guys want me to do any tests of setting  
up pws and using some of the mods let me know.

- Richard S.

Re: [Phpwebsite-developers] Where are we?

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

Sorry folks, wrong address :)


-- 
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] phpwsContacts 0.2.2

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

phpwsContacts is a module for the phpWebSite CMS 0.9.2-1 or higher. It
provides extended user contact information and vCard exporting.
Suggested uses are for corporate addressbooks or alumni websites.

Version 0.2.2 fixes a bug (thanks to Craig Musgraves) wherein I was an
idiot and didn't set the default sort order on the "browse" window, so
the contact list was being sorted by ID, which really isn't useful. List
is now sorted by last name, then first name, then middle name. Should
satisfy most people.

http://phpwscontacts.sourceforge.net

[Phpwebsite-developers] Where are we?

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

Greetings everyone,

A special welcome to the new members of the list. You have been added to
this special mailing list because you are running, or going to run,
phpWebSite.

I would like everyone within the sound of this email to open the
included attachment. It is a table of all the web sites we currently and
will eventually manage. It will let you know where you stand in full
implementation of your site.

Here is what you should look for:
Current Version : lists what version of phpwebsite you are running. If
it says 0.8.x, you need to get upgraded to 0.9.x. See below for how to
get upgraded.

Theme : lists the version of your theme. If you are running 0.8.x and
your theme says 0.9.x that means a theme has been created for your
eventual upgrade.

Contact : the name of the person to contact about the site. If you feel
you should not be the contact, please let me know.

Contact Email : how we can reach you

Training Date : this is the column we need to fill up. Before you can
get your new site or get your old site converted, you will need
training.

Live : Is your site on-line with phpWebSite?

Ready to Convert : is it safe to convert your 0.8.x data to 0.9.x?

Special Notes : special concerns about your site we need to address.


If your site requires conversion, you will need to set up a training
date and time with me. During training you will work on a staging area.
When you are comfortable with your abilities, we will convert your old
site to your new. If you have not used phpWebSite before, we will switch
your old with your new once you have transferred over all your data.

Your training may have to be over the course of a few days. Your first
training session will cover the basics. The faster you catch on, the
more we will go over. Each session will last an hour or less. We will
schedule each training session separately.

Please contact me to set up training and discuss your needs.

Remember: your web site's progress is up to you. The more you attend to
it, the more students and others will get out of it.

Best regards,
Matt McNaney

-- 
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] HTML Template?

[Geoff S. <ge...@ho...>]

In the 8.3 version, the web page creator had an option to create an HTML page =
as opposed to a regular page.

I think that the main thing that the HTML page option did was cause carriage =
return /line feeds to be ignored so that you could use <p> and <br> to control =
paragraphing. I don't know what other features it had.

But, the pagemaster templates I've been playing with seem to recognize carriage =
return / line feeds so that I cannot control paragraphing by using the <p> and =
<br> tags. I cannot figure out how to get pagemaster to ignore carriage return =
/ line feeds so that <p> and <br> tags will control the paragraphing.

Does this feature exist?=20

If not, any ideas about what would be involved in creating this feature and =
adding it to pagemaster?

Geoff

[Phpwebsite-developers] Security Vulnerabilities

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

Hello all phpWebSite users,

  Some security issues were brought to our attention earlier today.  In
order to protect yourself please replace your index.php with the one
found here.

http://res1.stddev.appstate.edu/horde/chora/co.php/phpwebsite/index.php?login=2&r=1.66&p=1&Horde=3430edc1fe94de721ac3c0f4c838a799

-- 
Steven Levin
Electronic Student Services
Appalachian State University
URL: http://phpwebsite.appstate.edu
Email: steven at tux dot appstate dot edu

[Phpwebsite-developers] [Phpwebsite-developers]

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

Hello all phpWebSite users,

  Some security issues were brought to our attention earlier today.  In
order to protect yourself please replace your index.php file in the
phpwebsite base with the one attached to this message.

-- 
Steven Levin
Electronic Student Services
Appalachian State University
URL: http://phpwebsite.appstate.edu
Email: steven at tux dot appstate dot edu

[Phpwebsite-developers] Security Update

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

Greetings,

Please take a moment to update your installations of phpWebSite 0.9.x
with a patch from our home page. All you need to do is replace your
index.php file.

This fix will be included in a full patch release coming soon.


-- 
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] LeagueSite 0.1.1 Released

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

LeagueSite is a PHPWebSite (>= 0.9.3) module that adds roster, stats,
and schedule information for a sports league or team onto the PHPWS
base. It can be used to create a website for their fans to learn more
about the league and its teams and players.

LeagueSite 0.1.1 fixes 3 pretty decent bugs. The most obvious is that I
had my permission names different in what the code was checking for vs
what they actually were.

Anyway it is suggested that all 0.1.0 users upgrade to 0.1.1 to avoid
having to rip their hair out in frustration and sending nasty things in
the mail to me.

http://leaguesite.sourceforge.net

[Phpwebsite-developers] Add: PHPWS_Array: ERROR! Function maxKey() did not recieve an array!

[cpteos <cp...@ne...>]

 > second error messages relates from time to time to diefferent lines:

Fatal error: Maximum execution time of 30 seconds exceeded in ... 
/lib/pear/DB/mysql.php on line 203

cp...@ne... wrote:

> I get above error-message when trying to move blocks. It won't wok in 
> most cases.
>
> having installed all phpws-modules + additinonal "articles"; phpws 
> 9.3; (commenting out of memory_size has no effect);
>
> who/what can help?
>
> THX
>
> EO
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers

[Phpwebsite-developers] PHPWS_Array: ERROR! Function maxKey() did not recieve an array!

[cpteos <cp...@ne...>]

I get above error-message when trying to move blocks. It won't wok in 
most cases.

having installed all phpws-modules + additinonal "articles"; phpws 9.3; 
(commenting out of memory_size has no effect);

who/what can help?

THX

EO

[Phpwebsite-developers] phpwsProv 0.1.0 beta

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

phpwsProv is a work-request and provisioning module for phpWebSite. It
provides basic abilities to accept work-requests, assign the requests
and track provisioning of the work order.

Happy birthday to me (July 28). As a treat I'm giving the class phpwsProv 0.1.0
beta. Some minor fixes from the alpha and added comment support. Please
download and try it out.

phpwsProv requires phpWebSite 0.9.3, see INSTALL.txt included in the
docs directory for details.

http://phpwsprov.sourceforge.net

[Phpwebsite-developers] Fast Help needed: ShowinMain 0.9.3

[cpteos <cp...@ne...>]

Hi,

viewing all comments on phpwebsite and forums it seems all ggot 
showinmain runnin' but me.

Downloading the actual tarbal, unpacking it, results in a module without 
lan/tmpl files. So boosting it will result in instaling the module but 
cannot see or get it run.

Does anyone have a working version/download link for actual ShowinMain 
for phpws 093.

THX

EO