phpbddb-dev1

Re: [phpBddb-dev1] comments

[Janis P. <jan...@on...>]

Hi!
Well, I have to agree.
1)One solution could be to define a global variable $msg and register it in=
 the session. So in the beggining of file we could check if it is !=3D'', p=
rint it out and clear after that.
2)We could save it all in the sql and attach to the session id. It could ke=
ep an archive so the logging would be solved.
3)I personally don't like frames, but one parent frame could solve the prob=
lem as well.
I am still thinking of better solutions... Just some ideas to think about.
Janis

> -----S=E2kotn=E7j=E2 zi=F2a-----
> No: "Brian" <br...@br...>
> S=FBt=EEts: 2002-08-07 16:11:22.78
> Kam: "php...@li..." <php...@li...urceforge=
.net>
> Par: Re: [phpBddb-dev1] comments
>=20
> Hi,
>=20
> i don`t really like to exchange error messages via the URL, if it is=20
> numeric or not. Best thing is to keep the URI clean. For the future i wan=
t=20
> to exchange even the 'cmd' parameter via post method only.
> Also adding new error codes is not very comfortable.
>=20
> So what to do with error messages!?
>=20
> - we want them to be displayed above the content
> - we want them to be configurable (color etc.)
> - we want multilanguage support
> - we want no more parameters in URI
> - we want it to be secure, so that no one could place html-code
> - we want to be able to display more than one error message
> - maybe we want to log errors with IP, username and error message
>=20
> Solution?
> We should have a function, that is called with an error code. It should=
=20
> handel translation, displaying and logging.
>=20
> I don't have a perfect idea right now, any suggestions??
>=20
> Brian
>=20
>=20
> At 01:37 06.08.2002 +0300, you wrote:
> >2) global $msg_codes array. This array has the numeric value for message=
s=20
> >that would be passed between files. It would be easier to send plain tex=
t=20
> >but it is not "secure" because someone could put HTML in it.
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Phpbddb-dev1 mailing list
> Php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpbddb-dev1
>=20

--> http://www.one.lv - your number one mobile email service!

Re: [phpBddb-dev1] comments

[Brian <br...@br...>]

Hi,

my suggestion is:

1. We'll define a global variable $msg in config_inc.php. (I think we need 
not to register it in the session).
2. We have a function setMsg(String m), which adds the provided String to 
the gobal $msg and logs the m parameter to database.
However m is just a error shortcut and the name of the corresponding array 
field.
3. We have a function getMsg(), which returns the formatted error messages 
saved in the gobal $msg. Also getMsg() has to clean $msg and log entries 
older than xx days.

Hm. where to place the translation? Logging should be done in english only, 
but displaying in user selected language.
We will do translation in the same way as done with the strings, before 
sending the error string.

Sending error messages could be easy done by setMsg('file_n_found');
Displaying is automaticlly done by calling getMsg(); before content $go is 
printed in body.php.

I've implemented bare bones of these two functions.
They do work for displaying errors yet. Have a look at CVS.

Brian



At 16:38 07.08.2002 +0300, you wrote:
>Hi!
>Well, I have to agree.
>1)One solution could be to define a global variable $msg and register it 
>in the session. So in the begining of file we could check if it is !='', 
>print it out and clear after that.
>2)We could save it all in the sql and attach to the session id. It could 
>keep an archive so the logging would be solved.
>3)I personally don't like frames, but one parent frame could solve the 
>problem as well.
>I am still thinking of better solutions... Just some ideas to think about.
>Janis