'%20' problems

Hey there,

We use NOF for templating our web apps.
Everything is cool except that NOF is now inserting %20 in links ...
even if these links are smarty template elements (smarty is a famous
template engine for Php apps.)

For example : I may have a dynamic link like
index.php?{if $myvar eq 1}page=my_redirect{/if}

the link becomes
index.php?{if%20$myvar%20eq%201}page=my_redirect{/if}

Is there a way to get rid of these '%20' ?

best regards,

Etienne

I've seen this happen when using spaces..therefore I NEVER EVER use spaces
for ANYTHING...but I could be way off here..I don't speak PHP

--
Thanks,
Cherie



"Etienne Sévin" <etienne@epiconcept.fr> wrote in message
news:eglgje$itu2@flsun90netnews01.netobjects.com.. .
> Hey there,
>
> We use NOF for templating our web apps.
> Everything is cool except that NOF is now inserting %20 in links ...
> even if these links are smarty template elements (smarty is a famous
> template engine for Php apps.)
>
> For example : I may have a dynamic link like
> index.php?{if $myvar eq 1}page=my_redirect{/if}
>
> the link becomes
> index.php?{if%20$myvar%20eq%201}page=my_redirect{/if}
>
> Is there a way to get rid of these '%20' ?
>
> best regards,
>
> Etienne

Etienne,

"index.php?{if $myvar eq 1}page=my_redirect{/if}" doesn't strike me as being valid syntax.

In any case, valid PHP code needs to be contained within <? and ?> delimiters for it to be interpreted by the web
server.

Do you have a working example of this that you're trying to go by?

--
Chuck Joslin
BeyondFusion.com - Your Fusion Community
www.beyondfusion.com

Register domain names at www.awavedomains.com

"Etienne Sévin" <etienne@epiconcept.fr> wrote in message news:eglgje$itu2@flsun90netnews01.netobjects.com.. .
> Hey there,
>
> We use NOF for templating our web apps.
> Everything is cool except that NOF is now inserting %20 in links ...
> even if these links are smarty template elements (smarty is a famous
> template engine for Php apps.)
>
> For example : I may have a dynamic link like
> index.php?{if $myvar eq 1}page=my_redirect{/if}
>
> the link becomes
> index.php?{if%20$myvar%20eq%201}page=my_redirect{/if}
>
> Is there a way to get rid of these '%20' ?
>
> best regards,
>
> Etienne

Thanks for your answer Chuck,

Of course it doesnt appear to be a valid php syntax ... because it is
not a php syntax at all ... it's a template syntax.

Today it's really hard, if not impossible, to consider developping php
applications inserting php code directly into the html pages !
Messy nested code ... hard to maintain ... yecchhh !

So "{if $myvar eq 1}page=my_redirect{/if}" will be parsed, not by the
server, but by the template engine.
It's really a common way to do. Most of all, the template engine is
smarty, kind of official template engine for php.


The problem is that nof consider that kind of syntax a crap !
Maybe we could have someting like <dontparse></dontparse> tags ... it
would be really useful for developpers who want to use nof !


best regards,

Etienne


Chuck «BeyondFusion» a écrit :
> Etienne,
>
> "index.php?{if $myvar eq 1}page=my_redirect{/if}" doesn't strike me as being valid syntax.
>
> In any case, valid PHP code needs to be contained within <? and ?> delimiters for it to be interpreted by the web
> server.
>
> Do you have a working example of this that you're trying to go by?
>

What "template engine" are you referring to?

I've been doing PHP with Fusion for years without using such a thing.

It's not hard or impossible (or hard to maintain) at all.

--
Chuck Joslin - Team NetObjects
BeyondFusion.com - Your Fusion Community
www.beyondfusion.com

Register domain names at www.awavedomains.com

"Etienne Sévin" <etienne@epiconcept.fr> wrote in message news:egvtcc$rod2@flsun90netnews01.netobjects.com.. .
> Thanks for your answer Chuck,
>
> Of course it doesnt appear to be a valid php syntax ... because it is
> not a php syntax at all ... it's a template syntax.
>
> Today it's really hard, if not impossible, to consider developping php
> applications inserting php code directly into the html pages !
> Messy nested code ... hard to maintain ... yecchhh !
>
> So "{if $myvar eq 1}page=my_redirect{/if}" will be parsed, not by the
> server, but by the template engine.
> It's really a common way to do. Most of all, the template engine is
> smarty, kind of official template engine for php.
>
>
> The problem is that nof consider that kind of syntax a crap !
> Maybe we could have someting like <dontparse></dontparse> tags ... it
> would be really useful for developpers who want to use nof !
>
>
> best regards,
>
> Etienne
>
>
> Chuck «BeyondFusion» a écrit :
>> Etienne,
>>
>> "index.php?{if $myvar eq 1}page=my_redirect{/if}" doesn't strike me as being valid syntax.
>>
>> In any case, valid PHP code needs to be contained within <? and ?> delimiters for it to be interpreted by the web
>> server.
>>
>> Do you have a working example of this that you're trying to go by?
>>

I'm refering to Smarty Chuck. And it's not because you're using Fusion
that everyone should ...
If you're considering smarty as an exotic template engine, what else
could I argue ?

Having NOF parsing the space as a %20 is a terrible new for us ... We
have been using nof for 10 years now and I keep strugling for it. Maybe
you should understand that.

If we use templates, we should have the choice to be non W3C compliant,
since the {} will be parsed by the template engine.

Chuck «BeyondFusion» a écrit :
> What "template engine" are you referring to?
>
> I've been doing PHP with Fusion for years without using such a thing.
>
> It's not hard or impossible (or hard to maintain) at all.
>