phpwebsite-developers — For our development team.

Re: [Phpwebsite-developers] Updating 0.9.x

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

How does boost know where to check what the latest version is?  Will there 
be a central repository of version/download files somewhere?  That would 
be great, IMHO.

Don.

On Tue, 17 Dec 2002, Matthew McNaney wrote:

> Something I forgot to mention was how you can let people know you have a
> module update.
> 
> Go here:
> http://phpwebsite.appstate.edu/updates/calendar/
> 
> There are two files, only one of which is required.
> 
> Open update.txt
> 
> There are three variables using double colons to separate the data
> 
> download
> ---------------
> Put the address of where people can download your latest tarball.
> You can put multiple address here if you like:
> 
> Example
> download::phpwebsite.appstate.edu/updates/calendar/cal.tar.gz
> download::mirror.phpwebsite.com/updates/calendar/cal.tar.gz
> 
> Or if you wanted, you could just enter the address your download page and
> not the tarball itself. It is your choice.
> 
> version
> ------------------
> The latest version of your module. This is what Boost checks to to see if
> the module should be downloaded.
> 
> 
> 
> information
> --------------------
> A web address to your information page. In this example, I just created an
> information file and left it in the same directory. Eventually we will
> probably have separate pages for each module or even different web sites
> for each developer. Who knows. Anyway, link to module information here.
> 
> 
> That is all. You can see how this works by getting CVS and laying it on
> top of RC3 (after using repair and updating boost and core). Click the
> "Check for Update" button next to calendar.
> 
> Later
> Matt
> 
> 
> 
> 

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

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

+1 infinity.

Great idea.

Don.

On Tue, 17 Dec 2002, Eloi George wrote:

> +1 !!!!
> 
> The ability to place custom metatags?   I would love that!
> 
> Eloi George
> 
> 
> 
> 
> 
> -------------------------------------------------------
> 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
> 
> 
> 

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

[Joost H. <joo...@bt...>]

Yes please!

I was struggling with this a few days ago - I was trying to use a javascript 
date fill-in popup calendar (Mihai Bazon's JS calendar) which forced me to add 
the javascript in the theme - not very elegant because if it stays like this the 
calendar will only work with themes I modified.

So yes, that would be very useful.

J:)st

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

[Matthew M. <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.


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

> +1
>
> Rig it for now if you want or wait for my rewrite :)
>
>
> --
> Matthew McNaney
> Internet Systems Architect
> Electronic Student Services
> Appalachian State University
> Phone: 828-262-6493
> phpwebsite.appstate.edu
> ess.appstate.edu
>
>> +1 !!!!
>>
>> The ability to place custom metatags?   I would love that!
>>
>> Eloi George
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> 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
>
>
>
>
>
> -------------------------------------------------------
> 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

[Phpwebsite-developers] Updating 0.9.x

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

Something I forgot to mention was how you can let people know you have a
module update.

Go here:
http://phpwebsite.appstate.edu/updates/calendar/

There are two files, only one of which is required.

Open update.txt

There are three variables using double colons to separate the data

download
---------------
Put the address of where people can download your latest tarball.
You can put multiple address here if you like:

Example
download::phpwebsite.appstate.edu/updates/calendar/cal.tar.gz
download::mirror.phpwebsite.com/updates/calendar/cal.tar.gz

Or if you wanted, you could just enter the address your download page and
not the tarball itself. It is your choice.

version
------------------
The latest version of your module. This is what Boost checks to to see if
the module should be downloaded.



information
--------------------
A web address to your information page. In this example, I just created an
information file and left it in the same directory. Eventually we will
probably have separate pages for each module or even different web sites
for each developer. Who knows. Anyway, link to module information here.


That is all. You can see how this works by getting CVS and laying it on
top of RC3 (after using repair and updating boost and core). Click the
"Check for Update" button next to calendar.

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

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

+1

Rig it for now if you want or wait for my rewrite :)


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

