Raphaël Luta wrote:
David Sean Taylor wrote:
Raphaël Luta wrote:
I would personnally say that the best way would be to define a new
FusionEncodingPortalURL that behaves just like PathInfoEncoding
except that it adds the follwoing string : _ns/_ns: instead of
simply _ns:
It would change anything for j2 since it specically looks for '_ns:'
as an identifier and will allow Turbine to recognize a new _ns
parameter which it would care about but at least will not break the
othher parts of the URL.
The Fusion assembly script needs to use the FusionPortalURL instead
of any of the regular ones.
What do you think ?
Looks Turbine friendly to me.
Are you going to write it ?
Im going to try releasing 1.6 today.
I thought we would first go through Release candidates for 1.6 before
announcing an official "1.6" release ?
If we could get the fix in now I'd be glad to incorporate it in the
release
I can write it easily but I don't have currently the environment to
test it :) I've not yet run Fusion...
I'll commit a patch later this evening.
anyway this is a good idea. I've got some time tomorrow to write and
test it. I can submit something tomorrow at around 12:00. Is that OK for
you ?
Fabrice
--
Fabrice Dewasmes
Responsable du domaine urbanisation des systèmes d'information
[EMAIL PROTECTED]
06.89.88.65.37
--
Open Wide
14 rue Gaillon
75002 PARIS
www.openwide.fr
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
