phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Module Substitution

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

I disagree with part of your analysis.

For the module to become part of the distro, the in-house developer needs 
take over the module. If the original developer wants to help, that is 
great. But, if the outside developer disappears or gets hit by a truck, the 
maintenance would revert to the in-house developer.

Also, if the module becomes part of the distribution, then the in-house 
developer is de facto responsible for it even if the original developer is 
still involved. The in-house developer takes on responsibility to insure 
that the module:

1. Continues to reflect architecture and coding standards.
2. Maintains consistent user interface.
3. Enhancements meet the approval of the in-house team.

Seems to me there ought to be three levels of module:

1. Those developed in-house or "taken over" as part of the distro.
2. Those that meet  a certification standard and are considered "official" 
modules developed by a third-party.
3. Those that work with phpWebsite but which have not been reviewed and 
approved.

Geoff
www.hostricity.com


At 01:46 PM 12/28/2002 -0500, Matthew McNaney wrote:
>This is not in direct response to Eloi's new module (good job btw) but
>just a question that needs consideration for the future.
>
>Suppose someone creates a better content module than one produced
>in-house. I know that many of the developers here have several things
>going on at one time (I can think of two huge ones off the top of my
>head). Perhaps, if an outside developer is willing, we could ask if they
>would like their module to become part of our distro.
>
>Here is the rub though.
>- We would all need to agree it should be done.
>- The in house developer would need to agree
>- The outside developer would have to guarantee support.
>
>Again, this may not come up, but I know that there are some modules we are
>working on that might have a more dedicated developer outside the
>unversity.
>
>Please discuss with pros and cons for both sides.
>
>Matt
>--
>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

[Phpwebsite-developers] Module Substitution

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

This is not in direct response to Eloi's new module (good job btw) but
just a question that needs consideration for the future.

Suppose someone creates a better content module than one produced
in-house. I know that many of the developers here have several things
going on at one time (I can think of two huge ones off the top of my
head). Perhaps, if an outside developer is willing, we could ask if they
would like their module to become part of our distro.

Here is the rub though.
- We would all need to agree it should be done.
- The in house developer would need to agree
- The outside developer would have to guarantee support.

Again, this may not come up, but I know that there are some modules we are
working on that might have a more dedicated developer outside the
unversity.

Please discuss with pros and cons for both sides.

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

Re: [Phpwebsite-developers] PHP 4.3 and PEAR

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

> There will come a point when the appropriate answer to "my host won't
> upgrade" is "find a new host". But, until that time, we need to do a
> little  hand-holding.

Agreed Geoff. We have no intention of changing the install to > 4.3. We
will continue supporting 4.2.2 and above and making sure the Pear support
easy and clear to use.

With 4.3 however, the light at the end of the tunnel draws closer :)

Best regards,
Matt

[Phpwebsite-developers] PHP 4.3 and PEAR

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

I saw the "my provider won't upgrade to PHP 4.3" complaint.

Apologies to all for stating the obvious!

As a web host, I can tell you that we won't upgrade to PHP 4.3 for awhile. 
In a production environment, it is considered prudent to wait for the bugs 
to be shaken out before upgrading.

Within a few weeks or months, we will upgrade based on the field experience 
of others.

Here's what needs to happen:

phpWebSite needs to be tested on 4.3 with native Pear AND on PHP 
4.2.whatever with the locally installed PEAR library for some indefinite 
period of time. That way, everyone currently using phpWebSite who wants to 
migrate to 0.9.0 will be able to do so.

At some point in 2003 we should be able to abandon testing on PHP 4.2 with 
local PEAR.

HOWEVER, there may still be an issue with web hosts that have upgraded to 
PHP 4.3, but have not installed the native PEAR libraries. Normally, this 
would not happen unless there are problems with the native PEAR libraries. 
So, we won't know for a while whether phpWebSite will have to be tested 
with PHP 4.3 and locally installed PEAR.