> +1 !!!!
>
> The ability to place custom metatags?   I would love that!
>
> Eloi George
>
>
>
>
>
> -------------------------------------------------------
> 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

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

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

+1 !!!!

The ability to place custom metatags?   I would love that!

Eloi George

[Phpwebsite-developers] Floating menus and new functions

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

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...

[Fwd: Re: [Phpwebsite-developers] RC3 update]

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

> Is Calendar also a model for new module developers?
>
> Don.

I'd say so. It is using a bunch of different concepts (FatCat, groups,
overlapping templates). But is only about half done. Take a look at it and
some of the newer modules coming out this week (eg FAQ, Polls).

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 update

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

Is Calendar also a model for new module developers?

Don.

On Mon, 16 Dec 2002, Matthew McNaney wrote:

> Hello all,
> 
> I talked with Adam and Steven today. Since we are in a new week, they
> would like an opportunity to tighten the screws on some of the new modules
> they are writing. I admit I would like a little elbow room as well. So we
> are shooting for a lockdown on Thursday, a release Friday morning, a
> re-release
> later in the day to fix the obvious error we included in the first
> release, and then a final one around midnight ;-)
> 
> Seriously, we are looking for Friday but we plan on testing better than
> the last two times.
> 
> Now then, for the impatient and the module developers, information on update.
> 
> I have successfully updated RC2 to RC3. However, I would like some of you
> who download CVS copies to give it a try.
> 
> Here is what you will need to do:
> Get your cvs copy of the core, mods, and themes. Copy the appropriate
> directories over. Obviously when RC3 comes out, you will just untar over
> the old files.
> 
> If you go to your site, you MIGHT get an error if you are running
> Calendar. No worries, go to setup/repair.php and follow the directions.
> Ultimately, you will be able to deactivate calendar.
> 
> If you go back to your site, you will get an error in Boost, so while in
> Repair, follow the question about Boost and choose Fix Boost.
> 
> NOW go back to your site, click on Boost, update Boost, update Core, and
> update the rest of your modules. There is an Update All button at the
> bottom of the screen.
> 
> You should be on RC3 level now. If there are any problems please let me know.
> 
> -------------------------------------------
> For the developers, please check out Calendar as an example of updating.
> It is very straight-forward and works much like the install.php file does.
> Make sure you change your version number in your mod_info.php file. If it
> is not greater than what is in mod_boost_version, it will not update. I
> have updated most of the core files. I haven't touched other modules. If
> you have not made any database changes, just increment your mod_info.php
> version number. If you have made database changes since RC2, please enter
> those changes in update.
> 
> Also, I did not use the --> if ($currentVersion < 2.3) <--- code in many
> of the updates but they will appear as updates increase. MAKE SURE your
> $status is TRUE by the end of the update or it will fail.
> 
> In the short term (maybe by RC3 release, maybe not) I will rethink
> dependencies. I would like modules to tell you whether you need to update
> other modules first. I also will build in the ability to turn modules off
> before updating them.
> 
> Those of you having problems with Fallout, please try a CVS checkout and
> see if repair.php helps you at all. Some changes have been made to
> set_config.php to try to assist Windows installations as well.
> 
> Excelsior,
> 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:
> 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
> 
> 
> 

Re: [Phpwebsite-developers] Version 0.9 status question

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

> 1. What do I need to do to upgrade my RC2 test site to RC3 (when it is
> available)? (Delete it and start over is a perfectly acceptable answer
> if  that is easiest.)

There should be an upgrade path, so you should not have to delete it.

> 2. What confidence level do you have that the database for RC3 will be
> final (or will further modifications to the database be needed)?

The main database tables (modules, users, layout) should be stable. Any
changes will be gracefully attended to by the update script :)

> 3. Is the module plug-in system sufficiently finalized to start working
> on  some modules?

I think so. We are constantly writing new mods and we are writing a major
module in-house based on the current implementation.

