phpwebsite-developers

[Phpwebsite-developers] BBCode

[Shaun M. <sh...@ae...>]

Just a quick 'gotcha'

Don recently added BBCode parsing to core/Text.php in CVS.

Don't use parseOutput on email address fields in your modules as the 
PEAR BBCode parser will convert anything it thinks is an email address 
into a mailto: link.


Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] BBCode

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

On Tue, Apr 06, 2004 at 02:14:25AM +0100, Shaun Murray wrote:
> Don't use parseOutput on email address fields in your modules as the=20
> PEAR BBCode parser will convert anything it thinks is an email address=20
> into a mailto: link.

Or use the BBCode parsing to your advantage and let it do the mailto:
link.  *shrug*

Don.

--=20
"I am mindful not only of preserving executive powers for myself, but for
predecessors as well."

George W. Bush
January 29, 2001
Washington, D.C.

Re: [Phpwebsite-developers] BBCode

[Shaun M. <sh...@ae...>]

On 6 Apr 2004, at 04:02, Don Seiler wrote:

> On Tue, Apr 06, 2004 at 02:14:25AM +0100, Shaun Murray wrote:
>> Don't use parseOutput on email address fields in your modules as the
>> PEAR BBCode parser will convert anything it thinks is an email address
>> into a mailto: link.
>
> Or use the BBCode parsing to your advantage and let it do the mailto:
> link.  *shrug*

I noticed it in a form where you filled in your email address. eg. a 
contact page. The user entered in an address which was getting saved in 
the database as a mailto: link. Not terribly useful if you actually 
wanted the email address for processing later but easily avoided by not 
using parseOutput.



Shaun
aegis design - http://www.aegisdesign.co.uk

Re: [Phpwebsite-developers] BBCode

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

On Tue, Apr 06, 2004 at 05:04:27AM +0100, Shaun Murray wrote:
> I noticed it in a form where you filled in your email address. eg. a=20
> contact page. The user entered in an address which was getting saved in=
=20
> the database as a mailto: link. Not terribly useful if you actually=20
> wanted the email address for processing later but easily avoided by not=
=20
> using parseOutput.

I don't think you want to be using parseOutput() to prefill form fields
anyway.  It's my opinion that parseOutput() is used for displaying of
that entered data.  In a form edit field you'd want to see the raw data
unparsed.

Where are you seeing this?  One of my mods?

Don.

--=20
"There is book smart and the kind of smart that helps do calculus.  But sma=
rt
is also instinct and judgement and common sense.  Smart comes in all kinds =
of
different ways."

George W. Bush
September 19, 2000
=46rom CNN interview.

Re: [Phpwebsite-developers] BBCode

[Shaun M. <sh...@ae...>]

On 6 Apr 2004, at 05:08, Don Seiler wrote:

> On Tue, Apr 06, 2004 at 05:04:27AM +0100, Shaun Murray wrote:
>> I noticed it in a form where you filled in your email address. eg. a
>> contact page. The user entered in an address which was getting saved 
>> in
>> the database as a mailto: link. Not terribly useful if you actually
>> wanted the email address for processing later but easily avoided by 
>> not
>> using parseOutput.
>
> I don't think you want to be using parseOutput() to prefill form fields
> anyway.  It's my opinion that parseOutput() is used for displaying of
> that entered data.  In a form edit field you'd want to see the raw data
> unparsed.
>

Yep. Almost certainly true else you get weird things like html entities 
turning back into their characters so the reason you put them in in the 
first place gets lost.


> Where are you seeing this?  One of my mods?
>

Nah, it was in the mailto mod announced on the phpwebsite site a few 
days ago that I noticed it but thought I'd mention it just in case 
other people came across it in their modules.


Shaun
aegis design - http://www.aegisdesign.co.uk