Eventually, the problem will resolve itself. In the mean time, we need to 
make sure that phpWebSite doesn't leave loyal users behind because of a 
temporary bump in the road.

There will come a point when the appropriate answer to "my host won't 
upgrade" is "find a new host". But, until that time, we need to do a little 
hand-holding.

We are currently on PHP 4.2.2 so I we will be testing phpWebSite 0.9.rc3 in 
this environment with the PEAR library locally installed.

Geoff
www.Hostricity.com

Re: [Phpwebsite-developers] php 4.3.0 and pear 1.0

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

Kick ass. Unfortunately you know the upcoming bitch...

"My provider won't update php to 4.3 because blah blah!"

Anyway, at least it means pear problems will hopefully start phasing out.

Thanks Don,
Matt

> I'm sure most of you know this, but today php 4.3.0 was release, which
> includes pear 1.0.  So pear is now awakened from it's long beta
> gestation.
>
> huzzah!
>
> Don.
>
>
> -------------------------------------------------------
> 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

[Phpwebsite-developers] php 4.3.0 and pear 1.0

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

I'm sure most of you know this, but today php 4.3.0 was release, which 
includes pear 1.0.  So pear is now awakened from it's long beta gestation.

huzzah!

Don.

[Phpwebsite-developers] New Module (ArticleManager) - Need Feedback

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

Hey all!

I have a new 0.90 module that I'm putting the finishing touches on =
before I post it up on SourceForge.  I need you guys to give it a quick =
run through so I can figure out what bugs I've missed. =20

I have it currently set up on www.realvidreams.com/testbed  - there's a =
page on the site that gives an overview of the module's features.

I'm not leaving the site wide open, so you'll only see the functions =
available to:

1) an admin who can add, edit or delete their own articles & =
upload/include images in articles, (username / password: admin / =
tester),  or

2) a registered user who add, edit or delete their own articles but =
requires approval before publication.  No image functionality is =
allowed.  (username / password: tester / tester)

I just updated it to rc3, so there may be site-related snafus that noone =
knows about yet.  In any case, please let me know! =20

Eloi George

[Phpwebsite-developers] Possible Search bug.

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

Just put rc3 up & I ran across this error message when I tried to search.

Fatal error: Cannot instantiate non-existent class: phpws_articlemanager in
/www/r/realvidreams/htdocs/testbed/mod/search/class/Search.php on line 81

I'm going to try tracking the exact cause down tomorrow, but has anyone else
run across this yet?

Eloi George

Re: [Phpwebsite-developers] Sigh...

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

Servers roasting on an open fire ...

Don. (too lazy to come up with the rest of the Christmas song)

On Sun, 22 Dec 2002, spiggy wrote:

> On Sun, 2002-12-22 at 17:23, Matthew McNaney wrote:
> 
> > I appreciate your words. Therefore I will postpone barbequing the CVS
> > server in retaliation of my feelings getting hurt :)
> 
> and chicken legs are better suited for barbequing anyway ;)
> 
> paivi
> 
> 
> 
> -------------------------------------------------------
> 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] latest cvs/ rc3

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

I'll check it when I get back to Boone. I can't get line numbers on CVS :P
There should be error checks before the foreach command.

Matt

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

> hello all,
>
> i have tried to install rc3 numerous times and different ways but i get
> this regardless of how i do it. install looks like everything is fine,
> but when i click the link 'go to my installation' i get this:
>
> Warning: Invalid argument supplied for foreach() in
> /home/httpd/fallout/core/Core.php on line 262
>
> Warning: Cannot send session cache limiter - headers already sent
> (output started at /home/httpd/fallout/core/Core.php:262) in
> /home/httpd/fallout/index.php on line 41
> Fatal Error: phpWebSite made its database connection but failed to load
> any modules.
> Please check your installation.
>
> the database gets populated, the admin user created etc. everything
> looks right.
>
> i have had fallout running locally a while back and it installed like a
> dream. currently i am running redhat8 with php4.3RC1 and mysql4.0.5beta.
> phpwebsite 0.8.3 works fine. and i have pear installed. the only thing i
> can think of is upgrading php but thats about it.
>
> anyway, i am out of ideas. anyone?
> paivi
>
>
>
> -------------------------------------------------------
> 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