> 4. How many more release candidates do you think there will be before
> the  final release of 0.9.0?

If RC3 goes well, then that will be last RC. A final release will follow.
If it goes bad, then one more RC.

> I'm just looking for a general idea of what to expect, not anything I
> can  take to the bank!

No problem. We are anxious to get it out as well.

Sincerely,
Matt

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

[Phpwebsite-developers] RC3 update

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

Hello all,

I talked with Adam and Steven today. Since we are in a new week, they
would like an opportunity to tighten the screws on some of the new modules
they are writing. I admit I would like a little elbow room as well. So we
are shooting for a lockdown on Thursday, a release Friday morning, a
re-release
later in the day to fix the obvious error we included in the first
release, and then a final one around midnight ;-)

Seriously, we are looking for Friday but we plan on testing better than
the last two times.

Now then, for the impatient and the module developers, information on update.

I have successfully updated RC2 to RC3. However, I would like some of you
who download CVS copies to give it a try.

Here is what you will need to do:
Get your cvs copy of the core, mods, and themes. Copy the appropriate
directories over. Obviously when RC3 comes out, you will just untar over
the old files.

If you go to your site, you MIGHT get an error if you are running
Calendar. No worries, go to setup/repair.php and follow the directions.
Ultimately, you will be able to deactivate calendar.

If you go back to your site, you will get an error in Boost, so while in
Repair, follow the question about Boost and choose Fix Boost.

NOW go back to your site, click on Boost, update Boost, update Core, and
update the rest of your modules. There is an Update All button at the
bottom of the screen.

You should be on RC3 level now. If there are any problems please let me know.

-------------------------------------------
For the developers, please check out Calendar as an example of updating.
It is very straight-forward and works much like the install.php file does.
Make sure you change your version number in your mod_info.php file. If it
is not greater than what is in mod_boost_version, it will not update. I
have updated most of the core files. I haven't touched other modules. If
you have not made any database changes, just increment your mod_info.php
version number. If you have made database changes since RC2, please enter
those changes in update.

Also, I did not use the --> if ($currentVersion < 2.3) <--- code in many
of the updates but they will appear as updates increase. MAKE SURE your
$status is TRUE by the end of the update or it will fail.

In the short term (maybe by RC3 release, maybe not) I will rethink
dependencies. I would like modules to tell you whether you need to update
other modules first. I also will build in the ability to turn modules off
before updating them.

Those of you having problems with Fallout, please try a CVS checkout and
see if repair.php helps you at all. Some changes have been made to
set_config.php to try to assist Windows installations as well.

Excelsior,
Matt


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

[Phpwebsite-developers] Version 0.9 status question

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

We want to get more involved with this project and start developing some 
modules for it.

So, I have a couple of basic questions:

1. What do I need to do to upgrade my RC2 test site to RC3 (when it is 
available)? (Delete it and start over is a perfectly acceptable answer if 
that is easiest.)

2. What confidence level do you have that the database for RC3 will be 
final (or will further modifications to the database be needed)?

3. Is the module plug-in system sufficiently finalized to start working on 
some modules?

4. How many more release candidates do you think there will be before the 
final release of 0.9.0?

I'm just looking for a general idea of what to expect, not anything I can 
take to the bank!

Geoff
www.Hostricity.com

[Phpwebsite-developers] Sign-On Oooops in 8.2

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

Just discovered this:

If you delete a user from the database, but, they were signed on at the 
time you deleted them, then they continue to have user access until they 
logout.

Apparently, when someone logs in and a cookie is stored on their machine, 
as long as they don't log out, the cookie stays forever and phpWebsite 
never looks up the userid in the cookie in the database.

Seems like, each time a user opens a browser and comes to the website, and 
is already logged on with a cookie, the system should verify the userid in 
the cookie against the database and delete the cookie if the user is no 
longer in the database.

Has anyone noticed this before? Is there a fix?

If not, can someone point me to the general location and I'll write a patch.