[Phpwebsite-developers] latest cvs/ rc3

[spiggy <th...@me...>]

hello all,

i have tried to install rc3 numerous times and different ways but i get
this regardless of how i do it. install looks like everything is fine,
but when i click the link 'go to my installation' i get this:

Warning: Invalid argument supplied for foreach() in
/home/httpd/fallout/core/Core.php on line 262

Warning: Cannot send session cache limiter - headers already sent
(output started at /home/httpd/fallout/core/Core.php:262) in
/home/httpd/fallout/index.php on line 41
Fatal Error: phpWebSite made its database connection but failed to load
any modules.
Please check your installation.

the database gets populated, the admin user created etc. everything
looks right. 

i have had fallout running locally a while back and it installed like a
dream. currently i am running redhat8 with php4.3RC1 and mysql4.0.5beta.
phpwebsite 0.8.3 works fine. and i have pear installed. the only thing i
can think of is upgrading php but thats about it.

anyway, i am out of ideas. anyone?
paivi

Re: [Phpwebsite-developers] Sigh...

[Philip M. <lis...@li...>]

On Sun, 2002-12-22 at 19:21, Matthew McNaney wrote:
> >From phpwebsite homepage:
> 
> that's not a demo.
> That's an unzipped tarball :)

[snip]

If some people don't see the value of beta releases and release
candidates that's their loss.

It's a shame in software development that for every 1 point of
constructive criticism received you'll get about 10 throwaway comments
disparaging any hard work you put in :-(

I hope I speak for the majority of the users & developers outside of
Appstate when I say that I think you guys are doing a great job.

I know you're not looking for praise, but it doesn't hurt to get some
every now & again, and it is Christmas after all ;-)

Thanks for all the hard work you've all done (and I mean core
developers, modders & themers) over the last year. phpWebSite has
certainly made my life a hell of a lot easier :o)

Rest assured that I'll be trying out RC3 when I get back in the New Year
and I'll be offering some *constructive* comments while wearing my
Interface Designer hat :-)

Merry Christmas and a Happy New Year to all :-)

Phil
-- 
Philip McAllister < uk . co . liquidsand @ phil >
  "All I ask is the chance to prove that money can't make me happy"
  - Spike Milligan
Milligan

Re: [Phpwebsite-developers] Sigh...

[spiggy <th...@me...>]

On Sun, 2002-12-22 at 17:23, Matthew McNaney wrote:

> I appreciate your words. Therefore I will postpone barbequing the CVS
> server in retaliation of my feelings getting hurt :)

and chicken legs are better suited for barbequing anyway ;)

paivi

Re: [Phpwebsite-developers] Sigh...

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

Geoff and Don,

Thanks guys. I wasn't fishing for compliments, I just needed to vent
because I didn't want to publically post disparaging remarks.

I appreciate your words. Therefore I will postpone barbequing the CVS
server in retaliation of my feelings getting hurt :)

Have a good holiday!

Matt

Re: [Phpwebsite-developers] Sigh...

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

Matt:

Please let me throw in my 2 cents:

As far as I can tell, phpWebSite is the ONLY Open Source content management 
system that is actually being built to a software engineering standard. I 
researched every CMS project I could find before I settled on phpWebSite. 
We probably host more  phpWebSite sites than any other hosting company. 
I've banked our company on phpWebsite. I made the decision to go with 
phpWebSite when you released the first version. I haven't seen anything 
that would make me want to go to another CMS. And, I've seen lots to 
increase my loyalty to phpWebSite.

Just look at the code in phpNuke and phpPostNuke. Remember the horrible 
code that was in phpWebSite when it was first broken off from phpNuke?