Geoff
www.Hostricity.com

[Phpwebsite-developers] Delay of game

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

RC3 will be pushed back until next week.

I was hoping to get something out today but I hit two nags.

One, I don't want to have JUST a boost kludge. Instead I started on a file
named repair.php. When run it will ATTEMPT to fix any problem you have
with your phpWS installation.

I will contain the fixes for the boost problem, but it will also diagnose
other problems as well and offer solutions. I figure that should cut down
on problems people are having with installations. It will be written such
that new problems and solutions can be added to it. It will also contain
tools to fix the problems as well as advice.

The second snag I hit was the ... grrr.. magic quotes issue. I changed the
cookie class as I thought I didn't need so many stripslashes. I was wrong.
Magic quotes, when enabled, not only addslashes to the cookie as it is
written it ALSO adds them when they are retrieved. Why, I don't know. On
the good side, I found an repeating function call that only needed calling
once. It has been fixed.

So anyway, these items have occupied my time today. I think in the long
run though, the repair stuff will improve our admin relations :) I am
testing the pear portion on my laptop. If it works, I'll return to the
things I have planned to facilitate the update.

Cheers,
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 Close

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

Rock on.

How is the situation as far as module stability, from a module author 
point-of-view?  Is it safe for me to being writing for RC3, or will 
interfaces/hooks/plugins be changed that will shoot it all to hell?

Thanks,
Don.

On Thu, 12 Dec 2002, Matthew McNaney wrote:

> Hello all,
> 
> I have been testing the new version of phpWebSite. The plan is to enable
> updating from this point on. It needs more testing before ready.
> 
> Here's the thing. I changed Boost. It has a new table that it uses to
> update modules and the core. Can you guess the side effect? To update RC2,
> you need that table. Without the table, boost can't help you and boost
> updates boost. Still following me?
> 
> So after fiddling around with it, I think the best thing to do would be to
> ship a crutch file with RC3 (probably just a DB dump). I could (and have
> in testing) written boost to kludge around its absence but that would be a
> bunch of sloppy code that would never be used after final release anyway.
> 
> So this next version should install as normal and be ready to update.
> However, with a few helpers, you should also be able to update RC2 just so
> you can see how it will work in the future.
> 
> Tonight's CVS may be a little shakey but should be better in the morning.
> 
> More tomorrow.
> Matt
> 
> 
> 

[Phpwebsite-developers] RC3 Close

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

Hello all,

I have been testing the new version of phpWebSite. The plan is to enable
updating from this point on. It needs more testing before ready.

Here's the thing. I changed Boost. It has a new table that it uses to
update modules and the core. Can you guess the side effect? To update RC2,
you need that table. Without the table, boost can't help you and boost
updates boost. Still following me?

So after fiddling around with it, I think the best thing to do would be to
ship a crutch file with RC3 (probably just a DB dump). I could (and have
in testing) written boost to kludge around its absence but that would be a
bunch of sloppy code that would never be used after final release anyway.

So this next version should install as normal and be ready to update.
However, with a few helpers, you should also be able to update RC2 just so
you can see how it will work in the future.

Tonight's CVS may be a little shakey but should be better in the morning.

More tomorrow.
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] New theme

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

lol Great theme, Matt!  It gives phpWebSite a little life :)

Adam

> I submitted a new theme for phpwebsite today.
>
> It is BRIGHT! Turn down your monitor settings!
>
> Seriously, it should show how quickly you can make a theme.
>
> i made it in notepad in my windows box. Copied all the images over,
> copied the default theme, style sheet, and boxstyles. A few edits later
> and bada bing. I would say it took about 4 hours tops.
>
> 4 hours to make this crap? Yes, I beat you to it ;)
>
> 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


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

[Phpwebsite-developers] New theme

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

I submitted a new theme for phpwebsite today.

It is BRIGHT! Turn down your monitor settings!

Seriously, it should show how quickly you can make a theme.