Your team has consistently improved phpWebSite. You have diligently worked 
the plan. As someone who has been developing software since 1973, I can 
tell you that despite whatever delays and deficits exist in the phpWebSite 
development effort, the phpWebSite team is doing far better than corporate 
America does on at least 80%, maybe 90% of their development projects.

So, are you guys perfect? Of course not! Have I been completely happy with 
everything that has happened. Of course not! Are you doing better than most 
developers in our industry? Absolutely!

And, most importantly, you have been true to your original commitment to 
create a system built to a real design and real standards.

You have much to be proud of with phpWebSite. So, just remember that some 
people will never be happy, no matter what you do.

Geoff
Geoff Staples
www.Hostricity.com


At 02:21 PM 12/22/2002 -0500, you wrote:
> >From phpwebsite homepage:
>
>that's not a demo.
>That's an unzipped tarball :)
>
>I am very disapointed with the new release. It' nowhere near a release
>candidate.
>Sorry, I am switching back to phpcms.
>
>just my 2 cents
>----------------------------------------------------------
>
>Things like this really fry my bacon. I am so tired of people hurling
>barbs at the software without offering anything constructive.
>
>Sorry I shouldn't vent here but we worked really hard before we left
>Friday to get this release out.
>
>Why do we bother?
>
>Matt
>
>
>
>
>-------------------------------------------------------
>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] Sigh...

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

Perhaps that person should have downloaded and installed for himself 
before judging anything.  Install is insanely easy for those of even 
modest skills.

If you want to have a cyber-rumble I've got your back.  It'll be like the 
Jets vs the Sharks in West Side Story.  Only more dancing.

Don.

On Sun, 22 Dec 2002, Matthew McNaney wrote:

> >From phpwebsite homepage:
> 
> that's not a demo.
> That's an unzipped tarball :)
> 
> I am very disapointed with the new release. It' nowhere near a release
> candidate.
> Sorry, I am switching back to phpcms.
> 
> just my 2 cents
> ----------------------------------------------------------
> 
> Things like this really fry my bacon. I am so tired of people hurling
> barbs at the software without offering anything constructive.
> 
> Sorry I shouldn't vent here but we worked really hard before we left
> Friday to get this release out.
> 
> Why do we bother?
> 
> Matt
> 
> 
> 
> 
> -------------------------------------------------------
> 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
> 
> 
> 

[Phpwebsite-developers] Sigh...

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

From phpwebsite homepage:

that's not a demo.
That's an unzipped tarball :)

I am very disapointed with the new release. It' nowhere near a release
candidate.
Sorry, I am switching back to phpcms.

just my 2 cents
----------------------------------------------------------

Things like this really fry my bacon. I am so tired of people hurling
barbs at the software without offering anything constructive.

Sorry I shouldn't vent here but we worked really hard before we left
Friday to get this release out.

Why do we bother?

Matt

[Phpwebsite-developers] RC3 is out

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

RC3 is on the home site.

Matt

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

Re: [Phpwebsite-developers] RC3 Today

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

I forgot to mention,

I believe Jeremy is going to try to keep the demo up to pace with the
release. You should be able to test there as well.

Cheers,
Matt

[Phpwebsite-developers] RC3 Today

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

Good morning,

We will attempt to release RC3 today. Unlike previous attempts however, we
are going to be a little more careful.

We will try to get one out this morning and then we will start testing it.
I will list a place for developers to download it. If you would like to
help, you can download a copy and start hammering on it. If and when you
find a bug, post it HERE and we will check it to see if we can quickly
repair it. We will release a final RC version when we are satisfied. Only
then will we post it to phpWebSite.

We will need information on conversions, installation, pear problems,
using repair, using modules, confusing instructions, etc.

If you have time to help, thanks. Please let us know if you plan on
helping. We would like to get a handle on the number of people testing it.
If not, we suggest you wait until you see the post on the phpWebSite home
page.

Thanks a bunch,
Matt


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

[Phpwebsite-developers] Cache changes

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