i made it in notepad in my windows box. Copied all the images over, copied
the default theme, style sheet, and boxstyles. A few edits later and bada
bing. I would say it took about 4 hours tops.

4 hours to make this crap? Yes, I beat you to it ;)

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] core_settings removed

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

More information:

I have removed addslashes and serialization from many of the core files.

I have ALSO removed the function serialize and unserialize from the Text
class. If you are using them (I don't think anybody did except for me),
dump them.

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] core_settings removed

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

> sqlInsert and sqlUpdate will take charge of the addslashes issue. They
> will automatically test text before it is saved. The developer will
> never worry about the save format.

Ok, this has been committed.

As a refresher:

You don't need to addslashes to anything before sending it to sqlInsert
and/or sqlUpdate now. They will take care of it.

You do not need to serialize arrays or (ick, not) objects before sending
them to sqlInsert and/or sqlUpdate.

You DO have to unserialize after a sqlSelect. I could have this done
automatically but it would exponentially increase its process time.

The 'parse' function should not be used any more. Use parseInput to remove
unwanted tags and parseOutput to remove profanity and to break the text.

You might want to grep your modules for parse and addslashes to clean it up.

Please respond if you have any problems.

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] core_settings removed

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

> This kind of comes back to something I was discussing with you earlier,
> Matt.  You remember when we were talking about a function that parses
> user input and a function that parses output.  We pretty much have those
> now in parse() and breaker() but I'm wondering if we should make these
> functions standard [parseInput(), parseOutput()].  Just a thought...

Adam, Steven, and I talked about the above issue. Here is what we decided.

sqlInsert and sqlUpdate will take charge of the addslashes issue. They
will automatically test text before it is saved. The developer will never
worry about the save format.

parse will split into parseInput and parseOutput. Input will strip tags.
Output will put breaks on newlines and strip profanity.

Expect these changes later today,
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] core_settings removed

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

> Good point. I think we could leave it up to the developer. You don't
> have to call parse before you save the data. You could just call
> strip_tags and addslashes on your own, then call profanityFilter during
> display.

This kind of comes back to something I was discussing with you earlier,
Matt.  You remember when we were talking about a function that parses user
input and a function that parses output.  We pretty much have those now in
parse() and breaker() but I'm wondering if we should make these functions
standard [parseInput(), parseOutput()].  Just a thought...

> BTW Adam, wasn't there something breaker was not working with properly?

Yes check out the bug on sourceforge: 645750

Adam

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

Re: [Phpwebsite-developers] core_settings removed

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

> I'd like to bring something up along these lines.  I'm wondering if
> parse() should handle the profanity filtering or breaker().  IMHO, I
> think we should store the profanity in the database and filter it on
> display. That way, if an admin decides to change his/her filter, any
> previous profanity will be revealed.  Thoughts?

Good point. I think we could leave it up to the developer. You don't have
to call parse before you save the data. You could just call strip_tags and
addslashes on your own, then call profanityFilter during display.

BTW Adam, wasn't there something breaker was not working with properly?

Thanks,
Matt

Re: [Phpwebsite-developers] core_settings removed

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

> The core_settings table has been removed from CVS. The text and date
> information is now handled by files, which you should receive when you
> update.

Woot!

> Adam: I tested pagemaster with parse and it worked well. You will need
> to add the function on the line that imports the POST into the section
> object.

I will get that in asap.

I'd like to bring something up along these lines.  I'm wondering if
parse() should handle the profanity filtering or breaker().  IMHO, I think
we should store the profanity in the database and filter it on display.
That way, if an admin decides to change his/her filter, any previous
profanity will be revealed.  Thoughts?

> Also, I have put a switch in the setup.php file for those who want to
> install with a version under 4.2.2. It was suggested we use a yes/no
> form but I prefer this way. The admin would have to physically alter the
> file instead of clicking a button.

+1 here

Lates,
Adam

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