Some suggestions were implemented in cache (baby).

setCache and getCache are now just set and get respectively.

TTL is set in seconds now and not minutes.

There is a cache.php file in the conf directory in case you want to turn
off the cache.

Matt


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

[Phpwebsite-developers] Cache Class

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

Greetings,

There is a new class in the core called PHPWS_Cache.

Adam and Steven had been discussing it as a replacement to the
(apparently) rampant use of sessions. So, after discussing the specs, I
wrote it this morning.

http://res1.stddev.appstate.edu/horde/chora/co.php/phpws_core/core/Cache.php?r=1.2

You will not use $core to call it. Instead you will use PHPWS_Cache::

There are two functions to call: setCache and getCache.

Read the CVS function documentation for usage.

The short of it is you set a cache value with setCache by sending your
data and an identifying id. You retrieve this data by calling getCache and
sending your id. Each cache value lasts for one minute defaultly, but you
can set it to whatever you wish.

I would suggest that we go ahead and start eliminating all unnecessary
SESSIONS that we are using for speed. For example, Calendar has been
retooled to use it, and I suggest changing Layout as well. Layout uses a
session to store templates, we could just use the cache instead.

Take a look and let me know what you think.
BTW if you have updated from RC2 to the CVS version, you should be able to
update the features by updating the core in Boost.

Later
Matt


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

Re: [Phpwebsite-developers] Floating menus and new functions

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

+1 here!  sorry so late on that vote...finally got my new debian machine
up and working....i think :)

Adam

> Hello All,
>
>    I was implementing the floating css menu within the menuman module
> (BTW
> if you would like to see
> http://res1.stddev.appstate.edu/phpwebsite/steven/phpws_core/ ).  Well
> after doing this I though of two functions for layout that would
> provide module writers with the ability to put tags and javascript in
> the head of the html document.  We could possibly call them addStyle and
> addJavaScript.  Layout could then add this stuff when it goes to
> process.  Does anyone else think these functions would be usefull?
>
> --
> 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:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> 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] Floating menus and new functions - Matt's 2 cents

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

+1  -- I like the idea, Matt!

You should go with the first option though (having a set template name).
It'll cut down on the code involved and any misunderstanding on how to work
with this feature.  I haven't really looked at your templating caching
system yet, but is there a way to cache this as well?

I don't think the layout option NOT to load includes is necessary.  It
really is up to the siteop to review all template code before they use it.
Or failing that, d/l templates and modules only from trusted developers or
archives.

Eloi George (aDarkling)


----- Original Message -----
From: "Matthew McNaney" <ma...@tu...>
> Along these same lines I was thinking of something many people have asked
> for but I wish discussion before putting it in the rewrite.
>
> Layout could look for a php include file. The theme developer could then
> put special code in it if they want. For example
>
> File: themes/mytheme/runme.php
> <?php
>
> $runmeTemplate["DATE"] = date("Ymd");
>
> ?>
>
> The admin could then put {DATE} in their theme and the date would appear.
>
> This could work a couple of different ways. There could be a set template
> name they have to use. Or there might be specific layout functions they
> could call to place their data in the theme box queue.
>
> We could also have a layout option NOT to load includes until the user has
> a chance to read what is in there. I realize this could be sketchy
> security wise, but a bogus module could do just as much damage.
>
> :Matt
>
> Oh and if you want me to write those functions let me know. Layout was
> supposed to have a way to overwrite or append the metatags set in the
> module but I never got around to it.

Re: [Phpwebsite-developers] Floating menus and new functions

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

On Tue, 2002-12-17 at 08:03, Steven Levin wrote:
>    I was implementing the floating css menu within the menuman module (BTW
> if you would like to see
> http://res1.stddev.appstate.edu/phpwebsite/steven/phpws_core/ ). 

Steven,
Thank you for adding this. :-)

-- 
Mike Noyes <mhnoyes @ users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
http://leaf-project.org/  http://sitedocs.sf.net/  http://ffl.sf.net/